Hi,
I do have the same problem as Joe although I am working on version
2.2.1. with Jeremie. The problem started as I seperated the client and
server classpath. Whenever I am using a UserTransaction in the client I
get the following error:
setPropagationContext: Bad Coordinator
[...]
The transaction is commited as normal but the created object inside the
transaction never appears in the database.
It seems that I am missing some necessary properties in the client
classpath. I NEVER found any description of what has to be inserted into
the classpath of the client. Is there any document?
I added the Jonathan.prop according to Joe's mail (included at the
bottom) to the client's classpath, but still no change. I would rather
stick to version 2.2.1 without going to the hassle of upgrading right
now!
Thanks in advance for any hint!
Simon
Philippe Durieux schrieb:
>
> Joe Gittings wrote:
> >
> > 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).
> I'm surprise of this, because we have lots of tests about transactional
> attributes and they all pass, but I will look deeper at your problem.
> >
> > 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?
> For this last point, you are right. You must see jonathan.prop with
> these lines
> from your client, or no transactional context will be propagated.
> May be the documentation is not complete on this.
> >
> > 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".
>
> --
> Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Bull - 1 rue de Provence - 38432 Echirolles Cedex France
> [EMAIL PROTECTED]
> -> Download our EJBServer at http://www.evidian.com/ejb <-
> ----
> 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".
----
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".
Re: jonas 2.2.5 still has problems with client-demarcated txns
Simon Oldeboershuis, outermedia Wed, 24 Jan 2001 03:22:34 -0800
- jonas 2.2.5 still has problems with client... Joe Gittings
- Re: jonas 2.2.5 still has problems wi... Joe Gittings
- Re: jonas 2.2.5 still has problem... Joe Gittings
- Re: jonas 2.2.5 still has problems wi... Philippe Durieux
- Re: jonas 2.2.5 still has problems wi... Philippe Durieux
- Re: jonas 2.2.5 still has problem... Joe Gittings
- Re: jonas 2.2.5 still has problems wi... Simon Oldeboershuis, outermedia
- Re: jonas 2.2.5 still has problem... Philippe Durieux
