Description
Legacy issue: baztian/jaydebeapi#218
Tier: P1 — verify-dodged
DB2 connection crash via jaydebeapi.connect. Our fork uses JPype for JVM management and has its own connection handling in __init__.py. The crash behavior may have changed with our rewritten connection logic, but since we still use JPype and DB2 drivers, we should verify our connect() handles DB2 failures gracefully without crashing the process. Need to check if our error handling in _handle_sql_exception covers this case.
Original Report
When connecting to DB2 via jaydebeapi.connect, the application crashes with an IBM J9 JVM assertion failure:
resize LOA size(0) should not be smaller than minimum LOA size(76800).
** ASSERTION FAILED ** at MemoryPoolLargeObjects.cpp:334: ((false))
The user's try/except block cannot catch this because it's a JVM-level crash, not a Python exception.
Description
Legacy issue: baztian/jaydebeapi#218
Tier: P1 — verify-dodged
DB2 connection crash via
jaydebeapi.connect. Our fork uses JPype for JVM management and has its own connection handling in__init__.py. The crash behavior may have changed with our rewritten connection logic, but since we still use JPype and DB2 drivers, we should verify our connect() handles DB2 failures gracefully without crashing the process. Need to check if our error handling in_handle_sql_exceptioncovers this case.Original Report
When connecting to DB2 via
jaydebeapi.connect, the application crashes with an IBM J9 JVM assertion failure:The user's try/except block cannot catch this because it's a JVM-level crash, not a Python exception.