Solved: How to debug JVM crashes

SQL-Fighter

I'm unable to deploy my RLS variant adapter.  Is there a preferred approach for debugging JVM issues?

 

drumcircle_0-1596098201306.png

 

1 ACCEPTED SOLUTION

Team Exasol
Team Exasol

@drumcircle   In general you can use Java remote debugging to debug any Java UDF , have a look here for virtual schemas: https://github.com/exasol/virtual-schemas/blob/master/doc/development/remote_debugging.md 

View solution in original post

4 REPLIES 4

SQL-Fighter

Using the python udf listener and redirecting script output...how did I miss that!

https://docs.exasol.com/database_concepts/udf_scripts/debug_udf_script_output.htm

SQL-Fighter

I was not listening to remote debugging, so it crashed.

Also, quick newbie tip.  Needs to be a fat char containing the com.exasol.adapter.dialects.exasol package for RLS type schemes.

SQL-Fighter

I'm seeing this in the system log:

/d02_data/EXASolution/log/process/20200729_194801_SqlSession_1673597007407133458.0:30.07 04:17:13.013 SWIGVM crashed with PID: 2575 (R,1,0,ipc:///tmp/exa_socket-0893-8154-ac27-28b4/zmqvmcontainer_conn_11778975284834414098,0)

/d02_data/EXASolution/log/process/20200729_194801_SqlSession_1673597007407133458.0:30.07 04:17:13.013 SWIGVM ERROR a377539d26a92e12 char(40)-6667768788875137518): 'Internal error: VM crashed'

/d02_data/EXASolution/log/process/20200729_194801_SqlSession_1673597007407133458.0:30.07 04:17:13.013 SWIGVM ENGINE SINGLE CALL ZMQVM ERROR: Internal error: VM crashed

/d02_data/EXASolution/log/process/20200729_194801_SqlSession_1673597007407133458.0:30.07 04:17:13.014 Error while SQL execution: Caught this exception: 22002:VM error: Internal error: VM crashed

/d02_data/EXASolution/log/process/20200729_194801_SqlSession_1673597007407133458.0:30.07 04:17:13.016 writeException: 22002 VM error: Internal error: VM crashed (Session: 1673597007407133458)

 

I'm running SYS and bucket is public.

Team Exasol
Team Exasol

@drumcircle   In general you can use Java remote debugging to debug any Java UDF , have a look here for virtual schemas: https://github.com/exasol/virtual-schemas/blob/master/doc/development/remote_debugging.md 

View solution in original post