https://issues.apache.org/bugzilla/show_bug.cgi?id=48717

David Rees <dree...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
            Version|5.5.28                      |5.5.32
         Resolution|FIXED                       |

--- Comment #6 from David Rees <dree...@gmail.com> 2011-02-09 19:29:32 EST ---
I never got a chance to test that this was fixed until now, but testing on
5.5.32 still does not appear to work.

How I'm testing:

Two Linux systems running Tomcat 5.5.32 with a Cluster defined in the Host
section like this:

<Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
receiver.sendAck="false" sender.waitForAck="false"
sender.doTransmitterProcessingStats="true" sender.queueDoStats="true"
sender.queueTimeWait="true">
<Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
filter=".*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt;"/>
<Valve className="org.apache.catalina.cluster.session.JvmRouteBinderValve"
enabled="true"/>
<ClusterListener
className="org.apache.catalina.cluster.session.ClusterSessionListener"/>
<ClusterListener
className="org.apache.catalina.cluster.session.JvmRouteSessionIDBinderListener"/>
</Cluster>

The application has a <listener><listener-class> defined in the web.xml which
implements ServletContextListener and HttpSessionListener.  The
HttpSessionListener methods work fine on each node.

The application adds an attribute to a session which implements
HttpSessionActivationListener, HttpSessionBindingListener and Serializable. 
The HttpSessionBindingListener methods work fine on each node.

When restarting a node, the session attribute never receives any calls to
sessionDidActivate when that node comes back online.

Let me know if you need any more details.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to