I too have just had this error. I'm also using Jonas 2.0 with JDK1.2.2.
In my case at least it *was* due to a transaction timing out. In fact, "JTM
timeout expired" was reported just prior to the error. It was easily cured
by doing a setTransactionTimeout() on the client-demarcated
UserTransaction.
It doesn't really appear to cause any problems, although it does seem to
leave the connection pool in an odd state. From time to time afterwards,
Jonas would report that it had found anomalous pool entries and was
removing them.
Joe
========================================================
"Halas, Miroslav" wrote:
Hi,can please somebody from Jonas team help me to explain where can this
problem occur?
We are running Jonas 2.0 using Jeremie on JDK 1.2.2 using Interbase 5.5.
All
our beans are using container managed persistance. From time to time (so
far
we cannot determine excact cause, might be timing, resource problem) we get
following error message and exception. Could this be caused for example by
too long transaction which times out? Any explanation or help is really
welcome. Thanks to all.WARNING: Connection was not always closed correctly
!
connection-open counter underflowremoveConnection: connectionlist is empty
Cannot enlist XAResource:javax.transaction.RollbackException
Exception in connectionClosed:javax.transaction.SystemException: Cannot
sendXA
end:javax.transaction.xa.XAException
Cannot enlist XAResource:javax.transaction.RollbackException
Exception in connectionClosed:javax.transaction.SystemException: Cannot
sendXA
end:javax.transaction.xa.XAException
EntitySynchroImpl.considerRequest() registerSynchronization(this)
:javax.transa
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
