Select to view content in your preferred language

Problem with ArcGISRuntimeSDK for Java on CentOS 6.2 after Installing AMD Catalyst Driver

5999
10
09-16-2014 03:09 PM
JohnHodson
Deactivated User

Hello,

I am working to develop an application on CentOS 6.2 using the ArcGISRunetimeSDK for Java. The application works as expected when the default drivers are used (mesa, I believe), but immediately after installing the latest AMD Catalyst driver for the FirePro V4900 in our system the application core dumps as soon as a view with an ArcGIS map is loaded. This has been tested on five different systems. The systems without the AMD driver work, the systems with it do not. Yesterday I even uninstalled the AMD driver on one of the systems that was not working and the application began to run properly. The configurations of all of the test systems are very similar--if not exactly the same. We plan to deploy the application we are developing to other systems that are currently configured with AMD drivers, too, so a solution to this problem would be very much appreciated.

The console output of the error follows:

16:49:44.684 [JavaFX Application Thread] INFO  c.g.a.c.MapViewControllerImpl - Initializing project progress MAP

Java version : 1.8.0_11 (Oracle Corporation) amd64

Rendering engine : OpenGL

GLX version 1.4

16:49:45.767 [JavaFX Application Thread] INFO  c.g.a.c.TabularViewControllerImpl - Initializing Tabular view

16:49:45.862 [pool-7-thread-1] ERROR com.ggs.asbe.daos.StationDaoImpl - getMinLongitude - No entity found for query

16:49:45.873 [pool-7-thread-1] ERROR com.ggs.asbe.daos.StationDaoImpl - getMinLatitude - No entity found for query

16:49:45.881 [pool-7-thread-1] ERROR com.ggs.asbe.daos.StationDaoImpl - getMaxLongitude - No entity found for query

16:49:45.885 [JavaFX Application Thread] INFO  c.g.a.controllers.MainControllerImpl - Loading Main window

16:49:45.889 [pool-7-thread-1] ERROR com.ggs.asbe.daos.StationDaoImpl - getMaxLatitude - No entity found for query

#

# A fatal error has been detected by the Java Runtime Environment:

#

#  SIGSEGV (0xb) at pc=0x0000003edf32f9df, pid=3821, tid=140132974003968

#

# JRE version: Java(TM) SE Runtime Environment (8.0_11-b12) (build 1.8.0_11-b12)

# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.11-b03 mixed mode linux-amd64 compressed oops)

# Problematic frame:

# C  [libc.so.6+0x12f9df]  __tls_get_addr@@GLIBC_2.3+0x12f9df

#

# 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:

# /opt/asbe/app/hs_err_pid3821.log

#

# If you would like to submit a bug report, please visit:

#   http://bugreport.sun.com/bugreport/crash.jsp

# The crash happened outside the Java Virtual Machine in native code.

# See problematic frame for where to report the bug.

#

Aborted (core dumped)

I have also attached the error report file. A little more system information follows:

Operating system: CentOS 6.2 (Final), 2.6.32-220.el6.x86_64, Gnome 2.28

Graphics Card: AMD V4900 (also tested with V5900)

Any help or suggestions are appreciated.

0 Kudos
10 Replies
WesEverett
Deactivated User

It does the same with RHEL6.  Do you see any reason why it is not working?  Anything we need to add or change?

0 Kudos