This content has been marked as final. Show 2 replies
Clustering with JBoss 3.2.6 using HAJMS:
running cluster with 2 nodes , 1 master, 1 nonmaster -> ok
adding a 3rd node -> following warnings occur on the 2nd node:
WARN [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] javax.naming.NameNotFoundException:ConnectionFactory not bound
it seems, that these warnings occur for HAJMS topics, queues and connectionFactories used on the 3rd (non master node).
I could reproduce this behaviour on W2K as well as on Solaris.
The deployed applications seemed to work properly.
Is this behaviour correct? What is the explanation for these warnings?
Use 'ethereal' it's a better tool for these sorts of issues.