<vendor>
I believe there is a bug in WebLogic, whereby the JDBC connection returned
in ejbCreate and ejbRemove has auto-commit enabled. This means that SQL
executed in these methods is always committed, even if the global transaction
was rolled back. This is obviously contrary to the EJB specification. I
would hope that WebLogic has a patch for this bug, and you should contact
them directly.
</vendor>
-jkw
"Wang, Jingfang, GOVMK" wrote:
>
> Is there any difference between update and insert or ejbCreate and ejbStore
> in transaction thread?
> It can roll back the set../ejbStore, but can't roll back the ejbCreate.
>
> tx.begin();
> beanA = zzzHome.create(); //--- (1)
> beanB = zzzHome.findByBBBB(bbbb);
> beanB.setCCCC(cccc); //--- (2)
> tx.rollback();
>
> statement (2) is rolled back, but (1) is not rolled back. Can anyone help
> me? Thanks,
>
> Jingfang Wang
>
> ===========================================================================
> 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".
