Alexandre Lefebvre wrote:
>
> (repost)
>
> From: [EMAIL PROTECTED]
> Date: Thu, 11 May 2000 16:53:35 +0530
>
> Hi,
> We are facing a serious problem regarding transaction management in
> JOnAS2.0. It is really crucial to the completion of the project now.
>
> The existing application was working perfectly in J2EE. It is only after the
> shift to JOnAS 2.0 that we faced this problem.
>
> We are using Session Beans with Transaction managed by Containers. In some
> methods of these Beans , there is inter Bean reference, where the method of
> another bean is being invoked. The invoked method of the referenced bean ,
> as well as the calling method of the Calling bean have the Transaction
> Attribute set to TX_REQUIRED.
> If both the substituent methods are executed successfully, the data goes
> correctly into the database, however the EJB Server still throws an
> exception - commit_one_phase exception. As a result of which, we are not
> able to detect the success/failure of the transaction.
>
> Is there a way to execute the above scenario using Bean Managed
> Transaction(by Coding for the Transaction in the bean) ?
>
> Thanx!
> Rohini
I think this question has already been replied a few days ago, but maybe
not in this list...
A bug has been fixed in jonas 2.0 concerning the jdbc connections that
were not closed by the user. In that case, you sometimes got a
"commit_one_phase exception". Try the new JOnAS version on the cvs tree
to see if this fix your problem.
Another solution is to always close connections before leaving a method,
since there is a pool of connections that is managed by the JOnAS server
that insure that connections can be reused, i.e. the physical jdbc
connection
is never closed really.
Philippe
--
Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bull S.A - 1 rue de Provence - 38432 Echirolles Cedex France
[EMAIL PROTECTED] http://www-frec.bull.com
-> Download our EJBServer at http://www.bullsoft.com/ejb <-
----
This list is cross-posted to two mail lists. To unsubscribe,
follow the instructions below for the list you subscribed to.
For objectweb.org: send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe ejb-container-group".
For enhydra.org: send email to [EMAIL PROTECTED] and include
in the body of the message "unsubscribe ejb-container-group".
