glassfish_at_javadesktop.org wrote:
> Thank you for your response!
>
> I don't want to solve the Dead Lock here.
>
> I want to solve the problem "The resource manager is doing work outside a
> global transaction",
Is this happening with the connection validation on?
"New request is not allowed to start because it should
> come with valid transaction descriptor." (in german "Die neue Anforderung
> kann nicht gestartet werden, weil sie einen gültigen Transaktionsdeskriptor
> aufweisen sollte.")
Is it a rollback of the deadlock or another rollback? If it's the former, just
ignore it - the resource might still be recovering after the deadlock.
and "Received diff Xid for open txnId:switching
> transactionId:".
This come from the stdout - is it your app code?
This happens everytime after a dead lock.
>
> And I think some strange happpens...
What exactly is happening?
thanks,
-marina
>
> GlassFish seams to struggle with the transactions after a dead lock happens.
> [Message sent by forum member 'hegalor' ]
>
> http://forums.java.net/jive/thread.jspa?messageID=374257
>
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net For additional
> commands, e-mail: users-help_at_glassfish.dev.java.net
>