1 Reply Latest reply on Dec 11, 2014 12:21 PM by jbertram

    NettyConnectorFactory error

    anuja.khemka

      I have a Jms Listener inside a tomcat application. The JMS server is a hornetQ server and I use netty connector to connect to it. The connection is successful and works fine, but when tomcat stops, I see the following error in catalina.out

       

       

      `Dec 11, 2014 4:31:40 PM org.apache.catalina.loader.WebappClassLoader loadClass

      INFO: Illegal access: this web application instance has been stopped already.  Could not load org.hornetq.core.remoting.impl.netty.NettyConnectorFactory.  The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.

      java.lang.IllegalStateException

              at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1245)

              at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1205)

              at org.hornetq.utils.ClassloadingUtil.newInstanceFromClassLoader(ClassloadingUtil.java:24)

              at org.hornetq.core.client.impl.ClientSessionFactoryImpl$2.run(ClientSessionFactoryImpl.java:1466)

              at org.hornetq.core.client.impl.ClientSessionFactoryImpl$2.run(ClientSessionFactoryImpl.java:1463)

              at java.security.AccessController.doPrivileged(Native Method)

              at org.hornetq.core.client.impl.ClientSessionFactoryImpl.instantiateConnectorFactory(ClientSessionFactoryImpl.java:1462)

              at org.hornetq.core.client.impl.ClientSessionFactoryImpl.<init>(ClientSessionFactoryImpl.java:203)

              at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:864)

              at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:583)

              at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:107)

              at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:102)

              at org.springframework.jms.support.JmsAccessor.createConnection(JmsAccessor.java:184)

              at org.springframework.jms.listener.AbstractJmsListeningContainer.createSharedConnection(AbstractJmsListeningContainer.java:405)

              at org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:390)

              at org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:880)

              at org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:856)

              at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1007)

              at java.lang.Thread.run(Thread.java:636)

      Dec 11, 2014 4:31:40 PM org.jboss.netty.util.ThreadRenamingRunnable

      WARNING: Failed to determine the thread name

      java.lang.NullPointerException

              at org.jboss.netty.util.ThreadRenamingRunnable.getNewThreadName(ThreadRenamingRunnable.java:126)

              at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:91)

              at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)

              at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:175)

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)

              at java.lang.Thread.run(Thread.java:636)`

       

       

      I know this is because tomcat illegally stops the connector but I am not sure how to fix this!

        • 1. Re: NettyConnectorFactory error
          jbertram

          As you noted, this looks like a problem caused by Tomcat (and perhaps Spring as well).  I think you'd be better off asking your question on the Tomcat forum.  It's not clear to me what (if anything) HornetQ could do about this.