The relevant bits of the JCA spec are:
JCA 1.5 spec:
Figure 6-7 (page 6-43)
7.6.5 "Scenario: Connection Close and JTA Transactional Cleanup" (page 7-26)
Figure 7-8 (page 7-28)
JCA 1.6 spec:
Figure 6-7 (page 6-41)
7.6.5 "Scenario: Connection Close and JTA Transactional Cleanup" (page 7-24)
Figure 7-8 (page 7-26)
A slice of the log summary showing that the the RA is sending connection close notification but jboss is not responding (as required) by delisting the resource:
[...]
out:MessageListener.onMessage(genericStreamMessage0) #1 @1361560697008..1361560702586
in:wlxaQueueConnectionFactory0.createConnection() -> wlConnection0 #1 @1361560698037..1361560700740
out:ConnectionManager.allocateConnection(wlManagedXAQueueConnectionFactory0,connectionRequestInfoImpl0) -> wlConnection0 #1 @1361560698093..1361560700687
in:wlManagedXAQueueConnectionFactory0.createManagedConnection(null,connectionRequestInfoImpl0) -> managedConnectionImpl0 #1 @1361560698194..1361560699457
[...]
[...]
in:managedConnectionImpl0.getXAResource() -> xaResourceWrapper2 #1 @1361560699619..1361560699675
[...]
in:xaResourceWrapper2.start(xid3,2097152) #6 @1361560700092..1361560700275
[...]
[...]
[...]
in:wlConnection0.close() #1 @1361560702160..1361560702546
[...]
out:ConnectionEventListener.connectionClosed([...]) #1 @1361560702423..1361560702503
out:MessageEndpoint.afterDelivery() #4 @1361560702595..1361560702930
[...]
[...]
I.e., immediately after the "out:ConnectionEventListener.connectionClosed" call (and with an additional level of indent) there should be an "in:xaResourceWrapper2.end" call, but the app-server is not calling XAResource.end as required.