Sorry, I forgot to mention that I'm using the cluster name: Tomcat-Cluster
So I really don't know where the DefaultPartition cluster name is coming from, all help welcome
I can't answer your question about the discarded messages but I can advise about the DefaultPartition.
DefaultPartition is the name of the primary cluster group in JBoss.
If you're using a clustered JBoss server (i.e., "all" configuration), JBoss itself uses two cluster groups. One is named DefaultPartition; it provides core clustering services. The other is named Tomcat-Cluster and provides session replication for the tomcat server in JBoss.
would i be right in assuming that if have 2 or more nodes on a network and i'm using JMS queues, the queues will only start on the first node to start up and not the subsequent nodes.
If this is the case, how would i go about making the JMS queues in the first node available to the subsequent nodes?
All help is greatly appreciated,
Thanks in advance
I have the same problem with queues, I see it, too, that on the master these queues are OK, but on the other second node, they don't work,
javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound
error appears always...
I am also having same problem. I have a Topic created on one server. I am creating a copy of the JBoss installation on another machine and starting it up.
The new server does not seem to deploy any of the default queues as well there is no Topic deployment as confirmed from JMX console.
I have a scheduler that reads JMS every 2 minutes. Now, since there is no topic deployed in new server, it is failing.
Is there any tutorial available that will help configuring the two nodes in the cluster sharing JMS resources and using them correctly?
I have found an insight to this issue. It is because it is in
server\all\deploy-hasingleton folder. If you move the MBean topic declaration to C:\jboss-3.2.5\server\all\deploy\jms
In face there is a bug that is being worked on
may be it is of some help. But, at least I have a clue now. :)
Like someone mentioned already, read the docs and wiki carefully...
In "all" configuration, JMS is started as a singleton in the cluster - it runs only on the master node, as you figured out rightly. To access any JMS queues, use HAJNDI. You dont move the jms stuff out of deploy-hasingleton.
What do you mean by