Skip navigation
Currently Being Moderated

Clustered Glassfish JMS Subscription Problem (BlazeDS is Missing ClientID)

Mar 18, 2009 12:53 PM

We are migrating our BlazeDS environment under standalone Glassfish instances to clustered instances and we're now seeing this Glassfish error when a BlazeDS consumer tries to subscribe to a JMS message service:

[#|2009-03-18T15:51:33.863-0400|SEVERE|sun-appserver2.1|javax.jms.Sess ion.mqjmsra|_ThreadID=17;_ThreadName=httpWorkerThread-38080-1;_Request ID=4bdd20d7-d53c-4bbe-b157-9e0e28e4bbf5;|MQJMSRA_SA4001: createSubscriber:Exception:Require non-null, non-empty clientId for clustered non-durable subscription:cId=null|#]

Which seems to be saying that Glassfish requires the client to add a non null client ID. I am trying to find out why Glassfish requires this, but I don't see how to set the clientId in BlazeDS even if I had to. Is there a reason why BlazeDS does not use a clientID when subscribing and is there a way to change that behaviour?

(we're using a old version of BlazeDS : 3.0.0.544)
 
Replies

More Like This

  • Retrieving data ...

Bookmarked By (0)