SIGSEGV error in JRE when connecting to the database
See original GitHub issueHello! sometimes I run into the following error when runnning the local-data-api container:
[2020-03-24 15:46:57 +0000] [7] [INFO] Waiting for application startup.
[2020-03-24 15:47:46 +0000] [7] [INFO] ('172.19.0.1', 43568) - "POST /BeginTransaction HTTP/1.1" 200
[2020-03-24 15:47:46 +0000] [7] [INFO] ('172.19.0.1', 43568) - "POST /RollbackTransaction HTTP/1.1" 500
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fef41ea0e69, pid=7, tid=0x00007fef49bc2b88
#
# JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build 1.8.0_222-b10)
# Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea 3.13.0
# Distribution: Custom build (Tue Oct 1 11:00:28 UTC 2019)
# Problematic frame:
# C [_jpype.cpython-37m-x86_64-linux-gnu.so+0x28e69] JPJavaEnv::NewLocalRef(_jobject*)+0x9
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /app/hs_err_pid7.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# https://icedtea.classpath.org/bugzilla
#
[2020-03-24 15:47:46 +0000] [21] [INFO] Booting worker with pid: 21
[2020-03-24 15:47:46 +0000] [21] [INFO] Started server process [21]
[2020-03-24 15:47:46 +0000] [21] [INFO] Waiting for application startup.
The reported section is taken from docker logs
of a container running the local-data-api image.
It seems that the problem is related to the amount of memory space reserved to the JVM, as suggested into the stacktrace it could be useful to increase it. I don’t know how you could reproduce the problem, since it appears only sometime.
By the way, for further enhancement I suggest to remove the JDBC approach for connecting to database instances. Since the program is written in Python, it could be more efficient using psycopg2 o pymysql.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
A fatal error has been detected by the Java Runtime ...
A fatal error has been detected by the Java Runtime Environment: SIGSEGV, libjvm - Stack Overflow. Stack Overflow for Teams – Start collaborating...
Read more >Re: Getting SIGSEGV error when trying to connect t...
I am running the spark jar on dataproc cluster. I am getting error when trying: datasource.getConnection(). This is the full error: # #...
Read more >unexpected sigsegv error - Oracle Communities
The consensus solution seems to be an upgrade of the JVM, but that's hard to recommend without completely understanding the cause of the...
Read more >FMS server crashes unexpectedly. Crash dump shows ...
Crash dumps in main FMS directory hs_err_pidNNN.log shows a SIGSEGV fault. # A fatal error has been detected by the Java Runtime Environment ......
Read more >JDK-8074089 SIGSEGV fault SEGV_MAPERR - Bug ID
ACTUAL - I don't see a place to attach a file, so here is a cut and paste of the SIGSEGV output: #...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@agatim I will check the documents!! Thank you very much 😄
Hi @koxudaxi
I hit same error, is there a workaround? Saw your #69 pr but not sure if that fixes it
Thanks!
UPDATE: I just tried your change and now it works