Continuing my configuration of the JMS cluster (sun message queue 4.3)...
After being able to (more or less) configure the application server, and
being able to ping the JMS broker from the GUI console, I developed a small
web application to test the installation.
Although I was able to get it to run, my setup is not good yet. Basically,
when I start the two cluster nodes, each one starts a JMS broker (as a
separate process). I don't want that, because I am trying to use a REMOTE
JMS configuration, and to completely separate the administration of the
messaging service. What's weird, is that when the glassfish node starts the
jms broker, then it uses the port number that I have specified for the
remote server.
So basically, when I create my JMS resources, the glassfish nodes talk to
their local JMS broker, and not to my REMOTE broker.
The only solution I found, was to specify the address of my REMOTE broker in
the connectionfactory addresslist property.
Any idea about what might be wrong in my setting, and what I could try to
improve it?
--
View this message in context: http://www.nabble.com/Remote-JMS%2C-glassfish-cluster%2C-cannot-PING-JMS-nor-create-physical-destinations-from-the-GUI-tp22340706p22352398.html
Sent from the java.net - glassfish users mailing list archive at Nabble.com.