APM java agent on JBoss 6

Shaoranlaos · August 13, 2018, 5:27am

Hello all,

i have problems to use the apm-java-agent within a jboss6 application server. I know this server isn't listed in the officaly supported webservers, but i hope someone can help.
The problem lies probably not with the apm-java-agent itself but with the way i integrated the agent.

I can add the java agent to the start configuration of the jboss server and it instruments the parts that should be instrument (JDBC and Servlet container).

The problem comes when i try to call a url from an app that is deployed in the jboss 6 server. With a call there is always a NoClassDefFound Error in the Logs for the Elastic APM Classes. But this is only the case for the JDBC Span, i get a transaction for this request in the apm server.

gist.github.com

https://gist.github.com/Shaoranlaos/5740cd106d6f2ed3e4b0cadb5435292e

gistfile1.txt

[org.jboss.resource.connectionmanager.TxConnectionManager] (http-127.0.0.1-8080-4) Connection error occured: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@1a4fe5b[state=NORMAL mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@722ac4 handles=1 lastUse=1533800189200 permit=true trackByTx=true mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@a3421f context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@136608a xaResource=org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource@b68581 txSync=null]: javax.resource.spi.ResourceAdapterInternalException: Unexpected error
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.broadcastConnectionError(BaseWrapperManagedConnection.java:411) [:6.1.0.Final]
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.connectionError(BaseWrapperManagedConnection.java:387) [:6.1.0.Final]
	at org.jboss.resource.adapter.jdbc.WrappedConnection.checkException(WrappedConnection.java:879) [:6.1.0.Final]
	at org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:257) [:6.1.0.Final]
	at com.xfab.drs.lot_transport.service.DBUtils.getTrolleynameByUsedBy(DBUtils.java:632) [:]
	at com.xfab.drs.lot_transport.service.TransportService.getTrolleyByIP(TransportService.java:90) [:]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.8.0_162]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [:1.8.0_162]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.8.0_162]

This file has been truncated. show original

I have set the java agent argument in the run.conf.bat

set "JAVA_OPTS=%JAVA_OPTS% -javaagent:U:\Projects\ElkStack\apm\elastic-apm-agent-0.6.1.jar"

I also tried to include the agent jar in the classpath but that was not helpfull (server not starting).

felixbarny · August 13, 2018, 7:47am

Hi and thanks for the report!

I'm afraid there is not easy fix or workaround for this. The problem lies in the way JBoss loads classes.
But I'll look into that problem and see how easy it is to add support for JBoss.

Could you tell me the exact version you are using?

Thanks,
Felix

Shaoranlaos · August 13, 2018, 8:04am

We are using jboss 6.1.0 (I known not the newest version )
apm-agent: 0.6.1
Elastic Stack (ES+Kibana+APM-Server): 6.2.4

felixbarny · August 14, 2018, 10:20am

Is JBoss 6.1.0 Java 7 compatible? I could not find information about that, but I think it might not be. The Java agent only supports Java 7+ applications.

Shaoranlaos · August 14, 2018, 10:53am

don't know if it is officialy supported but when i use a JVM Version 7 it starts and the applications are working
(can't say if that is true for all features)

edit: https://access.redhat.com/articles/111663
here is till java 7 for jboss 6.1

felixbarny · August 14, 2018, 12:00pm

But that page is about JBoss EAP, the enterprise version of JBoss. JBoss AS is the community version and is called WildFly as of version 8. I could not find any information about JBoss AS Java compatibility so far

system · September 4, 2018, 8:00am

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.