I've faced the similar problem using Oracle Application Server. In that case
one session bean was calling other session bean. And both were container
managed. The error was same.
The work around in this case was to run second bean in TX_NOT_SUPPORTED
mode. That way you don't need transaction for second bean.
My assumption was that this is only related to Oracle server!
-Anurag
>
>We have a Session Bean that calls a non-EJB Java class which in turn calls
>another Session Bean.
>
>If we make both beans container managed transaction demarcation, and the
>business method on the second bean have a "MANDATORY" transaction
>requirement, we get a transaction does not exists error.
>
>However, I am told that if we make the first bean bean managed transaction
>demarcation then all seems to work.
>
>The deployment environment is Weblogic 4.5.1.
>
>Any ideas ?
>
>Regards
>
>Graham
>
>
>===========================================================================
>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".
>
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
===========================================================================
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".
