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

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

by timfox

I don't get it. How can you handle the exception if we catch it in our layer so it never bubbles up to you? Here is the code: | | catch (RuntimeException e) | { | long id = m.getMessage().getMessageID(); | | log.error("RuntimeException was thrown from onMessage, " + id + " will be redelivered", e); | | // See JMS 1.1 spec 4.5.2 | | if (ackMode == Session.AUTO_ACKNOWLEDGE || ackMode == Session.DUPS_OK_ACKNOWLEDGE) | { | // We redeliver a certain number of times | if (tries < maxDeliveries) | { | tries++; | } | else | { | log.error("Max redeliveries has occurred for message: " + m.getJMSMessageID()); | | //postdeliver will do a cancel rather than an ack which will cause the ref to end | //up in the dlq | | cancel = true; | | break; | } | } | else | { | // Session is either transacted or CLIENT_ACKNOWLEDGE | // We just deliver next message | if (trace) { log.trace("ignoring exception on " + id); } | | break; | } | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986933#3986933 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986933

19 years, 4 months

1
0
0 / 0

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

by kukeltje

Haven't tried the webapp from cvs for more than a week and wanted to give it a try, also to see if the form caching is fixed. Currently the .xhtml files give me a download popup with all jsf tags in there. Nothing of the webapp works. I I run on jboss 4.0.4GA with jdk 1.4, have the latest dependencies. I do not see any errors in the logging and cannot turn on log4j since facelets and sun jsf use jdk logging. I'll try configuring that to see what causes this. If anybody has an idea, please let me know View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986932#3986932 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986932

19 years, 4 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: Include= multiple packages?

by clebert.suconic＠jboss.com

You can do: include=com.xxx,include=com.yyy Be careful with the concept of start though if you're using it. it will filter stuff based in your stack trace. Let me know if you have any problems. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986931#3986931 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986931

19 years, 4 months

1
0
0 / 0

[Design of JBoss Profiler] - Include= multiple packages?

by bhazer

Can you include multiple lists of packages in the filter? I want to do something like below. What would be the syntax for it? include=com.xxx,com.yyy Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986928#3986928 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986928

19 years, 4 months

1
0
0 / 0

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

by bstansberry＠jboss.com

LOL. I never thought for a second that fixing this would involve changing the synchronization handling behavior of JBossTS, although my post didn't say that. But it's why I posted on the EJB3 forum and not here. :-) JBoss Cache and Hibernate need to integrate properly with any transaction manager; relying on the implementation details of one or two obviously doesn't cut it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986926#3986926 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986926

19 years, 4 months

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: Problem with order of entity cache operations with Hiber

by bstansberry＠jboss.com

Agreed. I think JBC needs to become an XAResource. But when that can happen is an issue. Manik can better comment on that than I can. There is a discussion on the jbosscache-dev list about other, short term solutions, perhaps involving better coordination between JBC and Hibernate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986924#3986924 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986924

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

Put another way: If an EJB developer wants DLQ functionality for an MDB, he/she has to use the JMS/JCA DLQ implementation. Since we have made the decision to always execute message delivery in the context of a transaction (local or XA), JBM would not handle the case where a RuntimeException occurs. It would simply ignore the message and move on. While the JMS spec makes note that RuntimeExceptions should not occur in MessageListeners, EJB(X) does not make this assumption. The spec even goes so far as to *require* that message be redelivered depending upon the transaction attributes. For CMT/REQUIRED MDB's the choice is easy, the specification requires that the transaction be rolled back and the message be redelivered. For BMT/CMT-NOT_SUPPORTED, the spec is all but useless. Effectively the MDB executes in an 'unspecified transaction context'. There are no restrictions on how the container/JCA/integration layer can handle this situation but there are also no real guidlines unfortunately. Of course for a standalone JBM deployment, the situation is much different; at that point it's just plain ole JMS ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986923#3986923 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986923

19 years, 4 months

1
0
0 / 0

[Design of JBoss Collaboration Server] - Re: Administration guide for novices

by acoliver＠jboss.org

Did you read the wiki pages on this? The Admin GUI is on my plate right after I finish the present work on IMAP. (For some reason my brain hasn't been able to twist to do the proper tree transformation) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986916#3986916 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986916

19 years, 4 months

1
0
0 / 0

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

by timfox

"weston.price(a)jboss.com" wrote : | This is what we do, with the default behavior being that a rollback occurs. This can be altered via an ActivationSpec property to simply commit the message in the case of a RuntimeException when the transaction attribute of the MDB is BMT or CMT with NOT_SUPPORTED. CMT/REQUIRED is always rolledback and redelivered as per the EJB spec. | | The exception is caught in JBM code so I don't think you'll have a chance to do anything with it. We have to do this to be spec compliant. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986914#3986914 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986914

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 : | You mean JBoss MQ specific? JBoss Messaging doesn't have these properties. | I wondered about this. Based on this, the JMSXDeliveryCount will be consulted first and then the cached id in attempting to determine if the message should be sent to the DLQ. Effectively with JBM, no JBoss specific properties are consulted. anonymous wrote : | If a RuntimeException is thrown from onMessage and the session is transacted it is ignored as per JMS spec and delivery of the next message continues. | >From the JMS spec: anonymous wrote : | Transacted Session - the next message for the listener is delivered. The client | can either commit or roll back the session (in other words, a | RuntimeException does not automatically rollback the session). | This is what we do, with the default behavior being that a rollback occurs. This can be altered via an ActivationSpec property to simply commit the message in the case of a RuntimeException when the transaction attribute of the MDB is BMT or CMT with NOT_SUPPORTED. CMT/REQUIRED is always rolledback and redelivered as per the EJB spec. anonymous wrote : | Perhaps we should have an option to turn off JCA dlq functionality if we know the provider supports its own? Should this be the default? | You can already do this it's a simple property (useDLQ) of the JMSActivationSpec. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986911#3986911 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986911

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