> At run-time, the my container seems to hang after second setState
> statement. I have to stop the server to release the DB resources. It keeps
> a lock,
> even if I stop my client.
>
look at your database server and see if you have any blocking.
> From the Server log, I see that there is a synchronization problem within
> the transaction coordinator.
>
> 1-) Is there someone who has implemented a scenario similar to this one ?
> (wich EJB Server)
>
i have not. are you sure you need new TX's everywhere?
> 2-) Is it illegal to have 1 bean with the TX_REQUIRES_NEW attribute to
> call
> a method on a second one with the same
> TX_REQUIRES_NEW attribute ?
>
perfectly legal. try with TX_REQUIRED and see if it changes
anything. what's your isolation level set to? you might try the lowest
isolation to see if it changes anything.
if all that fails, what ejb server is this? you can mail me direct
if you don't want to embarass anyone and if none of the above points to the
answer, i'll have useful info for you re tx coordination issues.
> Input would be appreciated.
>
> Alain Dessureault, IBM Canada
> [EMAIL PROTECTED]
>
> ==========================================================================
> =
> 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".
