For some reason session clustering has never worked properly for us. We recently added a new application (w/new cluster across 2 servers) and now we get this error:

04/25 14:05:24 error Setup of session replication failed.
[1]java.rmi.RemoteException: The web application 'smt.war' could not be found to accept sessions for replication.
at jrun.servlet.session.SessionReplicationService.replicate(SessionRepli cationService.java:80)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4 60)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport .java:701)
at java.lang.Thread.run(Thread.java:595)

My jrun-web.xml file is set to write sessions to a JDBC database, which works fine, but they do not replicate to the 2nd server with JNDI as they should. When I first start the applications I do not see any errors...these errors (above) creep up after a short period of time. The app log also claims to have found a replication peer and setup session replication, but it doesn't seem that way (requests to the 2nd server generate a new session).

from the app log when I start the application:
04/13 03:40:57 info JRunRMIBroker successfully joined a JINI lookup service (assigned JINI-ID 7eb3b41d-9372-47c0-86f4-b0e59252c79f)
04/13 03:40:57 info Clusterable service SecurityContextCache discovered ClusterManager on 192.168.2.40:4283, cluster domain: SiteBuilderSBCluster (Lookup Service's JINI-ID: 855de2f9-adb5-4182-81c5-cc1aeb002823)
04/13 03:40:57 info Clusterable service SecurityContextCache discovered ClusterManager on 192.168.2.30:2744, cluster domain: SMTCluster (Lookup Service's JINI-ID: 7987d6e1-5efc-4f8f-bc56-b46136966981)
04/13 03:40:57 info Clusterable service JRunRMIBroker discovered a JRunRMIBroker peer on a JRun server named "SMT-ark" on host ARKANOID
04/13 03:40:57 info Clusterable service SecurityContextCache discovered a SecurityContextCache peer on a JRun server named "SMT-ark" on host ARKANOID
04/13 03:40:57 info Clusterable service ServletUsersService discovered ClusterManager on 192.168.2.40:4283, cluster domain: SMTCluster (Lookup Service's JINI-ID: 855de2f9-adb5-4182-81c5-cc1aeb002823)
04/13 03:40:57 info Clusterable service ReplicationIdService discovered ClusterManager on 192.168.2.40:4283, cluster domain: SMTCluster (Lookup Service's JINI-ID: 855de2f9-adb5-4182-81c5-cc1aeb002823)
04/13 03:40:57 info Clusterable service ServletUsersService discovered ClusterManager on 192.168.2.30:2744, cluster domain: SMTCluster (Lookup Service's JINI-ID: 7987d6e1-5efc-4f8f-bc56-b46136966981)
04/13 03:40:58 info Clusterable service ReplicationIdService discovered ClusterManager on 192.168.2.30:2744, cluster domain: SMTCluster (Lookup Service's JINI-ID: 7987d6e1-5efc-4f8f-bc56-b46136966981)
04/13 03:40:58 info Clusterable service ServletUsersService discovered a ServletUsersService peer on a JRun server named "SMT-ark" on host ARKANOID
04/13 03:40:58 info ServletUsersService successfully joined a JINI lookup service (assigned JINI-ID d95aab6c-ff39-449f-9fbe-832b74c8fd80)
04/13 03:40:58 info Clusterable service ReplicationIdService discovered a ReplicationIdService peer on a JRun server named "SMT-ark" on host ARKANOID
04/13 03:40:58 info ReplicationIdService successfully joined a JINI lookup service (assigned JINI-ID 9bc0dc20-4e10-4e3d-9a64-a0ab045bf85b)
04/13 03:40:58 info Clusterable service SessionReplicationService discovered ClusterManager on 192.168.2.40:4283, cluster domain: SMTCluster (Lookup Service's JINI-ID: 855de2f9-adb5-4182-81c5-cc1aeb002823)
04/13 03:40:58 info Clusterable service SessionReplicationService discovered ClusterManager on 192.168.2.30:2744, cluster domain: SMTCluster (Lookup Service's JINI-ID: 7987d6e1-5efc-4f8f-bc56-b46136966981)
04/13 03:40:58 info Clusterable service SessionReplicationService discovered a SessionReplicationService peer on a JRun server named "SMT-ark" on host ARKANOID
04/13 03:40:58 info SessionReplicationService successfully joined a JINI lookup service (assigned JINI-ID 946fa298-6b9d-4761-8ca1-d30ac4fd918f)
04/13 03:40:59 info JRunDataSource bound to JNDI under name dbcon
04/13 03:40:59 info JRun DataSourceService: Created JDBC XA Connection Pool named dbcon
04/13 03:40:59 info Bound a LinkRef from "DefaultDataSource" to the default DataSource "dbcon"
04/13 03:40:59 info Clusterable service DeployerService discovered ClusterManager on 192.168.2.40:4283, cluster domain: SMTCluster (Lookup Service's JINI-ID: 855de2f9-adb5-4182-81c5-cc1aeb002823)
04/13 03:40:59 info JRun Web Server listening on *:8102
04/13 03:40:59 info JRun Proxy Server listening on *:51007
04/13 03:40:59 info Clusterable service DeployerService discovered ClusterManager on 192.168.2.30:2744, cluster domain: SMTCluster (Lookup Service's JINI-ID: 7987d6e1-5efc-4f8f-bc56-b46136966981)
04/13 03:40:59 info Clusterable service JRunProxyClusterHelper discovered ClusterManager on 192.168.2.40:4283, cluster domain: SMTCluster (Lookup Service's JINI-ID: 855de2f9-adb5-4182-81c5-cc1aeb002823)
04/13 03:40:59 info DeployerService successfully joined a JINI lookup service (assigned JINI-ID 51e50863-0939-462b-86f6-e5170356b579)
04/13 03:40:59 info Clusterable service DeployerService discovered a DeployerService peer on a JRun server named "SMT-ark" on host ARKANOID
04/13 03:40:59 info Clusterable service JRunProxyClusterHelper discovered ClusterManager on 192.168.2.30:2744, cluster domain: SMTCluster (Lookup Service's JINI-ID: 7987d6e1-5efc-4f8f-bc56-b46136966981)
04/13 03:40:59 info JRunProxyClusterHelper successfully joined a JINI lookup service (assigned JINI-ID 2c3fbac0-9c83-424c-8f9c-ca28bc30ee71)
04/13 03:41:00 user JSPServlet: init
04/13 03:41:00 info Clusterable service JRunProxyClusterHelper discovered a JRunProxyClusterHelper peer on a JRun server named "SMT-ark" on host ARKANOID
04/13 03:41:06 info Deploying web application "JRun Default Web Application" from: file:/C:/sites/SMT/smt.war
04/13 03:41:08 user JSPServlet: init
04/13 03:41:10 info Deploying enterprise application "JRun 4.0 Internal J2EE Components" from: file:/C:/JRun4/lib/jrun-comp.ear
04/13 03:41:11 info Deploying EJB "JRunSQLInvoker" from: file:/C:/JRun4/lib/jrun-comp.ear



ideas?