[jboss-user] [JBoss Messaging] - JBoss Messaging, and JBoss Remoting in cluster environment

[berni_huber@a1.net]

I have question about using JBoss Remoting together with JBoss Messaging.

The system setup is a JBoss Cluster defining queues, and connection factories,
which are used by various single JBoss instances.

The system setup in detail:

A JBoss Cluster (Clu) defining clustered Queu (Q1) , and 
failover ConnectionFactories (CF).
Clu runs on JBoss 4.2.2.GA, and JBoss Messaging 1.4.0SP3

A single JBoss instance (Inst) deployed an MDB using
Q1, and CF from Clu.
Moreover a remote JMSProvider is deployed on Inst using the JBoss Messaging from Clu.
Inst runs on JBoss 4.2.2.GA, and JBoss Messaging 1.4.0SP3.

Initially I was using JBoss Remoting 2.2.2SP1 as it is default version when you
install JBoss 4.2.2.GA.

As I was testing failover in Clu I noticed that the MDBs running on Inst do not realize the failover,
and were still trying to reconnect to a shutdown Clu instance.

As soon as I installed JBoss Remoting 2.4.0.GA on the Clu instances, and the Inst 
cluster failover worked quite perfectly.

The only problem is that the remoting bisocket configuration in JBoss messaging does not
define the callbackServerHost explictly, thus I cannot configure the callbackServerHost 
in a multi-home environment.

The bisocket URL is:
bisocket://127.0.0.1:751235663/callback?callbackServerHost=127.0.0.1&
callbackServerPort=751235663&
callbackServerProtocol=bisocket&
clientMaxPoolSize=1&
clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&
datatype=jms&guid=3j001-cocgee-fh4tny56-1-fh4tptw8-f&
isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&
serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper

How do I configure the callbackServerHost in jboss messaging?

Moreover I'd like to hear if the system setup is sensible.

The reason for choosing this system setup is that we'd like to have Clu defining only the 
JMS infrastructure, like queues, and connection factories, but deploy the applications on
instances which do not join the cluster.



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156561#4156561

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156561