March 2007 - jboss-dev-forums - Jboss List Archives

[Design of JCA on JBoss] - Re: No LastResource gambit for non-xa MDB

by weston.price＠jboss.com

Right, but that's for the older version (AFS/StdServerSession) and is basically giving a warning about using non XA. The JCA adapter simply assumes that if you are not using an XAConnectionFactory, or you have chosen the madness option (ie BMT, CMT/NotSupported) that the local API will be used solely to support redelivery. However, the problem I see is that the interceptor will suspend the transaction prior to onMessage being invoked in the case of BMT and NotSupported. As result, the DB work being done is not going to effect the overall outcode of the Tx because the underlying XA connection will never be enlisted. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026685#4026685 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026685

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: No LastResource gambit for non-xa MDB

by weston.price＠jboss.com

Ok, this will change things somewhat as we need to 1)Wrap with some new LocalXAWrapper that can use the Local JMS transaction API where appropriate. 2)Enlist In some ways it will make the code cleaner being that everything will be hidden behind the wrapper and the LocalTxDemarcation strategy stuff can pretty much dissapear. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026684#4026684 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026684

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: No LastResource gambit for non-xa MDB

by adrian＠jboss.org

We currently print a warning about this at deployment time: | else if (destination instanceof Queue && con instanceof XAQueueConnection) | { | xaSes = ((XAQueueConnection)con).createXAQueueSession(); | ses = ((XAQueueSession)xaSes).getQueueSession(); | } | else if (destination instanceof Topic && con instanceof TopicConnection) | { | ses = ((TopicConnection)con).createTopicSession(transacted, ack); | | HERE | | log.warn("Using a non-XA TopicConnection. " + | "It will not be able to participate in a Global UOW"); | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026682#4026682 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026682

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: No LastResource gambit for non-xa MDB

by adrian＠jboss.org

No this is for CMT (and BMT/NotSupported with madness=true :-). The correct protocol is last resource gambit (assuming MDB uses DB): 1) Prepare DB (vote ok) 2) Commit JMS (session.commit()) 3) Commit DB (two phase if 2 works otherwise rollback) The current protocol for nonXA JMS is "transaction observer" - which is much weaker that LRG, we can't stop the DB from committing when jms doesn't commit. | tx.commit(); | if (committed) | session.commit(); | else | session.rollback(); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026679#4026679 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026679

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Lifecycle aspects revisited

by adrian＠jboss.org

I'm saying we should be able to intercept other contexts events, e.g. JMX events which isn't a KernelControllerContext it is a ServiceControllerContext. Look at the interface I mentioned. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026673#4026673 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026673

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: No LastResource gambit for non-xa MDB

by weston.price＠jboss.com

In other words, it's a *hack* to support the strange requirement of redelivery in the case of a BMT or NotSupported onMessage. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026672#4026672 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026672

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: No LastResource gambit for non-xa MDB

by weston.price＠jboss.com

Do we really want to do this on the receipt? The receipt of the message, if using Local transactions really should be independent of the Global transaction as it is only used to support rolling back a message in the case of a RuntimeException thrown from the listener. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026671#4026671 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026671

19 years, 1 month

1
0
0 / 0

[Design of JBossXB] - Re: Cleaning up the jbossxb projects

by adrian＠jboss.org

The annotation stuff is based on the MC's ClassInfo abstraction so it is not a trivial integration (given that the container project where this lives also depends on JBossXB). It might have to wait until we split up the MC build? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026670#4026670 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026670

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - No LastResource gambit for non-xa MDB

by adrian＠jboss.org

If the MDB uses a connection factory that is not XA, it drives the transaction, but uses an unlinked JMS local tx commit() We should really be wrapping this in a pretend XAResource like LocalXAResource in JCA that is tagged with LastResource so it can take part in the "last resource gambit". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026667#4026667 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026667

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Graphic Installer for Messaging

by alex.pinkin＠jboss.com

we still need to cover use case when user already has AS 4.x installed, and just wants to update it with Messaging. So it would be nice to have a standalone messaging installer as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026653#4026653 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026653

19 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2007