Problems JCA JMS inflow issue and tx NotSupported| JBoss.org Content Archive (Read Only)

1 2 Previous Next 22 Replies Latest reply on Jan 20, 2007 1:58 PM by weston.price Go to original post

15. Re: Problems JCA JMS inflow issue and tx NotSupported

timfox Jan 18, 2007 6:33 AM (in response to timfox)

Sorry I meant "calling commit on an XASession" (which is illegal)
Actions
16. Re: Problems JCA JMS inflow issue and tx NotSupported

weston.price Jan 18, 2007 7:55 AM (in response to timfox)

Can you confirm your simple JBM/jPBM test works with the adapter in HEAD? It should be a simple drop in replacement.
Actions
17. Re: Problems JCA JMS inflow issue and tx NotSupported

weston.price Jan 20, 2007 2:21 AM (in response to timfox)

Ok, so here it is in JIRA:

http://jira.jboss.org/jira/browse/JBAS-4001

I have backported the changes to 4.2.x. I will get it into a CP release for 4.0.5 once I figure out the new process.
Actions
18. Re: Problems JCA JMS inflow issue and tx NotSupported

timfox Jan 20, 2007 7:24 AM (in response to timfox)

"weston.price@jboss.com" wrote:
Can you confirm your simple JBM/jPBM test works with the adapter in HEAD? It should be a simple drop in replacement.

Certainly. I am a bit rushed right now, but will get around to this sometime early next week.

http://jira.jboss.com/jira/browse/JBMESSAGING-763
Actions
19. Re: Problems JCA JMS inflow issue and tx NotSupported

weston.price Jan 20, 2007 7:25 AM (in response to timfox)

Not a problem. Again, it is already backported to 4.2. 4.0.5 is next, however, I am not sure if I have to do anything special for the new cummulative patch cycle stuff. The changes to the adapter need to go in regardless of JBM, they offer improvements all around.
Actions
20. Re: Problems JCA JMS inflow issue and tx NotSupported

weston.price Jan 20, 2007 7:36 AM (in response to timfox)

CRAP...now I remember the issue. The problem you were seeing was that in the old code (now 4.0.5) support for handling a RuntimeException in an non specified transaction context had to be done via a SystemProperty. Being that you had not set this, it didn't work. However, I was never happy about having to set something like that to get that behavior. This requirement is removed in the latest code so it's best to go with that anyway.
Actions
21. Re: Problems JCA JMS inflow issue and tx NotSupported

timfox Jan 20, 2007 1:55 PM (in response to timfox)

I have done an initial check, and it seems the problem I had is resolved when using JCA from head :)
Actions
22. Re: Problems JCA JMS inflow issue and tx NotSupported

weston.price Jan 20, 2007 1:58 PM (in response to timfox)

Cool. Again, you can set that system property to get the desired behavior in the 4.0.5 stuff, but I think the approach is at best pretty weak, and downright f*!@ed up at the worst. If you wanted to do this, you would have to add the following to your run.sh or run.conf script

-Dorg.jboss.asf.jms.useold=true

Again, not the best approach and it was added in haste. I would prefer that it died a quick and swift death.
Actions

1 2 Previous Next

Go to original post