JDBC connection to Db2 raises JRE error

I recently upgraded MacOS to Big Sur and code that connects to DB2 using jaydebeapi used to connect successfully (prior to OS upgrade) now raises JRE errors.  I am running  2020.3 CE and jaydebeapi 1.2.3.  Is this a known issue?

Error in console starts off as follows:

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fff2a4f2658, pid=44039, tid=0x0000000000000307
#
# JRE version: Java(TM) SE Runtime Environment (8.0_251-b08) (build 1.8.0_251-b08)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.251-b08 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C [libunwind.dylib+0x9658] _Unwind_RaiseException+0x27
#
4 comments
Comment actions Permalink

Hi, would it be possible to provide minimal code sample that reproduces the issue? Could you please test if running the same code from the terminal outside of IDE produces the same error?

0
Comment actions Permalink

The following program will reproduce issue.  Actually, it fails when run from terminal too - looks like a JRE issue, maybe

#!/usr/bin/python

import jaydebeapi

def run():

host_url = <host name or IP>
port = <port
db_name = <db>
user = <username>
password = <pwd>
jarfiles = <path to jdbc jar>

conn_src = jaydebeapi.connect("com.ibm.db2.jcc.DB2Driver",
"jdbc:db2://%s:%s/%s" % (host_url, port, db_name),[user, password],jars=jarfiles)

return (0)

if __name__ == "__main__":
run()

0
Comment actions Permalink

Thank you,

You're right, if it fails from the terminal, it's not related to IDE.

0
Comment actions Permalink

It turns out that this was due to issues with Python 3.7 on Big Sur.  I downgraded to 3.6 and code ran fine.

0

Please sign in to leave a comment.