Queues not deploying on server with custom partition name

[dokkah]

I discovered the problem on a fully configured pair of nodes, so I worked back to a basic installation and see the same problem. Perhaps I've forgotten something basic, but investigation throughout the day has lead no where.

Here's the current dilemma.

1. Download jboss-4.0.2
2. Install on solaris 5.7 (java 1.4.2_05)
3. Start server using run.sh -c all (watch the default queues deploy fine)
4. Stop server, start server using run.sh -c all -Djboss.partition.name=MyPartition i can also see in the jmx console that ConnectionFactory, XAConnectionFactory and the security domain for jbossmq. are not in jndi
5. watch the default queues not deploy

I'm hoping if I can figure out why they don't deploy on very simple installation, I can just apply it to my regular installation.

Thanks

[dokkah]

It appears that the problem was that I didn't understand that my destinations would only be deployed on one server in the cluster (I guess deploy-hasingleton should have tipped me off). However, now that I understand that, it doesn't explain why when one server goes down, the other doesn't pick up those destinations.

Perhaps I can just force them to be deployed on both servers (I have no reason not to) and be done with it.

[dokkah]

Final update: the config was wrong on my second post. All is well with the world now.

[ccaprar]

Did you deployed all JMS stuff in all your cluster nodes only in some of them?

if you deployed the JMS stuff in all nodes, did you configured all JMS in the same way in all nodes?

Thanks,
Cristi

[dokkah]

All nodes and they were configured the same.

[chetanagg]

Hi Dokkah,

I am also getting the same problem. I am using basic setp and running cluster with my partitionName. But i am not able to see ConnectionFactory , XAConnectionFactory and queues not in JMX-Console.

I am wondering i am missing some configuration.

Can you suggest what you did in your config??

Thanks
Chetan