November 2008 - jboss-dev-forums - Jboss List Archives

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Reimplementing ClassPools for AS

by adrian＠jboss.org

The osgi stuff is anything that does not use import-all=true, export-all or uses delegates/requirements/capabilities I don't think you'll find tests that only test legacy rules (except possibliy the "old" tests). In general the tests are aimed at testing an area (e.g. different configs of parent domains) rather than a single use-case (e.g. there are no import-all=true tests they are mixed in with import-all=false tests in the same area, e.g. loading resources). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186373#4186373 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186373

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA resource and setting the timeout

by timfox

Ok, from a messaging POV the simplest thing for us to do would be to rollback and remove the tx branch on timeout. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186371#4186371 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186371

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA resource and setting the timeout

by jhalliday

The transaction manager will pass on any transaction level timeout information to the resource manager, but it's up to the RM to decide what, if anything, to do with that information. Since the TM will drive a transaction timeout itself anyhow, the RM does not really need to do anything proactive with the information. It's only worthwhile if you don't trust the TM to come along and rollback the branch in a timely manner. That can happen if the TM and RM are running as separate processes and the TM crashes, but it's not common. The utility really depends on your locking model and other resource (in the sense of RAM/disk etc) usage constraints. If releasing resources promptly is important to you then by all means put in your own rollback processing. Otherwise just implement getter/setter for API compliance and do nothing with the information. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186364#4186364 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186364

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA resource and setting the timeout

by timfox

"jhalliday" wrote : | So your options are: keep some meta data around after the timeout, so that you can reply 'rollback only' | If we keep some meta data lying around, we may as well just keep the transaction branch and not roll it back. At least that would give the tx mgr the opportunity to commit at some time too. It seems to me timing out without being able to delete the branch state in the RM seems a bit pointless. anonymous wrote : | , or throw away everything and reply 'unknown tx id'. | Seems sensible. At least then we can delete the state. anonymous wrote : | BTW, what's the perceived advantage to you in implementing timeouts at the resource level, given that users will (hopefully) set an overall tx timeout interval if they want one? Set and getTransactionTimeout are on the xaresource API so would it's my understanding they would be called by the transaction manager?? If the tx mgr does decide to call them, then it's my assumption that we need to implement them in a way that doesn't break anything. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186362#4186362 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186362

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA resource and setting the timeout

by jhalliday

The XA spec has this to say on the matter: "An RM can mark a transaction branch as rollback-only any time except after a successful prepare. A TM detects this when the RM returns a rollback-only return code. An RM can also unilaterally roll back and forget a branch any time except after a successful prepare. A TM detects this when a subsequent call indicates that the RM does not recognise the XID. The former technique gives the TM more information. So your options are: keep some meta data around after the timeout, so that you can reply 'rollback only', or throw away everything and reply 'unknown tx id'. It's up to the tm to deal with either of those cases. I don't off the top of my head know how well JBossTS will respond to either of them. I'm not aware of any major RM that uses either, so I suspect we'll run into seldom exercised corner cases. BTW, what's the perceived advantage to you in implementing timeouts at the resource level, given that users will (hopefully) set an overall tx timeout interval if they want one? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186357#4186357 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186357

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA resource and setting the timeout

by ataylor

The XA spec from the open group says:, " for a commit and prepare: the resource manager did not prepare or commit the work, upon return the resource manager has rolled back the branch and has released all held resources. the value XA_RBTIMEOUT is returned when the work took too long" I guess this is the way to handle it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186354#4186354 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186354

17 years, 1 month

1
0
0 / 0

[Design of JBoss Deployment Framework] - Re: SAR Deployment Deployers Ordering

by alesj

"richard.opalka(a)jboss.com" wrote : I'd like to see the same deployment order of nested .war vs. standalone .war? How could we ensure this Ales? | See how we do it for EARStructure in ear-deployer-jboss-beans.xml. --> comparator setting Try doing the same for JARStructure (that's the structure that handles .sar). Or use custom jboss-structure.xml in your .sar (see examples of this in Deployers project), setting the comparator attribute on context element. Note: this requires deployers 2.2.0-SNAPSHOT, as I've just added this comparator attribute :-) - https://jira.jboss.org/jira/browse/JBDEPLOY-120 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186353#4186353 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186353

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - XA resource and setting the timeout

by ataylor

Currently in JBM 2 we don't support setting the timeout on an XA Session. Since neither the JTA or XA specs define what a 'timeout' means we need to decide what the semantics of a timeout are with regard to an XA Session. A simplistic solution would be to roll back the tx and remove it from the Resource Manager but i'm not sure as to what effect this would have with the tx manager. Maybe one of the tx gurus could comment on what they think the expected semantics are! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186352#4186352 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186352

17 years, 1 month

1
0
0 / 0

[Design of JBoss Deployment Framework] - Re: SAR Deployment Deployers Ordering

by richard.opalka＠jboss.com

"alesj" wrote : | But that shouldn't affect deployers order, only deployment order. | You're right, this is better said. The deployment order has changed not deployers order. "alesj" wrote : | Although with dependencies done right, this shouldn't matter anyway. ;-) | So it is expected that .sar archive (defining e.g. custom MC beans) should define dependency on other MC beans to ensure correct deployment order of such .sar? I'm asking because I'd like to deploye simple .sar archive without MC beans containing just e.g. .war archive only). I'd like to see the same deployment order of nested .war vs. standalone .war? How could we ensure this Ales? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186348#4186348 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186348

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Behaviours of Ordering Group with scheduled delivery and DLQ

by gaohoward

Scheduled Messages Currently, Ordering group doesn't suppport scheduled messages. Although technically possible, in practical use these two features shouldn't be used together. Because in some sense they are functionally conflict. Using scheduled delivery meaning you want each of such messages delivered at certain point of time in future, namely those messages must be delivered in the order determined by their scheduled times. On the other hand ordering group requires messages to be delivered in the order of sent sequence. DLQ/ExpiryQueue If a message of an ordering group is 'dead' or expired, it goes to the corresponding DLQ or ExpiryQueue and the message will be ACKed. Ordering Groups treat those messages are correctly delivered and completed when controling the ordering group delivery. Therefore, the consumers would see some message 'hole's during the receiving of ordering group messages. The 'hole's won't prevent their succeeding messages from delivering. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186334#4186334 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186334

17 years, 1 month

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 November 2008