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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-126 -- JMS expiration

by weston.price＠jboss.com

:-) It took awhile for me to look at the call chain and with the new AOP JBM stuff it wasn't easy to get a handle on what was going on. It actually fits perfectly when you think about it. JMS/JCA interposes when required (as per EJB3) spec while JBM functions quite nicely as either a JMS provider in an EE environment (with JCA of course) or as a standalone distrubtion. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986946#3986946 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986946

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Server side HA and failover

by timfox

Have you considered just downloading the new connection factory from JNDI from the new server? Then you'll just need the URL of the jndi server on the failover box. Just an idea. Don't know if it's any good. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986945#3986945 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986945

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-126 -- JMS expiration

by timfox

Duh. I am an idiot. I have been doing powerpoint slides for JBW for 12 hours solid and it is eating into my brain :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986944#3986944 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986944

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Server side HA and failover

by clebert.suconic＠jboss.com

anonymous wrote : All you need to replicate is locator uri and server id, the rest stays the same as you mention One tiny correction... the Delegate::ID needs to be replicated also. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986943#3986943 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986943

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Server side HA and failover

by clebert.suconic＠jboss.com

Tim wrote : All you need to replicate is locator uri and server id, the rest stays the same as you mention I would still need to clone a delegate and replace objectIds to reflect a delegate on that server. It's simpler/cleaner to just use the ClientConnectionFactoryDelegate directly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986942#3986942 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986942

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Server side HA and failover

by clebert.suconic＠jboss.com

Tim wrote : Replicate the whole connection factory is not a good solution IMHO I don't see a problem... it's replicated only when a new server joins the cluster. I don't think it's needed to create a new class for this. Anyway, A ConnectionFactory will have to play with multiple delegates anyway. The best way to achive this is by having these delegates on the factory/replicated. Tim wrote : What do you mean by HAConnection, I am not aware of this term in JBoss Messaging Do you expect any JMS Connection Factory being able to round robbin with other servers? What about local connections? I think the user would have to choose if he wants a ConnectionFactory with HA features or not. This is just a matter of decide the use case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986940#3986940 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986940

19 years, 4 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: Integration issue with the ejb caching

by mark.little＠jboss.com

No problem. JBossTS does support ordering of invocations if you want, but it's not part of the specs so you'd be no better off than you are now really, at least as far as non-JBoss TMs are concerned. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986938#3986938 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986938

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: .xhtml files give download popup

by kukeltje

Shoot, that should say jdk 1.5 on this specific system, no idea why the jdk got updated today. hmmm.... now I think of it, the jems installer wanted to download jre1.5.0_08.... but then again. I tested it while posting this and jdk1.4.2_08 has the same behaviour View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986937#3986937 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986937

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-126 -- JMS expiration

by weston.price＠jboss.com

Callchain: AsfAspect.handleRun()->MessageCallbackHandler.callOnMessage()->JmsServerSession().onMessage()->MDB.onMessage() Exception is thrown from MDB which is caught in the following code in the JMSServerSesssion | | public void onMessage(Message message) | { | try | { | endpoint.beforeDelivery(JmsActivation.ONMESSAGE); | | try | { | if (dlqHandler == null || dlqHandler.handleRedeliveredMessage(message) == false) | { | MessageListener listener = (MessageListener)endpoint; | | | listener.onMessage(message); | } | } | finally | { | endpoint.afterDelivery(); | | if (dlqHandler != null) | dlqHandler.messageDelivered(message); | } | } | | catch (Throwable t) | { | //MDB RUNTIME EXCEPTION HANDLED HERE! | log.error("Unexpected error delivering message " + message, t); | | if(txnStrategy != null) | txnStrategy.error(); | | } | | | } | So, the exception never makes it back to the MessageCallbackHandler. So the code | | if (trace) { log.trace("calling listener's onMessage(" + m + ")"); } | | listener.onMessage(m); | | if (trace) { log.trace("listener's onMessage() finished"); } | | break; | | executes with no issues. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986936#3986936 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986936

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-126 -- JMS expiration

by weston.price＠jboss.com

anonymous wrote : | The exception is caught in JBM code so I don't think you'll have a chance to do anything with it. | It's not actually. The MessageCallbackHandler invokes onMessage() on the listener. For JCA that is the JmsServerSession who calls the MessageEndpoint.onMessage() method. At this point you are in the EJB3 interceptor chain. If the MDB throws a RuntimeException it bubbles back up to the JmsServerSession where I handle it with a rollback or a commit. As far as the MessageCallbackHandler is concerned, an exception was never thrown. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986934#3986934 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986934

19 years, 4 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 November 2006