2 Replies Latest reply on Mar 21, 2003 4:32 AM by michael bennett

    JBoss spits exception AFTER JMS connection

    Cory Watson Newbie

      After my JMS code connects to JBoss, I see the following error in the logs. What the heck does this mean?

      2002-12-18 14:44:45,384 ERROR [org.jboss.mq.il.oil.OILClientIL] Cannot connect to the ConnectionReceiver/Server
      java.net.ConnectException: Connection refused
      at java.net.PlainSocketImpl.socketConnect(Native Method)
      at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295)
      at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:161)
      at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148)
      at java.net.Socket.connect(Socket.java:425)
      at java.net.Socket.connect(Socket.java:375)
      at java.net.Socket.(Socket.java:290)
      at java.net.Socket.(Socket.java:146)
      at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:175)
      at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156)
      at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:112)
      at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:860)
      at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterceptorSupport.java:308)
      at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java:645)
      at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java:310)
      at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:324)
      at java.lang.Thread.run(Thread.java:536)

        • 1. Re: JBoss spits exception AFTER JMS connection
          Cory Watson Newbie

          Searching the forums yielded other problems, but no solutions. Using UIL instead of OIL makes the problem go away.

          Can someone shed some light on this? JBoss 3.0.4, RedHat 7.2

          • 2. Re: JBoss spits exception AFTER JMS connection
            michael bennett Newbie

            yes I get exactly the same thing on jboss 3.0.6 and 3.0.4T on winXP with jdk 1.4.1_01

            sending out around 1000 messages using OIL eats up all the ports on my machine so doing one test case is fine. running the test case a second time I got a huge list of exceptions and checking via netstat i see that almost EVERY socket on my maching was opened by jboss.

            For some reason it doesnt release the sockets straight after the message has been sent and there is no reuse either.

            can anyone tell me why this happens? and how to get around it.

            luckily I can use the JVM IL as it all resides on a single machine and JVM but i cant imagine the system is this unusable at high voulmes....