I would not say that I did not expect that.

I provided all source code, which easily shows errors, but as an answer got 

we can't reproduce this bug

If I could resolve those issues by myself I would do it, but this is InterSystems responsibility 

With those errors, I would not use JDBC in production, would not even try any project, due to the bugs I discovered with SQLancer project.

And for Python, luckily I already have driver in pure Python that works much more stable than new official one, so, would use it, and would not use official driver, as I see that it can fail at any time. 

I have no reason to use WRC for reporting these bugs, as I did not find it for the company, I found it in open source projects. And after discoveries, would not even try implementing it in company, so, no point.

Most of the time it generates queries that make no sense. But still supposed to be working.

CREATE TABLE t0(c0 BIT );
SELECT * FROM t0 WHERE (c0 IN (c0, c0, c0, c0));

Gives

SQL Error [400] [S1000]: [SQLCODE: <-400>:<Fatal error occurred>]
[Location: <Prepare>]
[%msg: <<UNDEFINED>in+4^%qaqpnl *mt("v","4")>]

https://ideas.intersystems.com/ideas/DPI-I-881 

Yeah, I know that it's works without those brackets. But the thing is that SQLancer generates SQL queries randomly, and expected to produce queries that looks ridiculous, but syntactically correct and expected to work

On community edition due to small amount of licensed connections, and issue with fast releasing available connections, and probably due to too many failures on the network layer in the communication it's very fast start to fail to connect due to license limit.