CXFServletExt#doPost generate 500 when INSERT to DB2

We are currently using elastic-apm-agent-0.6.2.jar which works fine, collects data from our postgres and DB2 calls.

We wanted to try a new agent and installed, elastic-apm-agent-0.7.0-20180910.093339-71.jar, which resulted in a lot off 500’s

How and why I cant actually understand from reading the logs. I just see that before and after the result is totally different

Response-Code: 500
Encoding: UTF-8
Content-Type: text/xml
Headers: {}
Payload: <env:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault xmlns:soap="http://schemas
.xmlsoap.org/soap/envelope/">
   <faultcode xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/">ns1:Server</faultcode>
   <faultstring>Unexpected error</faultstring>
   <detail>
      <LoginExceptionData xmlns="http://our-domain.se/our-login-path/data/v1_0" xmlns:ns2="http://our-domain.se/our-common-element-1/data/v4_6" xmlns:ns3="http://our-domain.se/our-common-element-2/data/v4_6">
         <Errormessage>(class: com/ibm/db2/jcc/am/CallableStatement, method: execute signature: ()Z) Illegal type in constant pool</Errormessage>
      </LoginExceptionData>
   </detail>
</env:Fault></env:Body></env:Envelope>

In the APM part of elastiic we did get two new requests MetricsStreamServlet#doGet CXFServletExt#doPost

It is the CXFServletExt#doPost that returns 500, it seems to be at time of INSERT

/Fredrik

[felixbarny]

I was wrong when saying the db2 driver was compiled for Java 5. It is actually compiled for Java 2(!).

When trying to instrument the class, I get this error from Byte Buddy:

java.lang.IllegalStateException: Cannot write type to constant pool for class file version Java 2
	at net.bytebuddy.dynamic.scaffold.TypeWriter$Default$ValidatingClassVisitor$Constraint$ForClassFileVersion.assertTypeInConstantPool(TypeWriter.java:2622)
	at net.bytebuddy.dynamic.scaffold.TypeWriter$Default$ValidatingClassVisitor$Constraint$Compound.assertTypeInConstantPool(TypeWriter.java:2764)

Not quite sure though why that affects your application. I would have assumed that this class is just not being instrumented so there should actually be no harm besides the fact that the JDBC instrumentation does not work.

I have also tried the more recent version (db2jcc4), which is compiled with the byte code level 50 (Java 6) and this error did not occur. So updating your JDBC driver should fix this.

[lk95jofr]

The only reason I think it relates to -Delastic.apm.application_packages is that we specify that package, so no really good reason 😃 Unfortunately I can’t do that kind of test now (db2jcc4), it will be to much impact on our system. If you think that will solve it I recommend you to close this and when I get to that change I will notify you.