XAConnectionImpl has no current tx!

[crowleym]

I have inherited a legacy application on JBoss 2.4.8 Jetty 4.0.4

Unfortunately there are no plans to upgrade.

In the server.log I get a "XAConnectionImpl@xxxxx has no current tx!" every minute. This message may or maynot be preceeded / followedby "no xares in rms for con org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@xxxxx"

I have checked the JBoss source and both these messages are warnings. I have checked the FAQs, WIKI, Forums etc. to locate the source of the problem without much luck.

Questions:

What is JBoss actually trying to tell me?
Should I be worried about this?
Is there some config settings that need tweaking?
Is this constant writing to the log going to degrade performance?

Thanks in advance.

Below is a snapshot of the log.

2005-01-17 12:05:28,828 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@5637e7 has no current tx!
2005-01-17 12:05:28,875 [XAConnectionFactory] no xares in rms for con org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@64b09c
2005-01-17 12:05:28,937 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@5637e7 has no current tx!
2005-01-17 12:05:32,000 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@5637e7 has no current tx!
2005-01-17 12:05:32,296 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@5637e7 has no current tx!
2005-01-17 12:05:32,375 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@5637e7 has no current tx!
2005-01-17 12:05:35,546 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@2f0d54 has no current tx!
2005-01-17 12:05:35,640 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@2f0d54 has no current tx!
2005-01-17 12:05:45,046 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@54177e has no current tx!
2005-01-17 12:05:46,109 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@5637e7 has no current tx!
2005-01-17 12:05:46,203 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@5637e7 has no current tx!
2005-01-17 12:06:08,562 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@1946c2 has no current tx!
2005-01-17 12:06:18,578 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@5637e7 has no current tx!
2005-01-17 12:06:21,015 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@2f0d54 has no current tx!
2005-01-17 12:06:21,250 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@1946c2 has no current tx!
2005-01-17 12:06:23,125 [XAConnectionFactory] XAConnectionImpl: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@1946c2 has no current tx!

[adrian.brock]

You are unlikely to get much help for that version of JBoss, very few people
use it anymore. We at JBoss still support it for paying customers only.

If you read the code:
http://cvs.sourceforge.net/viewcvs.py/jboss/jbosspool/src/main/org/jboss/pool/jdbc/xa/Attic/XAConnectionFactory.java?annotate=1.2.2.8

You will see it is warning you that you are trying to close an XAConnection
but the connection was never (or is no longer) enlisted in a transaction.
Probably because there is no active transaction?

[crowleym]

Adrian

Thanks for the response.

I will use this statement to see if I can force an upgrade, its ridiculous that we are using such an old version on what my company terms an critical project.

Cheers.