Skip to main content
Question

Java Runtime / Qt - Fatal Error on Ubuntu 14.04


I am working with a fairly old MS Access Database on Linux using the JDBC driver. When executing my workspace (FME 2016.1.3.1 - 20161207 - Build 16716 - linux-x64) I get the following error message (apparently after a SQL_Executor):

Creating reader for format: Microsoft Access (JDBC)
Trying to find a JAVA plugin for reader named `MSACCESS_JDBC'
Using Java Reader Interface Version 2.0 (Oct 31, 2000) with module MSACCESS_JDBC to read data from dataset `/media/something/CFC1-4CC4/Something/DB_sample12090708.mdb'
MS Access (JDBCReader: Preloading JDBC Driver Class 'net.ucanaccess.jdbc.UcanaccessDriver'
MS Access (JDBCReader: Creating connection using connection string 'jdbc:ucanaccess:///media/something/CFC1-4CC4/Something/DB_sample12090708.mdb' and properties '{jackcessOpener=COM.safe.fme.MsAccessCryptCodecOpener}'
MS Access (JDBCReader: Connected to 'Ucanaccess for access db(Jet) using hasqldb' version 'V2003 [VERSION_4]' using driver 'Ucanaccess' version '3.0.3.1' built against JDBC version '4.0'
MS Access (JDBCReader: Connection class 'net.ucanaccess.jdbc.UcanaccessConnectionis being loaded from '/opt/fme-desktop-2016/plugins/ucanaccess-3.0.3.1.jar'
MS Access (JDBCReader: Column 'jdbc_where_clause' is not present in table 'OWI' and will not be read
MS Access (JDBCReader: Executing SQL: SELECT `UPRN`, `ProDiCoVi`, [other attributes] FROM `OWI`
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f8a1a8a7dfc, pid=8376, tid=140231991601408
#
# JRE version: OpenJDK Runtime Environment (7.0_121) (build 1.7.0_121-b00)
# Java VM: OpenJDK 64-Bit Server VM (24.121-b00 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea 2.6.8
# Distribution: Ubuntu 14.04 LTS, package 7u121-2.6.8-1ubuntu0.14.04.1
# Problematic frame:
# C  [libQtGui.so.4+0x1b7dfc]
#
# 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:
# /media/something/CFC1-4CC4/Something/hs_err_pid8376.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
#   http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
terminate called after throwing an instance of 'int'


Error running translation.
 

 

Has anyone an idea how to get it to work? Or what the actual error is? 

The full log: http://pastebin.com/raw/fLL1cQqi

4 replies

Forum|alt.badge.img+2
  • January 13, 2017
@tka Most Java messages are a red herring and can be ignored. We're working on trying to think them down. Is it possible that this is a workspace you created in FME 2017.0 but you're running in FME 2016.1.3?

 

I think if this issue persists you should open a case with Safe Support or your FME reseller and send them a reproduction package including the Workspace and the FME log file.

 


  • Author
  • January 26, 2017
@MarkAtSafe Thank you, Mark. In this case, it wasn't mere red herring, more a show stopper since the translation broke down. Anyhow, I circumvented the issue by using FME on a Windows machine. I don't know how big the market on Linux is for SafeSoftware but a well-tested, smoothly running, Ubuntu16-ready version of FME would just be a dream come true. ;)

Forum|alt.badge.img+2
  • January 26, 2017
tka wrote:
@MarkAtSafe Thank you, Mark. In this case, it wasn't mere red herring, more a show stopper since the translation broke down. Anyhow, I circumvented the issue by using FME on a Windows machine. I don't know how big the market on Linux is for SafeSoftware but a well-tested, smoothly running, Ubuntu16-ready version of FME would just be a dream come true. ;)
@tka Sorry - I didn't mean to suggest your issue was not of concern and not a real one. Just that the Java messages themselves are very often miss-leading and don't point to the root cause of the problem. So you have to look at what might be triggering the failure.

 


  • Author
  • January 27, 2017
markatsafe wrote:
@tka Sorry - I didn't mean to suggest your issue was not of concern and not a real one. Just that the Java messages themselves are very often miss-leading and don't point to the root cause of the problem. So you have to look at what might be triggering the failure. 

 

No need to apologize; I just couldn't explain to me what (which seems to be cause of failure) ...

 

 

Problematic frame:
# C  [libQtGui.so.4+0x1b7dfc]
... could possibly mean; other than "You have the wrong Qt version". Anyhow, I suggest using Ubuntu 14.04 or Windows altogether to avoid stuff like this.

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings