August 2006 - jboss-dev-forums - Jboss List Archives

[Design of JCA on JBoss] - Re: XAResourceWrapper for WebSphereMQ XA (JBAS-3183)

by weston.price＠jboss.com

Actually, if we could talk about this a bit more that would be great :-) I am not quite sure how we can make the pad flag resource specific since we aren't generating the Xid. Sorry for my stupidity but I just don't quite remember all of the details we discussed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968734#3968734 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968734

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-410 - Use of JmsXA in non transactional envi

by ovidiu.feodorov＠jboss.com

No need, Clebert. This is what happens: For both JBossMQ and Messaging, the JCA layer creates a JMSManagedConnection instance that delegates to java:/XAConnectionFactory, active JTA transaction or not. If the JTA transaction is active, the XAResource instance (SpyXAResource for JBossMQ, MessagingXAResource for Messaging) is enlisted with the transaction, otherwise it is, obviously, not. The difference in behavior becomes apparent when sending the message. JBossMQ session tries to store the message with its SpyXAConnection's resource manager. The SpyXAResourceManager instance doesn't see any xid (xid is null) so immediately sends the message to the server. (SpyXAResourceManager line 115) Messaging holds the message in its ResourceManager, associating it with a transaction that will never commit. So the difference is in the JMS implementation, not in the JCA layer, which is identical in both cases, as Tim thoughtfully noticed. Now the question is what behavior is correct. Well, the common sense says that there is no active JTA transaction at the time of Session creation, the Session is NOT transacted, so JBossMQ behavior is correct. I would treat the current Messaging behavior as a bug. If you have spec paragraphs to throw at me, go ahead. I am still poring over specs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968731#3968731 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968731

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-410 - Use of JmsXA in non transactional envi

by clebert.suconic＠jboss.com

I'm digging JBossMQ code for this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968729#3968729 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968729

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-410 - Use of JmsXA in non transactional envi

by timfox

Hmmm, I find it strange that JBossMQ has different behaviour since we are using the exact same JCA layer as JBoss MQ. Unless JBossMQ is doing something weird internally like sending messages from an XASession if they haven't been sent when it closes - which is certainly not mandated by the JMS spec. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968712#3968712 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968712

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-410 - Use of JmsXA in non transactional envi

by genman

Let me just point out, that spec or not, you may want to be compatible with the JBossMQ behavior. If you decide against compatibility, you should also provide a non-XA pool at java:/Jms , along with the existing java:/JmsXA . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968710#3968710 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968710

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-410 - Use of JmsXA in non transactional envi

by ovidiu.feodorov＠jboss.com

I am looking at the JCA spec. I'll be back with an answer shortly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968707#3968707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968707

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-410 - Use of JmsXA in non transactional envi

by clebert.suconic＠jboss.com

Just an idea: We could throw an Exception on send if there isn't a transaction opened. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968706#3968706 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968706

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-410 - Use of JmsXA in non transactional envi

by clebert.suconic＠jboss.com

That's the whole point ot JBMESSAGING-410. JBossMQ would send it if you don't have a transaction. If this is the expected behavior we could decide this is not a bug, and that's it. If this is the case I'm cool about that. I'm just getting started, so I can't take that decision. Ovidiu, what you think? Clebert View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968705#3968705 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968705

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-410 - Use of JmsXA in non transactional envi

by timfox

If there is no JTA transaction, there is nothing to enlist, so commit can never be received by the XASession, so the message will never be sent. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968703#3968703 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968703

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-410 - Use of JmsXA in non transactional envi

by clebert.suconic＠jboss.com

My question is when you using JmsXA and not enlist a transaction. if you add this following test to XATransactionTest, the test will hang (as the message was never sent): public void test_JmsXA_NonTransactional() throws Exception | { | Transaction suspended = TransactionManagerLocator.getInstance().locate().suspend(); | | | ConnectionFactory cf = (ConnectionFactory)ic.lookup("java:/JCAConnectionFactory"); | | | Connection conn = cf.createConnection(); | | | | Session session = conn.createSession(false, Session.AUTO_ACKNOWLEDGE); | | MessageProducer prod = session.createProducer(queue); | prod.setDeliveryMode(DeliveryMode.NON_PERSISTENT); | | TextMessage m = session.createTextMessage("message one"); | prod.send(m); | m = session.createTextMessage("message two"); | prod.send(m); | | conn.close(); | | conn = cf.createConnection(); | | session = conn.createSession(false, Session.AUTO_ACKNOWLEDGE); | | MessageConsumer cons = session.createConsumer(queue); | | conn.start(); | | TextMessage rm = (TextMessage)cons.receive(); | assertEquals("message one", rm.getText()); | rm = (TextMessage)cons.receive(); | assertEquals("message two", rm.getText()); | | conn.close(); | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968702#3968702 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968702

17 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2006