Hi,

First, thanks to everyone on the Jonas team for addressing so quickly
the problem with txn propagation under Jeremie.

I have good news, and I have bad news. So first, the good news! It
appears that the problems with "Bad status=COMMITTED" messages under
container-demarcated txns are completely resolved.

Now, the bad news. Unfortunately it appears that some txn problems
remain. If I invoke a method on a session bean which has been declared
as tx=Mandatory, using a client-demarcated txn, I get this output from
Jonas (with default trace levels):
 Current.setPropagationContext: unknown tx:1003777137994753
 setPropagationContext: Bad Coordinator
 setPropagationContext: Bad Coordinator
 setPropagationContext: Bad Coordinator
 setPropagationContext: Bad Coordinator
 setPropagationContext: Bad Coordinator

(Note that this method loads an EJB which has been declared with
tx=Required. And that EJB's loading process loads a large number of
other EJBs, all of which are declared with tx=Required).

It appears that the client-demarcated txn *is* being used, since the
timeout set on it is honoured. But the error messages are worrying, and
I need to know if they represent a real problem or not.

Another point: in order for Jonas to recognize the client-demarcated txn
at all, I need to include these properties in the *client-side* copy of
jonathan.prop (as well as in the server-side copy):
jeremie.JRMITSHandler.sender=org.objectweb.jonas.rmifilters.JonasSender
jeremie.JRMITSHandler.receiver=org.objectweb.jonas.rmifilters.JonasReceiver

(this was also the case with 2.2.4). If I don't do this, invoking a
tx=Mandatory method gives a "Mandatory and not in transaction" error
from the server. Nowhere in the documentation is this requirement for
the client-side props mentioned, and I wonder if it is correct
behaviour?

As usual, thanks in advance,
Joe


----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".

Reply via email to