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

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

by timfox

JBM itself needs it's own DLQ logic since we won't always have JCA. E.g. in the standalone server case. Before a message is sent to a message listener, or before a call to receive() returns we check the delivery counts property (JMSXDeliveryCount) of the message. If it has exceeded the max delivery attempts as specified in the server peer config then it is sent to the DLQ. In the case of an MDB - this AFAIK is still implemented as a message listener (please correct me if I am wrong) and delivery is handled by JBM so the same will apply. Delivery count can be incremented in the following situations: a) A RuntimeException is thrown from onMessage and ack mode = auto ack or dups ok, retry is immediately attempted (in JBM code). b) Session gets closed before acking messages so messages are nacked back to the destination. BTW I'm unclear as to how you keep track of how many times delivery has been attempted in the JCA layer? JMSXDeliveryCount is an optional property not supported by all messaging systems, so if you rely on that your code won't necessary work with other messaging systems. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986846#3986846 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986846

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

A rudimentary implementation would be fairly straightforward. Something along the lines of sending them off to the DLQ or a specified expiration destination. Is the JBM DLQ always active? I am a bit confused about the 'two' DLQ implementations and which one takes precendence. Does JBM do DLQ handling even with the existence of a connection consumer for a connection? Maybe we should think about 'uniting' these. Either that or I am just missing something (more likely). The MDB container in the case of JCA inflow pretty much does nothing in terms of DLQ handling, transactions etc. This is all handled on my end. Basically the JMS/JCA adapter unifies the old ASF and JMSContainerInvoker functionality. The JCA DLQ handler detects redelivery attempts and either allows onMessage() to execute or shuffles the message off to the DLQ which is specified as a property of the ActivationSpec. This is where the expiry stuff happens as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986845#3986845 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986845

19 years, 4 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-3321 -- Method attributes and transaction timeout

by weston.price＠jboss.com

Right ActivationSpecConfig would be the only way to go. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986838#3986838 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986838

19 years, 4 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-3321 -- Method attributes and transaction timeout

by weston.price＠jboss.com

According to the API: "public void setTransactionTimeout(int seconds) throws SystemException Modify the timeout value that is associated with transactions started by subsequent invocations of the begin method. If an application has not called this method, the transaction service uses some default value for the transaction timeout." Again, this is just for inflow so you are talking about a completely new thread with no transaction context. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986837#3986837 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986837

19 years, 4 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-3321 -- Method attributes and transaction timeout

by bill.burke＠jboss.com

BTW, wouldn't this need to be done as an ActivationConfigSpec to keep the RAR portable? EIther that or we're gonna have to hack it in through a ThreadLocal variable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986836#3986836 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986836

19 years, 4 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-3321 -- Method attributes and transaction timeout

by bill.burke＠jboss.com

TM.setTransactionTimeout needs to happen *before* the transaction is started? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986835#3986835 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986835

19 years, 4 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-3321 -- Method attributes and transaction timeout

by weston.price＠jboss.com

This is for MDB's where I begin the transaction and enlist the provider (ie inflow) To my knowledge you guys don't set those and even if you did, I don't believe it would have any effect because it has to be set prior to beginning the transaction. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986834#3986834 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986834

19 years, 4 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-3321 -- Method attributes and transaction timeout

by bill.burke＠jboss.com

why does the adapter need to handle this? Can't this be done in an EJB interceptor like it is already done? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986833#3986833 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986833

19 years, 4 months

1
0
0 / 0

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

by timfox

Sounds like a nice idea. How hard would it be to add? I'm also curious how the DLQ works. JBM as of 1.0.2 has it's own DLQ logic (nothing to do with JCA), which will stick the message in a DLQ specified in the jboss messaging config after a certain number of retries. As I understand it, the MDB container also has it's own DLQ logic. (Which is what you're talking about) Under what circumstances would stuff go into that DLQ? Do we need to unite the two concepts somewhat? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986829#3986829 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986829

19 years, 4 months

1
0
0 / 0

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

by timfox

Clebert - I'm confused here. Can you explain in more detail why you think you need a ClusteredConnectionFactory and why you need to replicate more than the locatorURI? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986827#3986827 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986827

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