>>Meanwhile, maybe you could switch to RMI to avoid this problem.
That's not an option for me. My software needs the local call optimization in
Jeremie in order to perform at an acceptable level.
Joe
Philippe Durieux wrote:
> Joe Gittings wrote:
> >
> > Hi,
> >
> > OK now I have discovered a new txn-related problem: Jonas is apparently
> > leaking transaction objects on Sybase ASE. I am now using
> > client-demarcated txns for all operations.
> >
> > Is there something I'm doing wrong? A pile of "$chained_transaction"
> > objects accumulate in the Sybase server, all showing the transaction
> > state "begun". I've checked carefully and I'm pretty sure I'm committing
> > all my JTA txns.
> >
> > This is a problem because each "$chained_transaction" object has one or
> > more DBMS connections attached to it, and because these connections are
> > attached to unfinished txns, they never get released.
> >
> > Any ideas?
> > Joe
> I'm not familiar with Sybase ASE. But we are pretty sure now that there
> is
> a problem with propagation of transactional context when you use
> Jeremie.
> This pb can lead to different problems like "Bad Status=COMMITTED" for
> example.
> We are looking for a solution with Jonathan people to fix this problem.
> Meanwhile, maybe you could switch to RMI to avoid this problem.
> I am not sure that "client demarcation transaction" solve this problem.
> May be
> this is just a side effect...
> --
> 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".
