On 11-06-17 07:11 AM, Eugene Kondrashev wrote:
> Thanks a lot for the link!
>
> But what if there is no cluster, and I have distribute configuration
> environment with several servers defined. Who is responsible for
> propagating destination information to all of the server instances
> brokers?
If you are using GlassFish cluster, the GlassFish MQ brokers that are
managed by the GlassFish servers in the cluster are auto-clustered.
For standalone broker, a destination belongs to that broker only.
Please see GlassFish and MQ Administration Guides for JMS destination
management,
http://download.oracle.com/docs/cd/E18930_01/html/821-2416/ablkj.html
http://download.oracle.com/docs/cd/E18930_01/html/821-2438/gheav.html
amy
>
> Thanks,
> Eugene
>
> 2011/6/16 Amy Kang <amy.kang_at_oracle.com <mailto:amy.kang_at_oracle.com>>
>
> On 11-06-16 05:39 AM, Eugene Kondrashev wrote:
>
> Hi
> I have a question regarding deployment of the jms destination
> resources.
>
> Let sey i have several managed servers and a clustrer defined.
> I've created a Topic and selected the targets for it.
>
> As i read from the docs, Glassfish has integrated jms service
> support in face of Glassfish MQ 4.4.
> After looking to the domain.xml I've found that each config
> defines its own jms-service on a different ports. So each
> server instance has its own jms server.
>
> Does that means that jms destination(Topic, i've created) is
> registered at each target server(cluster) jms service?
>
> The confusion comes from the fact that there is ono-to-one
> relation between glassfish server instance and jms server.
> this
> <http://www.packtpub.com/article/configuring-jms-resources-in-glassfish-2>
> tutorial expalains how to register apache generic resource
> adapter to integrate glassfish with ActiveMQ.
> The command for creating resource-adapter-config contains url
> to the only one ActiveMQ broker that will be serving all the
> destinations, and in this case all is clear. If I create a
> topic for that resource adapter i know that the url of jms
> server(broker) is /URL=tcp://127.0.0.1:61616
> <http://127.0.0.1:61616> <http://127.0.0.1:61616>/ who will
> be serving the topic admin object.
>
>
> And what about jmsra, what is the relation between created
> Topic and all these brokers running per server instance?
>
>
> In that case, the JMS service in a GlassFish cluster is provided
> by a GlassFish MQ cluster where destination information is
> propagated to all brokers in the cluster. Please see details in
> GlassFish MQ Technical Overview
> http://download.oracle.com/docs/cd/E18930_01/html/821-2443/ggssc.html
>
> amy
>
>
>
> PS:
> I'm using Glassfish ES 9.1
>
> Thanks,
> Eugene
>
>
>