Currently, people are having a tough time figuring out how to correct this error when their apps hit it while running inside of JBossAS:

21:31:10,147 WARN oggerI18N om.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa om.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa Could not find new XAResource to use for recovering non-serializable XAResource

For examples of the types of questions people are asking (yes, I was one of them :

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146138&start=0&postdays=postDays&postorder=postOrder&highlight=highlight
http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=78&t=004053
http://www.nabble.com/JBoss-Integration---recovering-XAResource-td20035573.html
http://forums.java.net/jive/thread.jspa?messageID=254647

This talks about the problem, but nothing specifically addresses how to actually fix the problem: http://www.jboss.org/community/docs/DOC-12463

This comes close - but it mentions Messaging specific things, so it is not clear how you do this for your own JDBC data sources: https://www.jboss.org/community/docs/DOC-12826

This JIRA is to request that our documentation specifically address this problem and provide explicit hints as to how to fix it. Mention things like:

1) the existance of the Oracle and generic JNDI recovery modules, but how they are not configured/activated out-of-box
2) how to edit jbossjta-properties.xml to configure those modules with the JDBC URL/JNDI URI and db user/pass
3) how to add the recovery modules in jbossjta-properties.xml

I talk about how I plan to solve this in that first forum post linked above - that could be used as an example for the kind of docs I was looking for. Even if all this JIRA does is add a commented section in jbossjta-properties.xml, that would go a long way in helping solve this problem for people without them resulting to hair pulling or jumping off bridges.