Could not find new XAResource to use for recovering non-serializable XAResource

jensmander Oct 25, 2010 6:11 AM

Hi,

I already read a lot of this "problem" but I couldn't solve it right now ;(

Every 130sec. this message is prompted by the server (JBossAS 5.1):

Could not find new XAResource to use for recovering non-serializable XAResource < 131075

I am using two xa-datasources (PostgreSQL) and after querying either one of them it get the shown message.

I read something about setting up "max_prepared_transactions" in the postgres config what I already did to get the 2-Phase commit protocol running.

What I didn't get right now is if this is a bug in JBoss5.1 repectively the JTA-implementation or if I have to fix this issue. I didn't notice any problems in my application yet but I have some pain by putting it into production with such messages every 2 min.

Any ideas?

Best regards, Sascha

1. Re: Could not find new XAResource to use for recovering non-serializable XAResource

wdfink Oct 26, 2010 4:02 AM (in response to jensmander)

This mean that after a failure the transaction manager try to find a connector to recover (normally rollback) a transaction with a known id.

I have this behaviour after restarting JBoss due to a JCA connector which not support this.
In most cases the DB or backend will roll back the transaction itself, so the data will not become inconsistent.
See also https://jira.jboss.org/jira/browse/JBTM-353

If you are sure you should delete <jboss config>/data/tx-object-store to remove all known transactions.
Actions