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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Session recovery on rollback

by timfox

What you're saying is that if you put the message back on the queue (nack it) on rollback then you can't guarantee ordering, since the session could do work in different transactions that could rollback in a different order. However if you're not using XA then it seems to me that order can be maintained, even if you have competing consumers on the same queue, since on rollback you don't need to NACK the message back to the queue (where it could get picked up by a competing consumer), instead you can just recover it locally in the session, i.e. just resubmit it to the onMessage method, in the same way you do with session.recover. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958145#3958145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958145

19 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Session recovery on rollback

by adrian＠jboss.org

Incidently, if that JIRA task was done and being used and the above example was the same session on the same thread, it would DEADLOCK. Step 5 would never complete because step 6 can't happen. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958138#3958138 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958138

19 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Session recovery on rollback

by adrian＠jboss.org

You are still confusing different things. The JMS Session is not the same as the transaction. In fact, with transaction interleaving it is perfectly legal (and more efficient) to do the following which JBossMQ actually supports: 1) Enlist session in tx1 2) receive message 1 (this is in the session, but actually belongs to tx1) 3) delist session 4) Enlist session in tx2 5) receive message 2 (into tx2) 6) commit tx1 (this does NOT commit the session, it commits the transaction, i.e. message 1) Again, there is a test for this in the JBossMQ testsuite. Similarly, these could be different sessions on different threads receiving from the same queue. The idea of the JIRA task is that step 5 would not receive message 2 until step 6 either commits or rollbacks message 1. If it rolls back then step 5 gets message 1. This maintains a GLOBAL ordering across transactions/threads/sessions, something that is not a spec requirement, but some people have asked for. I wouldn't recomend somebody uses this, unless they aren't worried about throughput. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958136#3958136 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958136

19 years, 8 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: JBAOP-87 - Annotation Dependencies

by kabir.khan＠jboss.com

BTW how should we manage the dependency from AOP on the container? jboss-aop.deployer contains the aop stuff jboss-bean.deployer contains jboss-microcontainer.jar I will also need to create a retroed version of the jboss-microcontainer.jar that can be used with the aop JDK 1.4 distribution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958134#3958134 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958134

19 years, 8 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: JBAOP-87 - Annotation Dependencies

by kabir.khan＠jboss.com

I've got this moved out the container on my machine. I'll try to get the javassist stuff working this weekend, and then I'll update the mc snapshot jars in the repository. I've kept the signature of the AnnotationCreator.create method untyped since I'm not sure at this stage if I want to force JDK 1.4 users to have their annotation interfaces implementing org.jboss.lang.Annotation | public static Object createAnnotation(final String annotationExpr, final Class annotation) throws Exception | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958128#3958128 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958128

19 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Session recovery on rollback

by timfox

If it was acceptable for ordering to be lost after rollback that makes my life a lot easier. This JIRA task seems to imply that it is not a requirement of the spec. http://jira.jboss.com/jira/browse/JBAS-2444 Although I don't really understand how it is not a requirement since the spec says that session recovery occurs on rollback, and session recovery maintains the order (if prioriry and expiration are taken out of the equation). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958121#3958121 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958121

19 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Another JBESB Example - Data Transformation

by ddegroff

After creating a new application within JBESB Alpha1, I've documented (as much as possible) the "how-to": http://www.ehealthconnect.net/ehc/jbossesb-transformation-example.pdf Dave View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958113#3958113 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958113

19 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - access control and OpenLDAP

by pedalshoe

We have an access control system with openLDAP. can JBoss Portal use our system? We have a way of controlling what a user has access to, we would like to integrate what we have into JBoss Portal. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958110#3958110 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958110

19 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Session recovery on rollback

by timfox

"adrian(a)jboss.org" wrote : | The implementation in SpySession is overly complicated because there | is no "session thread" which means it has to stop delivery on the | whole connection to guarantee no new deliveries during the recovery. | Make sense. So *somehow* it's necessary to prevent any new messages arriving while recover is being executed. In the same way, It's my understanding that we would need to also prevent any new messages arriving while rollback is being executed. (Since the spec says rollback cause session recovery) Looking at the SpySession code I don't see the connection being stopped while rollback is happening. So it looks like messages could creep in which would be non spec complient. (BTW I'm not criticising the spy code, I'm just trying to make sure we're doing it correctly in messaging :) ) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958105#3958105 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958105

19 years, 8 months

1
0
0 / 0

[Design of JBoss Build System] - Eclipse plugin for Maven versus Maven plugin for Eclipse

by tuomas_kiviaho

mvn eclipse:eclipse is not the only available option to automate eclipse project mapping to pom.xml. The Maven 2.x Plug-in for Eclipse <http://m2eclipse.codehaus.org/> doesn't generate static .classpath entries from pom.xml but instead tries to map the whole pom (and it's parents) as one dynamic classpath variable. "Mavenizing" of a project is merely Maven>Enable from project pop-up menu. The approach is more transparent to the user since modifications to the pom.xml are visible to the user directly. Modifications to the parent pom.xml are noted are noted as well but not instantly. Drawback in this approach is that instead of mapping workspace projects the mapping is currently done to maven repositories. There is work being done to get the pom.xml aftifact resolution to prefer workspace projects over repository artifacts .<http://jira.codehaus.org/browse/MNGECLIPSE-59> By using separate checkout location (complete maven tree model consisting of module & parent relations from SCM) from workspace and picking up preferred projects to workspace as indirect references to the checkout location gives more control over workspace. And the best part is that mvn commands can still be done to the checkout location since it is maven compliant. Non recursive usage of mvn let's you drop part of the tree. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958099#3958099 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958099

19 years, 8 months

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 July 2006