Dear All,
Please tell me to shut up if this violates the EJB3 spec, but could the
Exception that gets thrown saying a JTA transaction is 'already marked for
rollback' please have as its getCause() the original exception that caused the
transaction to roll back?
I have a chain of EJBs that corr
Dear All,
I have a newbie question regarding the @Remove annotation.
EJB3, being all lightweight and POJO, doesn't mandate a @Remove method on a
SFSB or a SLSB. This makes it confusing when I need to declare it and when my
clients need to call it. Specifically:
1. Do I need it if my client use
Sorry - I am using 4.0.4.CR2 (I meant to say that in the subject heading)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939385#3939385
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3939385
---
Dear all,
I am a newbie to EJB3 and JTA, and am finding their behaviour a little
confusing. Let us say I have a SFSB A that calls another SFSB B:
1. If B throws a regular Exception (not a RuntimeException) do both B and A
have an opportunity to catch it and process it without triggering JTA rol
For those travelling this way themselves, I found that using...
| void onMessage( Message p_message )
| {
| if ( p_message.getJMSRedelivered()) return;
| ...
|
...is a (slightly yucky) way of avoiding the resends. Of course, an
ActivationConfigProperty would be better...
V
Peter,
Fantastic! I will give that a try - it sounds like exactly what I need!
With regards to catching Exceptions, that one is more tricky: I do catch
Exceptions at the top level of my onMessage (and don't rethrow them), but the
message still gets re-delivered.
Looking at the stack trace of t
If it helps, this page...
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMDB
...seems to be exactly what I want, with its mention of MaxmimumSize and
MaxTimesRedelivered, but how do I configure this in my EJB3 environment?
View the original post :
http://www.jboss.com/index.html?module=bb
Dear All,
I am finding when I set up a Queue much like the example at...
http://trailblazer.demo.jboss.com/EJB3Trail/serviceobjects/mdb/
...JBoss instantiates several (I'm guessing around 5) consumers that all
hungrily grab whatever appears on the Queue in a concurrent fashion. Also, if
any of
