WhenServer Agent v4.0.3.0 GA is running we get reoccuring dumps in the application log:
We use MS SQLServer and microsoft JDBC drivers in our application with a tomcat.jdbc.pool under Tomcat7.
[http-bio-80-exec-3] 24 Mar 2015 11:42:45,874 ERROR ADBSessionGrabber - An exception occurred when getting MySQL DB session id.
java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Long
at com.singularity.ee.agent.appagent.services.transactionmonitor.jdbc.vc.a(vc.java:11)
at com.singularity.ee.agent.appagent.services.transactionmonitor.jdbc.sc.b(sc.java:80)
at com.singularity.ee.agent.appagent.services.transactionmonitor.jdbc.f.a(f.java:48)
at com.singularity.ee.agent.appagent.services.transactionmonitor.common.g.a(g.java:468)
at com.singularity.ee.agent.appagent.services.transactionmonitor.common.g.a(g.java:444)
at com.singularity.ee.agent.appagent.services.transactionmonitor.common.g.a(g.java:376)
at com.singularity.ee.agent.appagent.services.bciengine.b.onMethodEnd(b.java:53)
at com.singularity.ee.agent.appagent.kernel.bootimpl.FastMethodInterceptorDelegatorImpl.safeOnMethodEndNoReentrantCheck(FastMethodInterceptorDelegatorImpl.java:476)
at com.singularity.ee.agent.appagent.kernel.bootimpl.FastMethodInterceptorDelegatorImpl.safeOnMethodEnd(FastMethodInterceptorDelegatorImpl.java:400)
at com.singularity.ee.agent.appagent.entrypoint.bciengine.FastMethodInterceptorDelegatorBoot.safeOnMethodEnd(FastMethodInterceptorDelegatorBoot.java:124)
at com.singularity.ee.agent.appagent.entrypoint.bciengine.FastMethodInterceptorDelegatorBoot.safeOnMethodEndNormal(FastMethodInterceptorDelegatorBoot.java:107)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:651)
at org.apache.tomcat.jdbc.pool.PooledConnection.validate(PooledConnection.java:460)
at org.apache.tomcat.jdbc.pool.PooledConnection.validate(PooledConnection.java:394)
at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:775)
at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:619)
at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:188)
at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:128)
at org.springframework.orm.hibernate3.LocalDataSourceConnectionProvider.getConnection(LocalDataSourceConnectionProvider.java:83)
at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446)
at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167)
at org.hibernate.jdbc.BorrowedConnectionProxy.invoke(BorrowedConnectionProxy.java:74)
at com.sun.proxy.$Proxy21.setReadOnly(Unknown Source)
at org.springframework.jdbc.datasource.DataSourceUtils.prepareConnectionForTransaction(DataSourceUtils.java:155)
at org.springframework.orm.hibernate3.HibernateTransactionManager.doBegin(HibernateTransactionManager.java:509)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:372)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)
Thanks,
Lee
oOo
Hi,
We see similar error in other customer environments and could see that the error around this stack trace is already fixed in 4.0.3 version, we request you to ugprade to 4.0.3 or latest 4.x version and see how it goes.
Hope that information helps.
Regards,
Arun