[jboss-dev-forums] [Design of JCA on JBoss] - Re: XAExpectionUnitTestCase Failures/JBossTS/JBoss 4.2

[weston.price@jboss.com]

anonymous wrote : 
  | Now the explanation is over, what is the exact problem? 
  | 

I explained this already. 

anonymous wrote : 
  | The tests require the failure to occur in the matchManagedConnections method. When the test originally runs, the pool is empty. As a result, a connection is successfully created and enlisted/delisted in the tranasction and returned to the pool. 
  | 
  | The second attempt to acquire the connection fails in the match and the connection is destroyed. Howerver, JBossTS rightfully 'remembers' this guy and when JBossTS attempts to finish the txn protocol the connection has already been destroyed causing the failure. 
  | 
  | 

Basically, JBossTS is attempting to complete the XA protocol on a resource that has already been destroyed which is causing the failure presented in the JIRA issue. The tests itself, as you point out, is designed to make sure that the correct behavior occurs when a match in the managed connection fails. However, as is often the case, it has turned up this other issue.

When you say

anonymous wrote : 
  | There has been some debate in the past on whether we should disable 
  | interleaving by default since most XAResources don't support it. 
  | This includes all xa datasources that I've come across which is why 
  | their examples disable it. 
  | 

This is basically what I am proposing since the default setting to allow for interleaving seems to cause problems with JBossTS and XAResources. 

My plan was to enable <track-connection-by-tx> by default for XA resources, and force it to be explicitly enabled for resources where this makes sense (ie JMS resources). 






View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006848#4006848

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006848