DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30489>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30489


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Additional Comments From [EMAIL PROTECTED]  2005-12-16 02:03 -------
Here is a trace from the jboss deployer which shows why this occurs. This is the
equivalent of the tomcat manager undeploying a web app. From within the session
writeObject, the non-Serializable attributes are being removed. This in turn
causes an invalidation the session as when the removeAttribute calls isValid(),
which in turn calls expire:

expire():650, org.apache.catalina.session.StandardSession, StandardSession.java
isValid():569, org.apache.catalina.session.StandardSession, StandardSession.java
removeAttribute():1146, org.apache.catalina.session.StandardSession,
StandardSession.java
removeAttribute():1122, org.apache.catalina.session.StandardSession,
StandardSession.java
writeObject():1405, org.apache.catalina.session.StandardSession,
StandardSession.java
writeObjectData():902, org.apache.catalina.session.StandardSession,
StandardSession.java
doUnload():539, org.apache.catalina.session.StandardManager, 
StandardManager.java
unload():485, org.apache.catalina.session.StandardManager, StandardManager.java
stop():687, org.apache.catalina.session.StandardManager, StandardManager.java
stop():4511, org.apache.catalina.core.StandardContext, StandardContext.java
destroy():1213, org.apache.catalina.core.ContainerBase, ContainerBase.java
destroy():4617, org.apache.catalina.core.StandardContext, StandardContext.java
invoke0():-1, sun.reflect.NativeMethodAccessorImpl, 
NativeMethodAccessorImpl.java
invoke():39, sun.reflect.NativeMethodAccessorImpl, NativeMethodAccessorImpl.java
invoke():25, sun.reflect.DelegatingMethodAccessorImpl,
DelegatingMethodAccessorImpl.java
invoke():324, java.lang.reflect.Method, Method.java
invoke():503, org.apache.commons.modeler.BaseModelMBean, BaseModelMBean.java
invoke():109, org.jboss.mx.server.RawDynamicInvoker, RawDynamicInvoker.java
invoke():473, org.jboss.mx.server.MBeanServerImpl, MBeanServerImpl.java
performUndeployInternal():436, org.jboss.web.tomcat.tc5.TomcatDeployer,
TomcatDeployer.java

The isValid() call returns false and the remove of the non-Serializable
attribute fails:


Caused by: java.lang.IllegalStateException: removeAttribute: Session already
invalidated
        at
org.apache.catalina.session.StandardSession.removeAttribute(StandardSession.java:1147)
        at
org.apache.catalina.session.StandardSession.removeAttribute(StandardSession.java:1122)
        at
org.apache.catalina.session.StandardSession.writeObject(StandardSession.java:1405)
        at
org.apache.catalina.session.StandardSession.writeObjectData(StandardSession.java:902)
        at
org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:539)
        at
org.apache.catalina.session.StandardManager.unload(StandardManager.java:485)
        at
org.apache.catalina.session.StandardManager.stop(StandardManager.java:687)
        at 
org.apache.catalina.core.StandardContext.stop(StandardContext.java:4511)
        at 
org.apache.catalina.core.ContainerBase.destroy(ContainerBase.java:1213)
        at
org.apache.catalina.core.StandardContext.destroy(StandardContext.java:4617)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at 
org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)

These stack traces are from the current jakarta-tomcat-5.0.30 beta source
release. Any attempt to serialize an expired session that has non-Serializable
attributes will show this problem.

One solution would be to not write out invalid sessions from within the
StandardManager doUnload() method.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to