users@glassfish.java.net

Client ID For Non Durable Connection Is Required In A Glassfish Cluster?

From: <glassfish_at_javadesktop.org>
Date: Wed, 18 Mar 2009 13:37:46 PDT

I am setting up a glassfish cluster with two instances and am coming across this error:

[#|2009-03-18T15:51:33.863-0400|SEVERE|sun-appserver2.1|javax.jms.Session.mqjmsra|_ThreadID=17;_ThreadName=httpWorkerThread-38080-1;_RequestID=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 preventing all of my JMS clients from subscribing to a topic. The topic is not persistent and is about as simple as it comes. In a non-clustered glassfish domain, it does not have this problem. Looking at the code,

http://www.docjar.com/html/api/com/sun/messaging/jms/ra/SessionAdapter.java.html

does anyone know why is this required for a cluster and not for a single (standalone) instance? It's connecting to the same JMS resource in both environments.
[Message sent by forum member 'h1d3m3' (h1d3m3)]

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