users@glassfish.java.net

Re: GlassFish v2ur2 JMS with EclipseLink JPA - HELP PLEASE

From: <glassfish_at_javadesktop.org>
Date: Wed, 01 Jul 2009 11:09:47 PDT

> I am unable to set the ClientID via the API. This is
> a slippery slope.

Misunderstanding there. I appreciate you can't set it properly: I was just speculating why setting it the way you did didn't have the expected result.

>
> [i]"Do you mean "the second instance of
> Glassfish"?"[/i]
>
> No, I mean the second instance of OpenMQ. We brought
> down one broker in the cluster, so there was only a
> single broker operating. We then brought up the
> GlassFish cluster, which contains two instances of
> GlassFish. This was able to provide us with
> stability.

 Ah. Does that means that if you use only one MQ broker both GF instances are stable?

Separately: I'm looking at what would be the best way to allow users to disable MQ's shared subscription feature in a clustered container. The simplest way would be to add a new connection factory property that you would need to set on the connection factory used to create the non-durable subscriptions. You would then leave ClientID unset without seeing an error, and you wouldn't get subscription sharing. Do you think that would work in your case?

Nigel
[Message sent by forum member 'nigeldeakin' (nigeldeakin)]

http://forums.java.net/jive/thread.jspa?messageID=353809