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

by adamw

Hello, I have just commited portal 2.4 binaries. To run it, best delete the current installation and do a new maven install && maven all. Many things aren't working yet, the full list of builds that are turned off is localized in the "TODO" file. So if you want to work on portlets or sth like that, don't update yet. Also, clean your database or migrate it using the migration webapp (the migration must happen before running portal 2.4 for the first time - I haven't tried it tho ;) ) -- Adam View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968777#3968777 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968777

19 years, 3 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

timfox wrote : As I said earlier in this thread, this is a religious argument and I don't think we'll find any conclusion in the JMS spec, since it is sparse at the best of times, especially the XA stuff. Right. Do you agree that analyzing the behavior of the reference implementation is the next step? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968776#3968776 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968776

19 years, 3 months

1
0
0 / 0

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

by timfox

"ovidiu.feodorov(a)jboss.com" wrote : | | If there is no distributed transaction, then there can be no "prepare and commit work on the transaction", hence the session is non-transactional. That is one solution, but it isn't a logical necessity. Other conforming implementations would be that messages (or acks) are stored up in the session, until work is started in a transaction, then the previous work done is transferred into the transaction. In fact, a similar conversion already happens in certain situations: See ResourceManager::convertTx(LocalTx anonXid, Xid xid) throws XAException Which converts work done outside a global tx into work done inside the global tx. As I said earlier in this thread, this is a religious argument and I don't think we'll find any conclusion in the JMS spec, since it is sparse at the best of times, especially the XA stuff. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968774#3968774 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968774

19 years, 3 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

timfox wrote : | I am merely saying that that the JBossMQ implementation adds *extra* semantics not specified in the spec. | I agree with that, but with the observation that this "extra" hints at common sense. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968772#3968772 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968772

19 years, 3 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

Of course, this is a conclusion inferred from the specification, and not the specification itself, which seems to be incomplete in this area. So, given the circumstances, your guess is as good as mine, and that's why I say to go and see how the reference implementation behaves. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968771#3968771 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968771

19 years, 3 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

JMS 1.1 Specification Section 8.5 XA Session: anonymous wrote : | XASession provides access to what looks like a normal Session object and a javax.transaction.xa.XAResource object which controls the session?s transaction context. The functionality of XAResource closely resembles that defined by the standard X/Open XA Resource interface. | | An application server controls the transactional assignment of an XASession by obtaining its XAResource. It uses the XAResource to assign the session to a distributed transaction, prepare and commit work on the transaction, and so on. | | An XAResource provides some fairly sophisticated facilities for interleaving work on multiple transactions, recovering a list of transactions in progress, and so on. A JTA aware JMS provider must fully implement this functionality. This could be done by using the services of a database that supports XA, or a JMS provider may choose to implement this functionality from scratch. A client of the application server is given the XASession?s Session. Behind the scenes, the application server controls the transaction management of the underlying XASession. | | It is important to note that a distributed transaction context does not flow with a message; that is, the receipt of the message cannot be part of the same | transaction that produced the message. This is the fundamental difference between messaging and synchronized processing. Message producers and | consumers use an alternative approach to reliability that is built upon a JMS provider ?s ability to supply a once-and-only-once message delivery guarantee. | | To reiterate, the act of producing and/or consuming messages in a Session can be transactional. The act of producing and consuming a specific message across different sessions cannot. | anonymous wrote : | | | | This is the letter of the spec, and nothing else of substance is specified about XASession throughout. The phrase that I find interesting is the following: "An application server controls the transactional assignment of an XASession by obtaining its XAResource. It uses the XAResource to assign the session to a distributed transaction, prepare and commit work on the transaction, and so on." | | | | Zooming again, "It uses the XAResource to assign the session to a distributed transaction [...]". | | | | If there is no distributed transaction, then there can be no "prepare and commit work on the transaction", hence the session is non-transactional. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968770#3968770 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968770

19 years, 3 months

1
0
0 / 0

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

by timfox

Here's the reference: JMS 1.1 spec Section 8.5: "An application server controls the transactional assignment of an XASession by obtaining its XAResource. It uses the XAResource to assign the session to a distributed transaction, prepare and commit work on the transaction, and so on." View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968769#3968769 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968769

19 years, 3 months

1
0
0 / 0

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

by timfox

"ovidiu.feodorov(a)jboss.com" wrote : | None of us was able to produce spec paragraphs confirming or proving invalid our assumptions. | I haven't made any assumptions or conjecture over and above what the JMS spec says should be the behaviour of an XASession. I am merely saying that that the JBossMQ implementation adds *extra* semantics not specified in the spec. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968768#3968768 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968768

19 years, 3 months

1
0
0 / 0

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

by timfox

"ovidiu.feodorov(a)jboss.com" wrote : | XASession is supposed to be transactional only if its XAResource is enrolled in a transaction. | Really? Can you point me to the place in the JMS spec that says this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968767#3968767 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968767

19 years, 3 months

1
0
0 / 0

[Design of JBoss Labs] - Re: Productization metrics for JEMS Matrix

by unibrew

Ok. So, Pawel could you make a list of new things which you need in project.xml ? Some time ago I sent you all a specification of new project.xml. Please check it and list what do you want to add. Cheers ------------------------ Ryszard Kozmik JBoss Labs Team View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968761#3968761 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968761

19 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2006