J
jan
Hi world,
I attempt to perform some cleanup work in the database whenever an
HttpSession expires. In order to do this I declared one of the session
attributes to implement HttpSessionBindingListener and put my cleanup
tasks in the valueUnbound() method. Everything works fine when the
session is invalidated explicitly (via session.invalidate()). However,
when the session expires I get the following stack trace:
[20/Nov/2003:11:39:59] SEVERE (14720): StandardManager[/myApp]
processsExpire: Exception during session expiration
com.sun.enterprise.InvocationException
at
com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.
java:134)
at
com.sun.enterprise.resource.JdbcDataSource.internalGetConnection(JdbcDat
aSource.java:241)
at
com.sun.enterprise.resource.JdbcDataSource.getConnection(JdbcDataSource.
java:98)
at de.glovis.ecom.MyObj.doCleanup(MyObj.java:890)
at de.glovis.ecom.MyObj.valueUnbound(MyObj.java:965)
at
org.apache.catalina.session.StandardSession.removeAttribute(StandardSess
ion.java:1116)
at
org.apache.catalina.session.StandardSession.expire(StandardSession.java:
611)
at
org.apache.catalina.session.StandardManager.processExpires(StandardManag
er.java:755)
at
org.apache.catalina.session.StandardManager.run(StandardManager.java:832)
at java.lang.Thread.run(Thread.java:534)
I must admit that I have no clue what happens here. Is this a bug of the
S1 AppServer? I sincerely hope that the truth is out there...;-)
Thanks in advance for any hints you can give me.
Jan
I attempt to perform some cleanup work in the database whenever an
HttpSession expires. In order to do this I declared one of the session
attributes to implement HttpSessionBindingListener and put my cleanup
tasks in the valueUnbound() method. Everything works fine when the
session is invalidated explicitly (via session.invalidate()). However,
when the session expires I get the following stack trace:
[20/Nov/2003:11:39:59] SEVERE (14720): StandardManager[/myApp]
processsExpire: Exception during session expiration
com.sun.enterprise.InvocationException
at
com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.
java:134)
at
com.sun.enterprise.resource.JdbcDataSource.internalGetConnection(JdbcDat
aSource.java:241)
at
com.sun.enterprise.resource.JdbcDataSource.getConnection(JdbcDataSource.
java:98)
at de.glovis.ecom.MyObj.doCleanup(MyObj.java:890)
at de.glovis.ecom.MyObj.valueUnbound(MyObj.java:965)
at
org.apache.catalina.session.StandardSession.removeAttribute(StandardSess
ion.java:1116)
at
org.apache.catalina.session.StandardSession.expire(StandardSession.java:
611)
at
org.apache.catalina.session.StandardManager.processExpires(StandardManag
er.java:755)
at
org.apache.catalina.session.StandardManager.run(StandardManager.java:832)
at java.lang.Thread.run(Thread.java:534)
I must admit that I have no clue what happens here. Is this a bug of the
S1 AppServer? I sincerely hope that the truth is out there...;-)
Thanks in advance for any hints you can give me.
Jan