Atomikos Forum

Hi All,

I am getting the following error. Happening only recently.
Has anybody encotered and resolved this issue?

regards
Prasad

==
 error creating proxy of connection an AtomikosXAPooledConnection with a SessionHandleState with 0 context(s)
com.atomikos.datasource.pool.CreateConnectionException: an AtomikosXAPooledConnection with a SessionHandleState with 0 context(s): connection is erroneous
        at com.atomikos.jdbc.AtomikosXAPooledConnection.testUnderlyingConnection(AtomikosXAPooledConnection.java:89)
        at com.atomikos.datasource.pool.AbstractXPooledConnection.createConnectionProxy(AbstractXPooledConnection.java:43)
        at com.atomikos.datasource.pool.ConnectionPool.borrowConnection(ConnectionPool.java:135)
        at com.atomikos.jdbc.AbstractDataSourceBean.getConnection(AbstractDataSourceBean.java:289)
        at com.atomikos.jdbc.AbstractDataSourceBean.getConnection(AbstractDataSourceBean.java:341)
        at org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy$LazyConnectionInvocationHandler.getTargetConnection(LazyConnectionDataSourceProxy.java:389)
        at org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy$LazyConnectionInvocationHandler.invoke(LazyConnectionDataSourceProxy.java:364)
        at $Proxy26.prepareStatement(Unknown Source)

==

What changed wrt before, when you were not getting this error?

Thanks

Guy,

apologies for the delayed reply.
Apparently nothing has changed. we did another build and it strated working fine. also, this error seems to strike in a virtual environment when we deploy our application on a vmware virtual machine.

the error I get is something like this.

==
can not initialize AtomikosDataSourceBean javax.naming.NamingException :
Another resource already exists with name XADS-xxx pick a different name.
at com.atomiks.util.IntraVmObjectFactory.java)
==

do we need to configure something differently while deploying on a VM?

Hi,

I am not aware of any VMWare issues like this. This can only happen if multiple datasources are using the same Java VM classloader and have the same uniqueResourceName value... Or if you don't close the datasource in between restarts of the Java application.

HTH

after enabling the logs I saw something like this.

when I test it locally, I see the following logs:

==
atomikos connection proxy for com.informix.jdbcx.IfxXAReusableConnection@ec6b00: calling getAutoCommit...
10-06-13 14:50:01,468 [main] atomikos connection proxy for com.informix.jdbcx.IfxXAReusableConnection@ec6b00: getAutoCommit returning true
==

Please not about autocommit is set to true.

In the instance, where it is not working [deployed application],

==
10-06-21 12:40:35,270 [http-8443-4] atomikos connection proxy for com.informix.jdbcx.IfxXAReusableConnection@4a0b66: calling getAutoCommit...
10-06-21 12:40:35,270 [http-8443-4] atomikos connection proxy for com.informix.jdbcx.IfxXAReusableConnection@4a0b66: getAutoCommit returning false
==

Note that autocommit is set to false. subsequently a call the setAutoCommit is made.

I am seeing if setting the autocommit to true will do the trick.

Regards
Prasad