Hi,
GlassFish 3.0.1 only has very limited clustering support. If your
application requires clustering, you might be better served to upgrade
to 3.1.
Support for an Embedded GF broker, in a JMS cluster was not introduced
until GlassFish 3.1. You may be able to get what you need with 3.0.1 by
selecting a REMOTE JMS, then, you'll need to setup your connection
factory to point to the JMS server, that's running as a broker on B (or
vise-versa, depending on where you actually want the broker to run).
This setup and configuration is much better supported in 3.1. In 3.1,
you can use EMBEDDED setup with both GlassFish instances and, you should
be able to send/receive messages from either server. If you don't want a
distributed JMS service, you could use specify REMOTE for all servers,
not hosting a JMS server, but that shouldn't be necessary unless you
have some special requirements.
-- Ed
On 8/18/2011 9:08 AM, forums_at_java.net wrote:
> Actually upon reading about various types for JMS on GF it seems like the
> reason the port is changed on the client is because the JMS type on
> machine B
> is set to LOCAL. It looks like it basically creates another broker on the
> machine A and gives it a new port (different from 7676). There is another
> EMBEDED JMS running on A. What I need is to connect B GF to original A's
> broker or to have some independant broker runnig on A, and both A and
> B GFs
> connected to it. How can I do it? Does any one know? What settings do
> I need
> to specify on A and B GFs to accomplish it?
>
>
>
>
> --
>
> [Message sent by forum member 'nakoned']
>
> View Post: http://forums.java.net/node/834184
>
>