This sounds like a bug to me on first glance. Please see EJB 1.1 spec
section 11.6.1. My read is that if the client has a tx, and calls a
stateless session, which starts a tx, the clients tx would be suspended.
Therefore the commit of the beans user transaction should not force a
rollback of the clients tx. This is firther clarified in Table 6 of 11.6.1
as:
"If the client is associated with a transaction T1, and the instance is not
associated with a trans-action,
the container suspends the client's transaction association and invokes the
method with
an unspecified transaction context. The container resumes the client's
transaction association
(T1) when the method completes."
Unless someone can show me another interpretation of this, I would consider
your containers response a bug.
Dave Wolf
Internet Applications Division
Sybase
----- Original Message -----
From: "Bhupesh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 08, 2001 11:05 AM
Subject: EJB & Transactions
> I have a stateless session bean that uses Bean Managed Transactions. It
> makes calls to a series of other session beans that perform database
> operations (INSERTS & UPDATES). All of these calls are made within the
scope
> of a UserTransaction.
>
> One of the beans that is called uses bean managed transactions and gets a
> JDBC connection (via javax.sql.DataSource) from the server pool. It begins
a
> transaction, executes some sql and then commits the transaction.
>
> The issue I have is that as a result of this commit (in the called bean),
> the UserTransaction started in the first bean is also committed. If I try
to
> rollback from the first bean it has no affect, all changes made by other
> session beans are committed. Is this correct, or should the commit on the
> second bean have no affect on the transaction running in the first bean?
>
>
>
> regards
>
> Bhupesh Wagjiani
> GamCom Solutions Limited
> [EMAIL PROTECTED]
>
>
>
****************************************************************************
***
> Any opinions expressed in this email are those of the individual and not
necessarily those of GamCom Solutions Ltd (herein after "GamCom") and/or its
subsidiaries. This email and any files transmitted with it, including
replies and forwarded copies (which may contain alterations) subsequently
transmitted from GamCom and/or its subsidiaries, are confidential and solely
for the use of the intended recipient. If you are not the intended recipient
or the person responsible for delivering to the intended recipient, be
advised that you have received this email in error and that any use is
strictly prohibited; please notify us immediately and do not disclose,
distribute, or retain this email or any part of it. We believe but do not
warrant that this e-mail and any attachments are virus free. You must
therefore take full responsibility for virus checking. GamCom and/or its
subsidiaries reserve the right to monitor all email communications through
their networks.
> If you have received this email in error please notify GamCom by telephone
on +44 (0)20 8838 5441 or via email to [EMAIL PROTECTED] , including a copy of
this message.
>
****************************************************************************
***
>
>
===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff EJB-INTEREST". 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 "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
