2 Replies Latest reply on Jul 10, 2006 2:42 AM by mswkk

    DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exit

    dolsen
    dolsen Jun 30, 2006 11:31 AM

      I know this is a DEBUG log entry and I'm tempted to igonre it (and filter it from the log).

      I would, however, like to know more about this "error"...

      Thanks
      Dag


      code use to send the message

      public void jmsSend (TextMessage textMessage) throws JMSException
 {
 final String jmsErrorMsg = "Could not send JMS message";

 boolean error = true;

 QueueConnection connection = null;
 QueueSession session = null;
 Queue queue = null;
 QueueSender queueSender = null;
 try {
 connection = createConnection();
 session = createSession(connection);
 queue = createQueue();

 queueSender = session.createSender(queue);
 queueSender.send(textMessage);

 error = false;
 } catch (JMSException e) {
 logger.error(jmsErrorMsg + e);
 } catch (NamingException e) {
 logger.error(jmsErrorMsg + e);
 }
 finally
 {
 if (null != queueSender)
 {
 try
 {
 queueSender.close();
 }
 catch (JMSException e)
 {
 logger.error ("Could not close queueSender");
 }
 }
 if (null != session)
 {
 try
 {
 session.close();
 }
 catch (JMSException e)
 {
 logger.error ("Could not close session");
 }
 }
 if (null != connection)
 {
 try
 {
 connection.close();
 }
 catch (JMSException e)
 {
 logger.error ("Could not close connection");
 }
 }

 }


      • 2402 Views
      • Tags:
        • 1. Re: DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler]
          dolsen
          dolsen Jun 30, 2006 11:44 AM (in response to dolsen)

          The degug message got chopped off a little... :(

          The full stack trace is:

          DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
          java.net.SocketException: Socket closed
          at java.net.SocketInputStream.read(SocketInputStream.java:162)
          at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
          at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
          at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:67)
          at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2200)
          at java.io.ObjectInputStream.readByte(ObjectInputStream.java:864)
          at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:290)
          at java.lang.Thread.run(Thread.java:595)

            • Actions
          • 2. Re: DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler]
            mswkk
            mswkk Jul 10, 2006 2:42 AM (in response to dolsen)

            Dear all,
            We have experience error at our JBoss 4.0.3 version, and I also capture the error from client side below. We suspected that occurred under heavy loading on JMS MQ.

            ####<Jul 10, 2006 2:18:23 PM SGT> <Warning> <EJB> <Cmapp2> <Server2> <ExecuteThread: '39' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
 java.lang.OutOfMemoryError: unable to create new native thread.
java.lang.OutOfMemoryError: unable to create new native thread
 at java.lang.Thread.start(Native Method)
 at org.jboss.mq.il.uil2.SocketManager.start(SocketManager.java:131)
 at org.jboss.mq.il.uil2.UILServerIL.createConnection(UILServerIL.java:666)
 at org.jboss.mq.il.uil2.UILServerIL.getSocketMgr(UILServerIL.java:532)
 at org.jboss.mq.il.uil2.UILServerIL.authenticate(UILServerIL.java:334)
 at org.jboss.mq.Connection.authenticate(Connection.java:1160)
 at org.jboss.mq.Connection.<init>(Connection.java:255)
 at org.jboss.mq.Connection.<init>(Connection.java:332)
 at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:66)
 at org.jboss.mq.SpyConnectionFactory.createConnection(SpyConnectionFactory.java:87)
 at org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:124)
...


            Appriecated if you could let me know any finding.
            BR,
            MK

              • Actions