My Oracle Support Banner

ODI 11g "java.lang.NoSuchFieldError: TRACE" Connectivity Issue with JBoss JMS Queue (Doc ID 2307804.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Data Integrator - Version and later
Information in this document applies to any platform.


In an ODI 10G environment, a JMS Queue Data Server was configured and it successfully connects with a JMS Queue in a JBoss installation (version 5.1.2).

After upgrading the environment from ODI 10g to ODI 11g, the JMS Queue Data Server Connection (with the same JBoss) is not working.

When testing the connection with Local/No Agent or with a Standalone Agent, the below error occurs:

[2017-09-06T04:01:08.164+01:00] [] [ERROR] [ODI-1131] [] [tid: <TID>] [ecid: <ECID>] Agent <AGENT_NAME> encountered an error: ODI-1274: Agent Exception Caused by: TRACE[[
ODI-1274: Agent Exception
Caused By: java.lang.NoSuchFieldError: TRACE
  at org.jboss.logging.Log4jLoggerPlugin.trace(
  at org.jboss.logging.Logger.trace(
  at org.jboss.remoting.serialization.SerializationStreamFactory.<clinit>(
  at org.jboss.invocation.unified.interfaces.JavaSerializationManager.register(
  at org.jboss.invocation.unified.interfaces.JavaSerializationManager.register(
  at org.jboss.invocation.unified.interfaces.JavaSerializationManager.<clinit>(
  at java.lang.Class.forName0(Native Method)
  at java.lang.Class.forName(
  at org.jboss.invocation.MarshalledInvocation.<clinit>(
  at java.lang.Class.forName0(Native Method)
  at java.lang.Class.forName(
  at org.jboss.ha.framework.server.HARMIServerImpl_Stub.class$(Unknown Source)
  at org.jboss.ha.framework.server.HARMIServerImpl_Stub.<clinit>(Unknown Source)
  at sun.misc.Unsafe.ensureClassInitialized(Native Method)
  at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(
  at sun.reflect.ReflectionFactory.newFieldAccessor(
  at java.lang.reflect.Field.acquireFieldAccessor(
  at java.lang.reflect.Field.getFieldAccessor(
  at java.lang.reflect.Field.getLong(
  at Method)

The corresponding JBoss JARs files have been placed into ODI 11g classpath (oracledi/agent/drivers or userlib location) however, the issue is the same.




To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.