This does seem to be a bug, however it only seems to occur when using a rather
perverse usage pattern which the spring jms template seems to use.
See http://jira.jboss.org/jira/browse/JBMESSAGING-864
and
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019590#4019590
So any people out
Tim,
I know you guys work like crazy, I follow very closely the user and developer
forums, and I greatly appreciate your efforts as I expect to switch to 1.2GA
soon after GA, to benefit from its distributed queues.
My test is now 100% spring free and I had already created a support entry: I
just
Olivier-
The messaging team is currently working 20 hours a day, 7 days a week for out
1.2. release which is due out at the end of the month.
If you can replicate your issue with just JBM then I will try and fit some time
in to look at it in the four hours of the day I have remaining, but I can
I just use the a spring JtaTransactionManager which acts as a TM wrapper that
looks up JBoss UserTx and TM in jndi, and allow consistent syntax when
switching to a spring-specific TM.
I dont know the spring code base by heart but it has to properly call commit on
the jboss resources as I do hav
Well.. we haven't tested with Spring so we've no idea whether it works or not
with Spring.
At the end of the day we don't know what calls Spring is making or whether it
is obeying the XA usage contract.
At first glance it looks like something (Spring?) is not closing sessions.
If you can repli
