"kesavramesh" wrote : We have an application running on 2 JBoss nodes running on the same machine (RMI ports 1199, 1299) I checked up the same in the JMX-CONSOLE too. | | I have Apache mod_jk sitting in front of the application servers. | | I have enabled BuddyReplication and session replication(web.xml has the tag ) | | jboss-4.2.2.GA\server\node1\deploy\jboss-web-cluster.sar\META-INF\ jboss-service.xml | SERIALIZABLE | | jboss-4.2.2.GA\server\node1\deploy\jboss-web-cluster.sar\META-INF\ jboss-service.xml | | | true | org.jboss.cache.buddyreplication.NextMemberBuddyLocator | | numBuddies = 1 | ignoreColocatedBuddies = true | | default | 2000 | false | true | true | | | | | | All of a sudden I have lots of DEBUG messages in the log files | œDEBUG [org.jboss.web.tomcat.service.session.JBossCacheManager] - Looking for sessions that have expired ... | | DEBUG [org.jboss.web.tomcat.service.session.JvmRouteValve] - checkJvmRoute(): check if need to re-route based on JvmRoute. Session id: yGDtf+7isob8Q5alzt5hMg**.node1 jvmRoute: node1 | | How do I prevent this?? | | Also when I use the cluster jnp address as “jnp://ipaddress:1199,jnp:ipaddress:1299”, it throws ServiceLocator exception. | "kesavramesh" wrote : View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122361#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...