>I tried to change its transaction attribute to Transactoin Required (for
>making a
>container - managed transaction). For that I had to register the Resource
>Manager. In the implementation class's various methods, I declared
>the "java.sql.Connection pConn = null;". Then I opened the connection and
>made
>the JDBC call. But in some cases, it threw an exception "Global Transaction
>not
>started". I can't figure out why this is happening.
Make sure, the method is running in a transaction context, by making
sure either
TX_REQUIRED is set or TX_SUPPORTS and the calling bean is in a
transactions.
In global transactions, connection can not be obtained outside a
transaction.
>From 4.0, service pack, you could also use local transactions.
>There's one more problem that I occasionally face - "A Transaction is
>already associated
>with the current thread". I absolutely haven't been able to understand
>what's happening.
>It would be really nice if anyone helps me out.
R u using bean managed transactions? If so u can not start a new
transaction
when there is a transaction context pending. You either commit/rollback
transaction,
before starting a new one, since nested transactions are not supported.
Thanks,
- Satish
iPlanet application server
===========================================================================
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".
