4 Replies Latest reply on Sep 15, 2004 10:12 PM by rolfz

Problems with jms-tobic in cluster (ConnectionFactory not bo

berndit Jul 31, 2004 11:57 AM

I have problems with creating a JMS-Topic in a clustered JBoss. The ConnectionFactory is only bound to the JNDI-Tree in one JBoss node (I think, that is correct ?!).

So I must search the ConnectionFactory for my JMS-Topic by HAJNDI (right?). How can I achive this? My Topic is the following:

 <!-- the KODO distributed cache Topic -->
 <mbean code="org.jboss.mq.server.jmx.Topic"
 name="jboss.mq.destination:service=Topic,name=KodoCommitProviderTopic">
 <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
 </mbean>

I have the Topic configured on every node (in the jboss-mq-destination-services.xml), is that right?

Thanks for your hints (sorry, I am a newbe to clustering JBoss)!
BERND

1. Re: Problems with jms-tobic in cluster (ConnectionFactory no

danielamadei Aug 12, 2004 7:32 PM (in response to berndit)

Hi!

I'm getting the same behaviour as you may see in my post.

I believe this happens to guarantee that only one instance consumes the messages but I'd like to confirm this.

Did you get any new info about it?

Daniel
Actions
2. Re: Problems with jms-tobic in cluster (ConnectionFactory no

jasonc Aug 18, 2004 8:02 PM (in response to berndit)

Hi folks,

Have you had any resolution on this? We're experiencing the same problem in that our queues depend on the DestinationManager which apparently only starts up on the master node.

How are the other nodes in the cluster aware of the various jms-queues if this is the case?

I'm convinced there is a way to resolve this, but I can't find any documentation that will lead me to how our configuration is off.

Thanks,
-Jason
Actions
3. Re: Problems with jms-tobic in cluster (ConnectionFactory no

danielamadei Aug 18, 2004 8:13 PM (in response to berndit)

Hi!

Yes, I've got a "workaround" on this.

As you can see, this is an expected behaviour since JBoss 3.2.4: http://jboss.org/wiki/Wiki.jsp?page=JBossMQHA

On option to make the service "activate" before the servers synchronizes state (wich takes 1 minute to happen after the master node crashes) is to do a lookup in the desired component, after that, the user will receive a NameNotFoundException but this call will start the activation process and in the subsequent call everything will work fine.

I'm investigating why we get the firs NNFException as the lookup activates the service and we shouldn't get NNFException and if I have news, I can post it here.

[]'s
Daniel
Actions
4. Re: Problems with jms-tobic in cluster (ConnectionFactory no

rolfz Sep 15, 2004 10:12 PM (in response to berndit)

Same problem here. Does anyone has a solution for this problem (3.2.5)
Actions

Go to original post