why Session would close under stress test?

[gan.gary]

I have a JBoss under stresstest and under what condition the Session would close?

and the very first log is:

2008-09-10 09:01:40,695 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_2] TwoPhaseCoordinator.beforeCompletion - failed for null
org.hibernate.SessionException: Session is closed!
 at org.hibernate.impl.AbstractSessionImpl.errorIfClosed(AbstractSessionImpl.java:49)
 at org.hibernate.impl.SessionImpl.getActionQueue(SessionImpl.java:1817)
 at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:201)
 at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76)
 at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26)
 at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
 at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338)
 at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:59)
 at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:114)
 at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:247)
 at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:86)
 at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
 at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1389)
 at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
 at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
 at org.jboss.resource.adapter.jms.inflow.JmsServerSession$XATransactionDemarcationStrategy.end(JmsServerSession.java:494)
 at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:248)
 at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
 at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
 at java.lang.Thread.run(Thread.java:595)
2008-09-10 09:01:40,695 ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] org.jboss.resource.adapter.jms.inflow.JmsServerSession@e94c75 failed to commit/rollback
java.lang.NullPointerException

[gan.gary]

anyone?

[francis17101970]

You should provide some more info about your system.
Anyway it is it seems that more Thread are accessing the Hibernate Session Object and you eventually try to manipulate a Session which has been closed.....
If you are closing the session yourself, and it's not an error, you might want to think about extending the life of the session. A very, very common pattern is to open a Hibernate Session transaction as soon as a request comes in. Then, when all the processing is done, from the Servlet to the final JSP, the transaction is closed. This can be achieved by opening and closing the Hibernate Session in a ServletFilter.

Take a look at this:
http://www.hibernate.org/42.html#A8

[gan.gary]

"francis17101970" wrote:
You should provide some more info about your system.

the log file is rolled, since the log4j with FileRolling is used. I have posted the earliest error logged.

"francis17101970" wrote:
You should provide some more info about your system.
Anyway it is it seems that more Thread are accessing the Hibernate Session Object and you eventually try to manipulate a Session which has been closed.....
If you are closing the session yourself, and it's not an error, you might want to think about extending the life of the session. A very, very common pattern is to open a Hibernate Session transaction as soon as a request comes in. Then, when all the processing is done, from the Servlet to the final JSP, the transaction is closed. This can be achieved by opening and closing the Hibernate Session in a ServletFilter.

Take a look at this:
http://www.hibernate.org/42.html#A8

No, I was running on stress test and it(session) should not suppose to be closed. What might be the root cause? WHat's the solution?

[gan.gary]

anyone?

[gan.gary]

anyone?

[gan.gary]

OMG, it's becase the queue is so long until it over the transaction timeout