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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-1006 - Throwing exception when failover fail

by clebert.suconic＠jboss.com

There is one problem with that though... Suppose a connection has one session, two consumers, consumerA, consumerB... one on each queue... ConsumerA will failOver OK, while ConsumerB won't recover acks. Should we invalidate the whole connection... closing also ConsumerA... or should we invalidate only ConsumerB? I believe we should invalidate the whole connection... as the failover is supposed to perform as a whole IMO, but I wanted to discuss that first. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059292#4059292 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059292

16 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JBMESSAGING-1006 - Throwing exception when failover fails (b (Repost)

by clebert.suconic＠jboss.com

Discussion of http://jira.jboss.com/jira/browse/JBMESSAGING-1006 As part of 1006, ChannelSupport:recoverDeliveries will throw an exception if it can't find a delivery to recover on messageRefs. This will certainly cause Failover to fail... so the connection that couldn't get a proper failover should be invalidated in such state that no invocation should be made. But it happens that a messageConsumer.receive() is going through ok, even if the failover was aborted. I have tried few combinations such as closing the connectionDelegate on FailoverCommandCenter, but it didn't work as a close would try to communicate on server. So I want to create a method on DelegateSupport, called invalidate, which will be intercepted by ClosedInterceptor and will throw an exception to any call to any Delegate that failed after a failover. This way a call to messageConsumer.receive() would throw a proper exception to the client. Let me know if you see any issues. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059263#4059263 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059263

16 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JBMESSAGING-1006

by clebert.suconic＠jboss.com

Discussion of http://jira.jboss.com/jira/browse/JBMESSAGING-1006 As part of 1006, ChannelSupport:recoverDeliveries will throw an exception if it can't find a delivery to recover on messageRefs. This will certainly cause Failover to fail... so the connection that couldn't get a proper failover should be invalidated in such state that no connection should be made. But it happens that a messageConsumer.receive() is going through ok, even if the failover was aborted. I have tried few combinations such as closing the connectionDelegate on FailoverCommandCenter, but it didn't work as a close would try to communicate on server. So I want to create a method on DelegateSupport, called invalidate, which will be intercepted by ClosedInterceptor and will throw an exception to any call to any Delegate that failed after a failover. This way a call to messageConsumer.receive() would throw a proper exception to the client. Let me know if you see any issues. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059263#4059263 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059263

16 years, 10 months

1
0
0 / 0

[Design of JBoss Internal Benchmarking] - JIRA Project

by rlogiacco

I've a patch (minor typos in the javadoc) I wish to submit, but I wasn't able to find out the JRUNIT project into JBoss JIRA to create the issue and attach the patch. Can you provide it? I suggest to update the site/wiki to document this information too. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059251#4059251 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059251

16 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Getting a list of all ClientConsumers (http://jira.jboss

by timfox

Yes you're right. There's no need to wait for the deliveries to arrive, just need to wait for onmessages to complete and make sure no more messages are returned to receive or sent to onMessage until it is restarted. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059237#4059237 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059237

16 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Getting a list of all ClientConsumers (http://jira.jboss

by sergeypk

I have got it working locally but I will need to add some more tests to make sure it's implemented correctly. I had to collect all those lastDeliveryIDs into a map on the server side and send them back to the client in a ConnectionStopResponse packet that I created. Do we really have to wait for the delivery lastDeliveryID to come in this case? Wouldn't it be possible for ClientConsumer to still accept messages as usual when stopped but not deliver them to receive() and onMessage()? Then Connection.stop() could tell the server side to stop, wait until every ClientConsumer finishes any onMessage calls it has already started and return afterwards? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059236#4059236 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059236

16 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Thinking about transition attrs

by kukeltje

sorry, wrong topic, but it still is a good idea... (i'm currently working on this) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059207#4059207 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059207

16 years, 10 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: The JBossWS build is a joke - the project is unmaintaina

by adrian＠jboss.org

One other point. You shouldn't be using the main deployer to create webcontexts. You should just be adding WebMetaData to your deployment. That was one of the main reasons for the Deployers changes. A single deployment can be both a web deployment and an ejb deployment, exactly because this occurs in webservices. The hack to create a new deployment for the web-app is a hangover from the JBoss4 limitiations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059205#4059205 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059205

16 years, 10 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Maven2 Repository

by camunda

Correct me, if I am wrong, but http://repository.jboss.com/jbpm/ is not a maven2 repository. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059203#4059203 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059203

16 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Deployer Changes for AOP

by kabir.khan＠jboss.com

Thanks, I am on holiday for the next week, but will get this done when I am back View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059202#4059202 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059202

16 years, 10 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 June 2007