Description Daniel Lo 2010-07-13 10:20:22 EDT

When we define EclipseLink cache coordination with JMS in WebLogic Cluster, we want to take the advantage that the JNDI names of the Connection Factory and Distributed Topic being replicated on every managed WLS in the cluster, so that our J2EE applications don't need to pass the WLS ip-address, username/password to JMSTopicTransportManager, but our developer found him had to, because of the following code from JMSTopicTransportManager:

public Context getRemoteHostContext(String remoteHostURL) {
Hashtable remoteProperties = (Hashtable)getRemoteContextProperties().clone();
remoteProperties.put(Context.PROVIDER_URL, remoteHostURL);
Object[] args = { remoteProperties };
rcm.logDebug("context_props_for_remote_lookup", args);

// decrypt password just before looking up context
remoteProperties.put(Context.SECURITY_CREDENTIALS, decrypt(getPassword()));

return getContext(remoteProperties);
}

Can this code be fixed so that when the remoteHostURL, username and password are not set then don't send them to the InitialContext? Our test code shows that we can find the Connection Factory and Topic on all the managed WLS on different machines with the local context:

InitialContext initContext = new javax.naming.InitialContext();
TopicConnectionFactory topicConnectionFactory = (TopicConnectionFactory)initContext.lookup("POMSConnectionFactory");

By taking advantage of the JNDI name replication not only we can reduce the amount of configurations, we can also reduce the single point of failure.