Enabling Syslog Logging Results In an UnsatisfiedLinkError to be Reported for libutilforsyslog.so: wrong ELF class: ELFCLASS32 (Doc ID 1149785.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle GlassFish Server - Version 2.1 and later
Linux x86-64
***Checked for relevance on 4-Sep-2014***

Symptoms

Configuring the Application Server to use the operating system's syslog logging facility on a 64-bit Linux platform results in the following error being reported when starting the instance:

[#|2010-06-08T11:11:38.183-0400|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;|java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
Caused by: java.lang.UnsatisfiedLinkError: /opt/glassfish/lib/libutilforsyslog.so: /opt/glassfish/lib/libutilforsyslog.so: wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch)

Changes

The problem can only be encountered on 64-bit installation of GlassFish on Linux platforms when the syslog logging option is enabled, either through the asadmin command line or the web based Administration console.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms