Weblogic 10 - JMS - This RJVM has already been shutdown

Question

Any idea why the following errors comes up.This is happening when posting a JMS message to a queue deployed on Admin server from the application on managed server.

009-06-02 11:21:18,688 (com.xxx.util.servicelocator.ServiceLocator:612) ERROR - Error while loading Queue ProfilerNotify

javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: This RJVM has already been shutdown 3481854169479569584S:XX.XXX.X.XXX:[9200,9200,-1,-1,-1,-1,-1]:Production10:AdminServer]

        at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:64)

        at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:426)

        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:382)

        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)

        at javax.naming.InitialContext.lookup(InitialContext.java:351)

        at com.xxx.util.servicelocator.ServiceLocator.loadQueue(ServiceLocator.java:607)

        at com.xxx.util.servicelocator.ServiceLocator.getQueue(ServiceLocator.java:285)

Answer 1

We had this error in what sounded like similar circumstances recently.

It turned out to be because we didn't have the domain names of the servers in DNS. We weren't using domain names (we used IPs) but it seems weblogic needs to be able to reverse-lookup IP addresses or it gives this most misleading error.

We just added the relevant lines to /etc/hosts and everything started working.