"oglueck" wrote : This happens randomly and rarely on a production system.
It then becomes difficult to identify the problem , the only option I can think right now
is to simulate the test on the development system .
If you are able to do it there with the TRACE logging enabled for JCA and TM it would be
easy to SPOT the cause.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106999#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...