I may be way off base here, but this looks very much like a long-standing
bug in WebLogic. That is, the JDBC connection returned in ejbCreate does
not have auto-commit disabled, as it should, as per the spec. You might
be able to:
a) disable auto-commit yourself, or
b) see if this bug has been fixed in a more recent product release.
-jkw
E Bakka Reddy wrote:
>
> Hi Ardianto,
>
> Yes, we have used the same, but not working.
>
> for more details read the following:
>
> We are facing problem with controlling the trasaction at entity bean side
> by using javax.transaction. UserTransaction
>
> We have two insert stmts in BMP of create method under a single
> transaction(u.begin();..insert stmt1, insert stmt2...u.commit();, even if
> second fails, first stmt is commiting and even we caught sqlexception and
> written rollback stmt there...u.rollback(), samething happeneing here also.
>
> Second way we tried as getUserTransaction on entitycontext, but while
> running the application, it is throwing an exception saying that
> TX_BEAN_MANAGED is not set. But we dont know how to set the
> TX_BEAN_MANAGED.
>
> But, from client side we are able to do this( one insert stmt in create
> method and call it two times from client under userTransaction Scope, it's
> working fine, i.e., calling the create method twice)
>
> Please, guide us, whether we can put multiple stmts in entity beans under
> single transaction scope or not.
>
> Thanks,
> Reddy
>
> ===========================================================================
> 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".
