Re: JMX listener does not recieve the ClientId set on the
JMS

Hi,

Its looks pretty likely that the problem is in JMX/mbeans, so you might want to
try posting to the "management" newsgroup instead.   That said, here
are some thoughts based on my limited experience:

(1) Consider polling each server every few seconds rather than using
notification listeners:
MBeanServerConnection rtConnection;
....
Set s = rtConnection.queryMBeans(
                          new ObjectName("*:Type=" +
"JMSConnectionRuntime" + ",*"), null);

(2) If you haven't already done so, consider using the local runtime mbean
server on each server, rather than the global mbean server, as the latter must
route through the admin server.

eg pass "weblogic.management.mbeanservers.runtime" in the jmx service
URL rather than "weblogic.management.mbeanservers.domainruntime".

(3) Try keep everything local for increased stability, reliability, and
performance.  Particularly if its used frequently,  the JMX code that queries a
particular WebLogic server should try run on the same JVM as the WL sever that
it's querying.

Hope this helps,