https://issues.apache.org/bugzilla/show_bug.cgi?id=56578
--- Comment #4 from Konstantin Kolinko <knst.koli...@gmail.com> --- WORKSFORME: I placed both files into webapps/examples/ I added the following line to session.jsp to display current session id: <tr><td>Session ID:</td><td><%= session.getId() %></td></tr> I am using a single Tomcat instance, with default configuration. I added the following line added to server.xml. <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/> I do not see any error. The session creation time is updated on invalidation, and session id is changed as well. Tested with current 7.0.x (JDK 6u45) and 8.0.x (JDK 7u55), on Win7, Firefox 29.0.1, A fragment of catalina.date.log of Tomcat 7 (at start time): 31.05.2014 0:02:35 org.apache.catalina.ha.tcp.SimpleTcpCluster startInternal INFO: Cluster is about to start 31.05.2014 0:02:35 org.apache.catalina.tribes.transport.ReceiverBase bind INFO: Receiver Server Socket bound to:/xxx.yyy.z.www:4000 31.05.2014 0:02:35 org.apache.catalina.tribes.membership.McastServiceImpl setupSocket INFO: Setting cluster mcast soTimeout to 500 31.05.2014 0:02:35 org.apache.catalina.tribes.membership.McastServiceImpl waitForMembers INFO: Sleeping for 1000 milliseconds to establish cluster membership, start level:4 31.05.2014 0:02:36 org.apache.catalina.tribes.membership.McastServiceImpl waitForMembers INFO: Done sleeping, membership established, start level:4 31.05.2014 0:02:36 org.apache.catalina.tribes.membership.McastServiceImpl waitForMembers INFO: Sleeping for 1000 milliseconds to establish cluster membership, start level:8 31.05.2014 0:02:37 org.apache.catalina.tribes.membership.McastServiceImpl waitForMembers INFO: Done sleeping, membership established, start level:8 31.05.2014 0:02:37 org.apache.catalina.ha.session.JvmRouteBinderValve startInternal INFO: JvmRouteBinderValve started Did you use a single Tomcat instance in your reproduction scenario, or I need something more complex? Did your cluster startup log looked like the above? Does your configuration have other differences from the default one (besides the added line in server.xml)? Can you try debugging? (As mentioned in the e-mail thread). -- 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
