This forum is for user problems related to
JCA (j2ee connector architecture) and ResourceAdapters.
It is also the support forum for JBoss's JTA implementation, i.e. the transaction
manager

A guide to getting your question answered http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp

The WIKI can be found here: http://www.jboss.org/wiki/Wiki.jsp?page=JBossJCA
The FAQ can be found here: http://www.jboss.org/wiki/Wiki.jsp?page=FAQJBossJCA

Enable TRACE logging to look for funny behaviour, this is configured
in conf/log4j.xml:

e.g. for general problems

<category name="org.jboss.resource">
 <priority value="TRACE" class="org.jboss.logging.XLevel"/>
</category>

Logging the transaction manager can also be useful:

<category name="org.jboss.tm">
 <priority value="TRACE" class="org.jboss.logging.XLevel"/>
</category>

e.g. for problems with the jdbc resource adapter

<category name="org.jboss.resource.adapter.jdbc">
 <priority value="TRACE" class="org.jboss.logging.XLevel"/>
</category>

e.g. for problems with the jms resource adapter

<category name="org.jboss.resource.adapter.jms">
 <priority value="TRACE" class="org.jboss.logging.XLevel"/>
</category>

e.g. for problems with the connection manager/pooling

<category name="org.jboss.resource.connectionmanager">
 <priority value="TRACE" class="org.jboss.logging.XLevel"/>
</category>

But don't dump your whole log/server.log here. Nobody will read it.

If you suspect a deadlock or hang post a thread dump:
On unix ctrl-\ or kill -3 <jboss-pid>
On windows ctrl-break