Deploy .ear to cluster problem
aradka Dec 11, 2002 1:33 PMI have an ear file that contains a .war and 2 .jar files. One of the jars has a session bean that is available to the cluster. I put the .ear in the /all/deploy/ directories before startup.
I start the first node. Everything works fine.
I add/start the second node in the cluster. Failover works, round-robin doesn't.
I redeploy the .ear on the first node, round robin now works.
I see in the logs where the 2nd node, notifies the 1st that it can service requests to the bean, but it looks like the first node doesn't send a reply message saying it can also service that bean.
Log from starting first node:
2002-12-11 13:06:02,651 DEBUG [org.jboss.ha.framework.server.HATarget] replicantsChanged 'jboss.j2ee:jndiName=RateBotEJB,service=EJB' to 1 (intra-view id: 120610399)
Log from 1st node when 2nd node starts up:
2002-12-11 13:07:11,759 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] Handle: DistributedReplicantManager._add
2002-12-11 13:07:11,759 DEBUG [org.jboss.ha.framework.server.HATarget] replicantsChanged 'jboss.j2ee:jndiName=RateBotEJB,service=EJB' to 2 (intra-view id: -1576938832)
Log from node 2 on startup:
2002-12-11 13:07:45,294 DEBUG [org.jboss.ha.framework.server.HATarget] replicantsChanged 'jboss.j2ee:jndiName=RateBotEJB,service=EJB' to 1 (intra-view id: -1697549231)
Should the intra-view id's match?
Log from node 1 on redeploy of ear on node 1:
2002-12-11 13:13:51,525 DEBUG [org.jboss.ha.framework.server.HATarget] replicantsChanged 'jboss.j2ee:jndiName=RateBotEJB,service=EJB' to 2 (intra-view id: -1576938832)
Log from node 2 on redeploy of ear on node 1:
2002-12-11 13:14:25,210 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl.DefaultPartition] Handle: DistributedReplicantManager._add
2002-12-11 13:14:25,210 DEBUG [org.jboss.ha.framework.server.HATarget] replicantsChanged 'jboss.j2ee:jndiName=RateBotEJB,service=EJB' to 2 (intra-view id: -1576938832)
Intra-view id's now match and round-robin works.
Is this a bug, or should I deploy the ear differently? I tried deploying the jar the with the clustered bean separately, using farming, but I got all sorts of classloader/linking/verify errors, so I retreated to this method, but I guess that is a different topic.
Thanks,
Alex