13 Replies Latest reply on Nov 18, 2005 7:32 PM by Adrian Brock

    JBoss client API seems to leak files !

    Vignesh C K Newbie

      Hi,
      I run a JBoss 4.0.2 on a linux machine. I have a servlet which runs as a daemon and keeps browsing the queue for new messages. When I stop JBoss server / JBoss goes on for a busy state it starts opening Sockets from the client and never seems to be closing.

      I do a AUTO_ACK when i start the client session. When i do a netstat on the PID it says the client has sockets to the server in the Established state.

      Has anyone experienced this isssue. Or let me know what could go wrong here.

      One obvious solution is to make sesssion managed by itself. But wanted to make sure if there a patch/solution to this.

      Thanks
      Vignesh

        • 2. Re: JBoss client API seems to leak files !
          Vignesh C K Newbie

          JBoss Vesion : jboss-4.0.2
          JDK-Version : jdk 1.5_03

          The config level changes are , I tried making a jboss_home and a jboss_base.
          So I can change the binaries of JBoss when needed.

          You can look at the part of start script.


          export JBOSS_HOME=/opt/GEinet/jboss-4.0.2
          
          STATUS=10
          while [ $STATUS -eq 10 ]
          do
          # Execute the JVM
           "$JAVA" $JAVA_OPTS \
           -Djboss.base.dir=$JBOSS_BASE \
           -Djboss.server.base.dir=$JBOSS_BASE/server/ \
           -Djboss.server.base.url=file:$JBOSS_BASE/server/ \
           -Djboss.server.home.dir=$JBOSS_BASE/server/default \
           -Djboss.server.config.dir=$JBOSS_BASE/server/default/conf \
           -Djboss.server.lib.dir=$JBOSS_BASE/server/default/lib \
           -Djboss.server.data.dir=$JBOSS_BASE/server/default/data \
           -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" -classpath "$JBOSS_CLASSPATH" org.jboss.Main -c default >$JBOSS_CONSOLE 2>&1 &
           if [ ! -z "$JBOSS_PID" ]; then
           echo $! > $JBOSS_PID
           fi
           STATUS=$?
           echo "JBoss started with jvm code : $STATUS , you can find logs at $JBOSS_CONSOLE"
          done


          OS Info :

          uname -a
          Linux gealnx28 2.4.21-9.ELsmp #1 SMP Thu Jan 8 17:08:56 EST 2004 i686 i686 i386 GNU/Linux

          FD Max Size: 1024 (This is reached after a period of time)

          Problem StackTrace (Running on DEBUG MODE)
          -------------------

          2005-11-03 16:51:25,683 WARN [org.jboss.mq.il.uil2.UILServerILService] Failed to setup client connection
          java.net.SocketException: Too many open files
          at java.net.PlainSocketImpl.socketAccept(Native Method)
          at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
          at java.net.ServerSocket.implAccept(ServerSocket.java:450)
          at java.net.ServerSocket.accept(ServerSocket.java:421)
          at org.jboss.mq.il.uil2.UILServerILService.run(UILServerILService.java:124)
          at java.lang.Thread.run(Thread.java:595)


          Error Reproduction:
          ------------------------
          This happens after some hours since the server is started.


          Scenario:
          ------------

          I have a external system that puts messages into a queue and a servlet browsing and consuming this on a
          timeinterval. I run this on a while loop. When the fd limit is full this is what i get on the client side...


          StackTrace :
          --------------------------------
          2005-11-08 06:51:09,447|UIL2.SocketManager.ReadTask#7313 client=3.130.200.40:8093|DEBUG|org.jboss.mq.il.uil2.SocketManager|Created ObjectInputStream
          2005-11-08 06:51:09,448|TP-Processor23|DEBUG|org.jboss.mq.il.uil2.UILClientILService|Starting
          2005-11-08 06:51:09,448|UIL2.SocketManager.ReadTask#7315 client=3.130.200.40:8093|DEBUG|org.jboss.mq.il.uil2.SocketManager|Begin ReadTask.run
          2005-11-08 06:51:09,448|UIL2.SocketManager.WriteTask#7316 client=3.130.200.40:8093|DEBUG|org.jboss.mq.il.uil2.SocketManager|Begin WriteTask.run
          2005-11-08 06:51:09,448|UIL2.SocketManager.WriteTask#7316 client=3.130.200.40:8093|DEBUG|org.jboss.mq.il.uil2.SocketManager|Created ObjectOutputStream
          2005-11-08 06:51:09,449|UIL2.SocketManager.WriteTask#7316 client=3.130.200.40:8093|DEBUG|org.jboss.mq.il.uil2.SocketManager|End WriteTask.run
          2005-11-08 06:51:09,449|TP-Processor24|WARN|tptpgateway.init.InitServlet|Fatal Error while checking for new messages
          2005-11-08 06:51:09,482|TP-Processor24|ERROR|org.jboss.mq.SpyJMSException|org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable: (java.net.SocketException: Socket closed)
          at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:66)
          at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:51)
          at org.jboss.mq.Connection.authenticate(Connection.java:1118)
          at org.jboss.mq.Connection.(Connection.java:267)
          at org.jboss.mq.Connection.(Connection.java:338)
          at org.jboss.mq.SpyConnection.(SpyConnection.java:68)
          at org.jboss.mq.SpyConnectionFactory.createConnection(SpyConnectionFactory.java:87)
          at tptpgateway.init.InitServlet.areThereNewMessages(InitServlet.java:205)
          at tptpgateway.init.InitServlet.coreWork(InitServlet.java:137)
          at tptpgateway.init.InitServlet.processRequest(InitServlet.java:123)
          at tptpgateway.init.InitServlet.doGet(InitServlet.java:167)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:204)
          at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
          at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
          at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
          at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
          at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
          at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307)
          at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385)
          at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748)
          at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678)
          at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871)
          at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
          at java.lang.Thread.run(Thread.java:595)
          Caused by: java.net.SocketException: Socket closed
          at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)




          Here the code which runs on the servlet :
          ---------------------------------------------


          protected void coreWork(){
           try {
           // Start the Listner for consuming the messages
           logger.debug("Bootstrapping the Listner");
           while (RUN_AS_DAEMON_STATUS) {
           // Normal Execution
           if (areThereNewMessages()) {
           logger.debug("New Messages were found");
           reciever = new MessageReciever();
           reciever.connectAndRecieveMessages();
           reciever.disconnectReciever();
           } else {
           logger.debug("No Messages were found");
           }
           Thread.sleep(sleepingTime);
           }
          
           } catch (Throwable th) {
           logger.alert("Fatal Error occured in coreWork() !"+th.getMessage());
           logger.printStackTrace(th);
           logger.alert("Trying to recover from the error ,going back to core work");
           coreWork();
           }
          
           }
          
          
          
          
          
          
          private boolean areThereNewMessages() {
           boolean newMessageFound = false;
           try {
           logger.debug("Loading the JMSConfiguration");
           loadJMSConfig();
           Properties jndi = getInitialContextProperties();
          
           context = new InitialContext(jndi);
           // Look up the ConnectionFactory
           factory = (ConnectionFactory) context.lookup(jmsConfig
           .getAdminsteredConnFactoryName());
           // Look up the Desination
           dest = (Queue) context.lookup(jmsConfig.getInputJMSQueue());
          
           // create the connection
           connection = factory.createConnection();
          
           // create the session
           session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
          
           // create the browser
           browser = session.createBrowser(dest);
          
           // start the connection
           connection.start();
          
           Enumeration messages = browser.getEnumeration();
           while (messages.hasMoreElements()) {
           // set the flag to true
           newMessageFound = true;
           // Can remove this unwanted part
           Message message = (Message) messages.nextElement();
           if (message instanceof TextMessage) {
           TextMessage text = (TextMessage) message;
           String messageFromLaptop = text.getText();
           logger.debug("Browsed Msg From The Queue: " + messageFromLaptop);
           } else if (message != null) {
           logger.debug("Browsed non text message");
           }
           }
          
           } catch (Throwable th) {
           logger.alert("Fatal Error while checking for new messages");
           logger.printStackTrace(th);
           } finally {
           if (connection != null) {
           try {
           browser.close();
           session.close();
           connection.close();
           } catch (JMSException exception) {
           logger.alert("JMSException while disconnection connection",
           exception.toString());
           }
           }
           }
          
           return newMessageFound;
           }
          
          
          
           private Properties getInitialContextProperties() {
           Properties env = new Properties();
           env.put(Context.SECURITY_PRINCIPAL, "guest");
           env.put(Context.SECURITY_CREDENTIALS,"guest");
           env.put(Context.INITIAL_CONTEXT_FACTORY,"org.jboss.naming.HttpNamingContextFactory");
           env.put(Context.PROVIDER_URL, "http://gealnx28.appl.ge.com:8080/invoker/JNDIFactory");
           return env;
           }


          Hope this suffices to your comment.


          Thanks and warm regards
          Vignesh








          • 3. Re: JBoss client API seems to leak files !
            Vignesh C K Newbie

            JBoss Vesion : jboss-4.0.2
            JDK-Version : jdk 1.5_03

            The config level changes are , I tried making a jboss_home and a jboss_base.
            So I can change the binaries of JBoss when needed.

            You can look at the part of start script.


            export JBOSS_HOME=/opt/GEinet/jboss-4.0.2
            
            STATUS=10
            while [ $STATUS -eq 10 ]
            do
            # Execute the JVM
             "$JAVA" $JAVA_OPTS \
             -Djboss.base.dir=$JBOSS_BASE \
             -Djboss.server.base.dir=$JBOSS_BASE/server/ \
             -Djboss.server.base.url=file:$JBOSS_BASE/server/ \
             -Djboss.server.home.dir=$JBOSS_BASE/server/default \
             -Djboss.server.config.dir=$JBOSS_BASE/server/default/conf \
             -Djboss.server.lib.dir=$JBOSS_BASE/server/default/lib \
             -Djboss.server.data.dir=$JBOSS_BASE/server/default/data \
             -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" -classpath "$JBOSS_CLASSPATH" org.jboss.Main -c default >$JBOSS_CONSOLE 2>&1 &
             if [ ! -z "$JBOSS_PID" ]; then
             echo $! > $JBOSS_PID
             fi
             STATUS=$?
             echo "JBoss started with jvm code : $STATUS , you can find logs at $JBOSS_CONSOLE"
            done


            OS Info :

            uname -a
            Linux gealnx28 2.4.21-9.ELsmp #1 SMP Thu Jan 8 17:08:56 EST 2004 i686 i686 i386 GNU/Linux

            FD Max Size: 1024 (This is reached after a period of time)

            Problem StackTrace (Running on DEBUG MODE)
            -------------------

            2005-11-03 16:51:25,683 WARN [org.jboss.mq.il.uil2.UILServerILService] Failed to setup client connection
            java.net.SocketException: Too many open files
            at java.net.PlainSocketImpl.socketAccept(Native Method)
            at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
            at java.net.ServerSocket.implAccept(ServerSocket.java:450)
            at java.net.ServerSocket.accept(ServerSocket.java:421)
            at org.jboss.mq.il.uil2.UILServerILService.run(UILServerILService.java:124)
            at java.lang.Thread.run(Thread.java:595)


            Error Reproduction:
            ------------------------
            This happens after some hours since the server is started.


            Scenario:
            ------------

            I have a external system that puts messages into a queue and a servlet browsing and consuming this on a
            timeinterval. I run this on a while loop. When the fd limit is full this is what i get on the client side...


            StackTrace :
            --------------------------------
            2005-11-08 06:51:09,447|UIL2.SocketManager.ReadTask#7313 client=3.130.200.40:8093|DEBUG|org.jboss.mq.il.uil2.SocketManager|Created ObjectInputStream
            2005-11-08 06:51:09,448|TP-Processor23|DEBUG|org.jboss.mq.il.uil2.UILClientILService|Starting
            2005-11-08 06:51:09,448|UIL2.SocketManager.ReadTask#7315 client=3.130.200.40:8093|DEBUG|org.jboss.mq.il.uil2.SocketManager|Begin ReadTask.run
            2005-11-08 06:51:09,448|UIL2.SocketManager.WriteTask#7316 client=3.130.200.40:8093|DEBUG|org.jboss.mq.il.uil2.SocketManager|Begin WriteTask.run
            2005-11-08 06:51:09,448|UIL2.SocketManager.WriteTask#7316 client=3.130.200.40:8093|DEBUG|org.jboss.mq.il.uil2.SocketManager|Created ObjectOutputStream
            2005-11-08 06:51:09,449|UIL2.SocketManager.WriteTask#7316 client=3.130.200.40:8093|DEBUG|org.jboss.mq.il.uil2.SocketManager|End WriteTask.run
            2005-11-08 06:51:09,449|TP-Processor24|WARN|tptpgateway.init.InitServlet|Fatal Error while checking for new messages
            2005-11-08 06:51:09,482|TP-Processor24|ERROR|org.jboss.mq.SpyJMSException|org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable: (java.net.SocketException: Socket closed)
            at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:66)
            at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:51)
            at org.jboss.mq.Connection.authenticate(Connection.java:1118)
            at org.jboss.mq.Connection.(Connection.java:267)
            at org.jboss.mq.Connection.(Connection.java:338)
            at org.jboss.mq.SpyConnection.(SpyConnection.java:68)
            at org.jboss.mq.SpyConnectionFactory.createConnection(SpyConnectionFactory.java:87)
            at tptpgateway.init.InitServlet.areThereNewMessages(InitServlet.java:205)
            at tptpgateway.init.InitServlet.coreWork(InitServlet.java:137)
            at tptpgateway.init.InitServlet.processRequest(InitServlet.java:123)
            at tptpgateway.init.InitServlet.doGet(InitServlet.java:167)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
            at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:204)
            at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
            at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
            at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
            at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307)
            at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385)
            at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748)
            at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678)
            at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871)
            at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
            at java.lang.Thread.run(Thread.java:595)
            Caused by: java.net.SocketException: Socket closed
            at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)




            Here the code which runs on the servlet :
            ---------------------------------------------


            protected void coreWork(){
             try {
             // Start the Listner for consuming the messages
             logger.debug("Bootstrapping the Listner");
             while (RUN_AS_DAEMON_STATUS) {
             // Normal Execution
             if (areThereNewMessages()) {
             logger.debug("New Messages were found");
             reciever = new MessageReciever();
             reciever.connectAndRecieveMessages();
             reciever.disconnectReciever();
             } else {
             logger.debug("No Messages were found");
             }
             Thread.sleep(sleepingTime);
             }
            
             } catch (Throwable th) {
             logger.alert("Fatal Error occured in coreWork() !"+th.getMessage());
             logger.printStackTrace(th);
             logger.alert("Trying to recover from the error ,going back to core work");
             coreWork();
             }
            
             }
            
            
            
            
            
            
            private boolean areThereNewMessages() {
             boolean newMessageFound = false;
             try {
             logger.debug("Loading the JMSConfiguration");
             loadJMSConfig();
             Properties jndi = getInitialContextProperties();
            
             context = new InitialContext(jndi);
             // Look up the ConnectionFactory
             factory = (ConnectionFactory) context.lookup(jmsConfig
             .getAdminsteredConnFactoryName());
             // Look up the Desination
             dest = (Queue) context.lookup(jmsConfig.getInputJMSQueue());
            
             // create the connection
             connection = factory.createConnection();
            
             // create the session
             session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
            
             // create the browser
             browser = session.createBrowser(dest);
            
             // start the connection
             connection.start();
            
             Enumeration messages = browser.getEnumeration();
             while (messages.hasMoreElements()) {
             // set the flag to true
             newMessageFound = true;
             // Can remove this unwanted part
             Message message = (Message) messages.nextElement();
             if (message instanceof TextMessage) {
             TextMessage text = (TextMessage) message;
             String messageFromLaptop = text.getText();
             logger.debug("Browsed Msg From The Queue: " + messageFromLaptop);
             } else if (message != null) {
             logger.debug("Browsed non text message");
             }
             }
            
             } catch (Throwable th) {
             logger.alert("Fatal Error while checking for new messages");
             logger.printStackTrace(th);
             } finally {
             if (connection != null) {
             try {
             browser.close();
             session.close();
             connection.close();
             } catch (JMSException exception) {
             logger.alert("JMSException while disconnection connection",
             exception.toString());
             }
             }
             }
            
             return newMessageFound;
             }
            
            
            
             private Properties getInitialContextProperties() {
             Properties env = new Properties();
             env.put(Context.SECURITY_PRINCIPAL, "guest");
             env.put(Context.SECURITY_CREDENTIALS,"guest");
             env.put(Context.INITIAL_CONTEXT_FACTORY,"org.jboss.naming.HttpNamingContextFactory");
             env.put(Context.PROVIDER_URL, "http://gealnx28.appl.ge.com:8080/invoker/JNDIFactory");
             return env;
             }


            Hope this suffices to your comment.

            Infact there is another person with the same issue

            http://www.jboss.com/index.html?module=bb&op=viewtopic&t=66105

            Thanks and warm regards
            Vignesh








            • 4. Re: JBoss client API seems to leak files !
              Vignesh C K Newbie

              here is what i see after adding jboss debug on the client side....

              2005-11-10 00:49:17,666|TP-Processor24|DEBUG|tptpgateway.init.InitServlet|Loading the JMSConfiguration
               10919 2005-11-10 00:49:17,666|TP-Processor24|DEBUG|tptpgateway.init.InitServlet|JMSConfiguration=jmsprovider=JBOSS,
               10920 inputJMSQueue=queue/TPTP_IN_QUEUE,
               10921 outputJMSQueue=queue/TPTP_OUT_QUEUE,
               10922 adminsteredConnFactoryName=ConnectionFactory,
               10923 jmsProviderLocation=http://ap1lnx120.appl.ge.com:8080/invoker/JNDIFactory,
               10924 jmsUserRoleName=guest,
               10925 jmsUserName=guest,
               10926 jmsUserPassword=guest,
               10927
               10928 2005-11-10 00:49:17,676|TP-Processor24|DEBUG|org.jboss.mq.referenceable.SpyConnectionFactoryObjectFactory|Extracting S pyConnectionFactory from reference
               10929 2005-11-10 00:49:17,677|TP-Processor24|DEBUG|org.jboss.mq.referenceable.SpyConnectionFactoryObjectFactory|The GenericC onnectionFactory is: GenericConnectionFactory[server=org.jboss.mq.il.uil2.UILServerIL@1022de4 connectionProperties={UI L_PORT_KEY=8093, ClientILService=org.jboss.mq.il.uil2.UILClientILService, UIL_ADDRESS_KEY=3.130.233.117, UIL_TCPNODELA Y_KEY=yes, PingPeriod=60000, UIL_CHUNKSIZE_KEY=1000000, UIL_RECEIVE_REPLIES_KEY=No, UIL_BUFFERSIZE_KEY=2048}]
               10930 2005-11-10 00:49:17,680|TP-Processor24|DEBUG|org.jboss.mq.referenceable.SpyDestinationObjectFactory|SpyDestinationObje ctFactory->getObjectInstance()
               10931 2005-11-10 00:49:17,680|TP-Processor24|TRACE|org.jboss.mq.Connection|Connection Initializing userName=null Connection@ 256294[clientID=null rcvstate=STOPPED]
               10932 2005-11-10 00:49:17,680|TP-Processor24|TRACE|org.jboss.mq.Connection|Getting the serverIL Connection@256294[clientID=n ull rcvstate=STOPPED]
               10933 2005-11-10 00:49:17,680|TP-Processor24|TRACE|org.jboss.mq.Connection|serverIL=org.jboss.mq.il.uil2.UILServerIL@bfd66a Connection@256294[clientID=null rcvstate=STOPPED]
               10934 2005-11-10 00:49:17,680|TP-Processor24|TRACE|org.jboss.mq.Connection|Authenticating user null Connection@256294[client ID=null rcvstate=STOPPED]
               10935 2005-11-10 00:49:17,680|TP-Processor24|TRACE|org.jboss.mq.il.uil2.UILServerIL|Connecting to : ap1lnx120.appl.ge.com/3. 130.233.117:8093
               10936 2005-11-10 00:49:17,680|TP-Processor24|TRACE|org.jboss.mq.il.uil2.UILServerIL|Connecting with addr=3.130.233.117, port =8093, localAddr=null, localPort=0, socketFactory=javax.net.DefaultSocketFactory@b113c7, enableTcpNoDelay=true, buffer Size=2048, chunkSize=1000000
               10937 2005-11-10 00:49:17,680|TP-Processor24|TRACE|org.jboss.mq.il.uil2.UILServerIL|Begin connect loop, maxRetries=10, delay =0
               10938 2005-11-10 00:49:17,680|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|start called
               10939 java.lang.Exception: Start stack trace
               10940 at org.jboss.mq.il.uil2.SocketManager.start(SocketManager.java:96)
               10941 at org.jboss.mq.il.uil2.UILServerIL.createConnection(UILServerIL.java:666)
               10942 at org.jboss.mq.il.uil2.UILServerIL.getSocketMgr(UILServerIL.java:532)
               10943 at org.jboss.mq.il.uil2.UILServerIL.authenticate(UILServerIL.java:334)
               10944 at org.jboss.mq.Connection.authenticate(Connection.java:1114)
               10945 at org.jboss.mq.Connection.<init>(Connection.java:267)
               10946 at org.jboss.mq.Connection.<init>(Connection.java:338)
               10947 at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:68)
               10948 at org.jboss.mq.SpyConnectionFactory.createConnection(SpyConnectionFactory.java:87)
               at tptpgateway.init.InitServlet.areThereNewMessages(InitServlet.java:205)
               10950 at tptpgateway.init.InitServlet.coreWork(InitServlet.java:137)
               10951 at tptpgateway.init.InitServlet.processRequest(InitServlet.java:123)
               10952 at tptpgateway.init.InitServlet.doGet(InitServlet.java:167)
               10953 at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
               10954 at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
               10955 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
               10956 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
               10957 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:204)
               10958 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
               10959 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
               10960 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
               10961 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
               10962 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
               10963 at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307)
               10964 at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385)
               10965 at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748)
               10966 at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678)
               10967 at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871)
               10968 at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
               10969 at java.lang.Thread.run(Thread.java:595)
               10970 2005-11-10 00:49:17,681|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|Begin internalSendMessage, round-trip msg=org.jboss.mq.il.uil2.msgs.CheckUserMsg6815360[msgType: m_authenticate, msgID: 9, error: null]
               10971 2005-11-10 00:49:17,682|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|DEBUG|org.jboss.mq.il.uil2.SocketManag er|Begin ReadTask.run
               10972 2005-11-10 00:49:17,682|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|DEBUG|org.jboss.mq.il.uil2.SocketMana ger|Begin WriteTask.run
               10973 2005-11-10 00:49:17,682|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|DEBUG|org.jboss.mq.il.uil2.SocketMana ger|Created ObjectOutputStream
               10974 2005-11-10 00:49:17,682|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketMana ger|Write msg: org.jboss.mq.il.uil2.msgs.CheckUserMsg6815360[msgType: m_authenticate, msgID: 9, error: null]
               10975 2005-11-10 00:49:17,683|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|DEBUG|org.jboss.mq.il.uil2.SocketManag er|Created ObjectInputStream
               10976 2005-11-10 00:49:17,683|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msgType: m_authenticate, msgID: 9
               10977 2005-11-10 00:49:17,683|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Found replyMap msg: org.jboss.mq.il.uil2.msgs.CheckUserMsg6815360[msgType: m_authenticate, msgID: 9, error: null]
               10978 2005-11-10 00:49:17,683|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msg reply: org.jboss.mq.il.uil2.msgs.CheckUserMsg6815360[msgType: m_authenticate, msgID: 9, error: null]
               10979 2005-11-10 00:49:17,683|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|End internalSendMessage, msg=org.jboss .mq.il.uil2.msgs.CheckUserMsg6815360[msgType: m_authenticate, msgID: 9, error: null]
               10980 2005-11-10 00:49:17,683|TP-Processor24|TRACE|org.jboss.mq.Connection|Starting the client il Connection@256294[clientID =null rcvstate=STOPPED]
               2005-11-10 00:49:17,683|TP-Processor24|TRACE|org.jboss.mq.GenericConnectionFactory|Handing out ClientIL: org.jboss.mq. il.uil2.UILClientILService
               10982 2005-11-10 00:49:17,683|TP-Processor24|DEBUG|org.jboss.mq.il.uil2.UILClientILService|Starting
               10983 2005-11-10 00:49:17,683|TP-Processor24|TRACE|org.jboss.mq.Connection|Using client id org.jboss.mq.il.uil2.UILClientILS ervice@175b7f9 Connection@256294[clientID=null rcvstate=STOPPED]
               10984 2005-11-10 00:49:17,683|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|Begin internalSendMessage, round-trip msg=org.jboss.mq.il.uil2.msgs.ConnectionTokenMsg25250173[msgType: m_setSpyDistributedConnection, msgID: 10, error: nul l]
               10985 2005-11-10 00:49:17,684|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketMana ger|Write msg: org.jboss.mq.il.uil2.msgs.ConnectionTokenMsg25250173[msgType: m_setSpyDistributedConnection, msgID: 10, error: null]
               10986 2005-11-10 00:49:17,684|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msgType: m_setSpyDistributedConnection, msgID: 10
               10987 2005-11-10 00:49:17,684|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Found replyMap msg: org.jboss.mq.il.uil2.msgs.ConnectionTokenMsg25250173[msgType: m_setSpyDistributedConnection, ms gID: 10, error: null]
               10988 2005-11-10 00:49:17,684|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msg reply: org.jboss.mq.il.uil2.msgs.ConnectionTokenMsg25250173[msgType: m_setSpyDistributedConnection, msgID: 10, error: null]
               10989 2005-11-10 00:49:17,684|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|End internalSendMessage, msg=org.jboss .mq.il.uil2.msgs.ConnectionTokenMsg25250173[msgType: m_setSpyDistributedConnection, msgID: 10, error: null]
               10990 2005-11-10 00:49:17,684|TP-Processor24|TRACE|org.jboss.mq.Connection|Creating XAResourceManager Connection@256294[toke n=ConnectionToken:null/aa78f5118553f8356edc91e2780e6af9 rcvstate=STOPPED]
               10991 2005-11-10 00:49:17,684|TP-Processor24|TRACE|org.jboss.mq.Connection|Starting the ping thread Connection@256294[token= ConnectionToken:null/aa78f5118553f8356edc91e2780e6af9 rcvstate=STOPPED]
               10992 2005-11-10 00:49:17,684|TP-Processor24|TRACE|org.jboss.mq.Connection|Connection establishment successful Connection@25 6294[token=ConnectionToken:null/aa78f5118553f8356edc91e2780e6af9 rcvstate=STOPPED]
               10993 2005-11-10 00:49:17,685|TP-Processor24|TRACE|org.jboss.mq.Connection|Checking clientID=null Connection@256294[token=Co nnectionToken:null/aa78f5118553f8356edc91e2780e6af9 rcvstate=STOPPED]
               10994 2005-11-10 00:49:17,685|TP-Processor24|TRACE|org.jboss.mq.Connection|Ask for an id Connection@256294[token=ConnectionT oken:null/aa78f5118553f8356edc91e2780e6af9 rcvstate=STOPPED]
               10995 2005-11-10 00:49:17,685|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|Begin internalSendMessage, round-trip msg=org.jboss.mq.il.uil2.msgs.GetIDMsg8640702[msgType: m_getID, msgID: 11, error: null]
               10996 2005-11-10 00:49:17,685|Connection Monitor Thread|TRACE|org.jboss.mq.Connection|PING 1131601757685 Connection@256294[t oken=ConnectionToken:null/aa78f5118553f8356edc91e2780e6af9 rcvstate=STOPPED]
               10997 2005-11-10 00:49:17,685|Connection Monitor Thread|TRACE|org.jboss.mq.il.uil2.SocketManager|Begin internalSendMessage, one-way msg=org.jboss.mq.il.uil2.msgs.PingMsg713167[msgType: m_ping, msgID: 12, error: null]
               10998 2005-11-10 00:49:17,685|Connection Monitor Thread|TRACE|org.jboss.mq.il.uil2.SocketManager|End internalSendMessage, ms g=org.jboss.mq.il.uil2.msgs.PingMsg713167[msgType: m_ping, msgID: 12, error: null]
               10999 2005-11-10 00:49:17,685|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketMana ger|Write msg: org.jboss.mq.il.uil2.msgs.GetIDMsg8640702[msgType: m_getID, msgID: 11, error: null]
               11000 2005-11-10 00:49:17,685|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketMana ger|Write msg: org.jboss.mq.il.uil2.msgs.PingMsg713167[msgType: m_ping, msgID: 12, error: null]
               2005-11-10 00:49:17,686|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msgType: m_pong, msgID: -2147432568
               11002 2005-11-10 00:49:17,686|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read new msg: org.jboss.mq.il.uil2.msgs.PingMsg7272378[msgType: m_pong, msgID: -2147432568, error: null]
               11003 2005-11-10 00:49:17,686|UIL2(SocketManager.MsgPool@95f290 client=3.130.233.117:8093)#1|TRACE|org.jboss.mq.il.uil2.UILC lientILService|Begin handleMsg, msgType: 24
               11004 2005-11-10 00:49:17,686|UIL2(SocketManager.MsgPool@95f290 client=3.130.233.117:8093)#1|TRACE|org.jboss.mq.Connection|P ONG serverTime=1131601757685 Connection@256294[token=ConnectionToken:null/aa78f5118553f8356edc91e2780e6af9 rcvstate=ST OPPED]
               11005 2005-11-10 00:49:17,686|UIL2(SocketManager.MsgPool@95f290 client=3.130.233.117:8093)#1|TRACE|org.jboss.mq.il.uil2.UILC lientILService|End handleMsg
               11006 2005-11-10 00:49:17,686|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msgType: m_getID, msgID: 11
               11007 2005-11-10 00:49:17,686|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Found replyMap msg: org.jboss.mq.il.uil2.msgs.GetIDMsg8640702[msgType: m_getID, msgID: 11, error: null]
               11008 2005-11-10 00:49:17,686|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msg reply: org.jboss.mq.il.uil2.msgs.GetIDMsg8640702[msgType: m_getID, msgID: 11, error: null]
               11009 2005-11-10 00:49:17,686|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|End internalSendMessage, msg=org.jboss .mq.il.uil2.msgs.GetIDMsg8640702[msgType: m_getID, msgID: 11, error: null]
               11010 2005-11-10 00:49:17,686|TP-Processor24|TRACE|org.jboss.mq.Connection|ClientID established Connection@256294[token=Conn ectionToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 rcvstate=STOPPED]
               11011 2005-11-10 00:49:17,687|TP-Processor24|TRACE|org.jboss.mq.SpySession|New session SpySession@20730792[tx=false ack=AUTO txid=null RUNNING connection=Connection@256294[token=ConnectionToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 rcvsta te=STOPPED]]
               11012 2005-11-10 00:49:17,687|TP-Processor24|TRACE|org.jboss.mq.Connection|Starting connection Connection@256294[token=Conne ctionToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 rcvstate=STARTED]
               11013 2005-11-10 00:49:17,687|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|Begin internalSendMessage, round-trip msg=org.jboss.mq.il.uil2.msgs.EnableConnectionMsg26757789[msgType: m_setEnabled, msgID: 13, error: null]
               11014 2005-11-10 00:49:17,687|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketMana ger|Write msg: org.jboss.mq.il.uil2.msgs.EnableConnectionMsg26757789[msgType: m_setEnabled, msgID: 13, error: null]
               11015 2005-11-10 00:49:17,687|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msgType: m_setEnabled, msgID: 13
               11016 2005-11-10 00:49:17,687|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Found replyMap msg: org.jboss.mq.il.uil2.msgs.EnableConnectionMsg26757789[msgType: m_setEnabled, msgID: 13, error: null]
               11017 2005-11-10 00:49:17,687|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msg reply: org.jboss.mq.il.uil2.msgs.EnableConnectionMsg26757789[msgType: m_setEnabled, msgID: 13, error: null ]
               11018 2005-11-10 00:49:17,687|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|End internalSendMessage, msg=org.jboss .mq.il.uil2.msgs.EnableConnectionMsg26757789[msgType: m_setEnabled, msgID: 13, error: null]
               11019 2005-11-10 00:49:17,687|TP-Processor24|TRACE|org.jboss.mq.Connection|Browsing queue=QUEUE.TPTP_IN_QUEUE selector=null Connection@256294[token=ConnectionToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 rcvstate=STARTED]
               11020 2005-11-10 00:49:17,687|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|Begin internalSendMessage, round-trip msg=org.jboss.mq.il.uil2.msgs.BrowseMsg21668571[msgType: m_browse, msgID: 14, error: null]
               2005-11-10 00:49:17,687|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketMana ger|Write msg: org.jboss.mq.il.uil2.msgs.BrowseMsg21668571[msgType: m_browse, msgID: 14, error: null]
               11022 2005-11-10 00:49:17,688|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msgType: m_browse, msgID: 14
               11023 2005-11-10 00:49:17,688|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Found replyMap msg: org.jboss.mq.il.uil2.msgs.BrowseMsg21668571[msgType: m_browse, msgID: 14, error: null]
               11024 2005-11-10 00:49:17,688|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msg reply: org.jboss.mq.il.uil2.msgs.BrowseMsg21668571[msgType: m_browse, msgID: 14, error: null]
               11025 2005-11-10 00:49:17,688|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|End internalSendMessage, msg=org.jboss .mq.il.uil2.msgs.BrowseMsg21668571[msgType: m_browse, msgID: 14, error: null]
               11026 2005-11-10 00:49:17,688|TP-Processor24|TRACE|org.jboss.mq.SpySession|Session closing SpySession@20730792[tx=false ack= AUTO txid=null RUNNING CLOSED connection=Connection@256294[token=ConnectionToken:ID:17534/aa78f5118553f8356edc91e2780e 6af9 rcvstate=STARTED]]
               11027 2005-11-10 00:49:17,688|TP-Processor24|TRACE|org.jboss.mq.SpySession|Closing consumers SpySession@20730792[tx=false ac k=AUTO txid=null RUNNING CLOSED connection=Connection@256294[token=ConnectionToken:ID:17534/aa78f5118553f8356edc91e278 0e6af9 rcvstate=STARTED]]
               11028 2005-11-10 00:49:17,688|TP-Processor24|TRACE|org.jboss.mq.SpySession|Close handling unacknowledged messages SpySession @20730792[tx=false ack=AUTO txid=null RUNNING CLOSED connection=Connection@256294[token=ConnectionToken:ID:17534/aa78f 5118553f8356edc91e2780e6af9 rcvstate=STARTED]]
               11029 2005-11-10 00:49:17,688|TP-Processor24|TRACE|org.jboss.mq.SpySession|Informing connection of close SpySession@20730792 [tx=false ack=AUTO txid=null RUNNING CLOSED connection=Connection@256294[token=ConnectionToken:ID:17534/aa78f5118553f8 356edc91e2780e6af9 rcvstate=STARTED]]
               11030 2005-11-10 00:49:17,688|TP-Processor24|TRACE|org.jboss.mq.Connection|Closing session SpySession@20730792[tx=false ack= AUTO txid=null RUNNING CLOSED connection=Connection@256294[token=ConnectionToken:ID:17534/aa78f5118553f8356edc91e2780e 6af9 rcvstate=STARTED]]
               11031 2005-11-10 00:49:17,689|TP-Processor24|TRACE|org.jboss.mq.Connection|Closing connection Connection@256294[token=Connec tionToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 rcvstate=STARTED]
               11032 2005-11-10 00:49:17,689|TP-Processor24|TRACE|org.jboss.mq.Connection|Stopping connection Connection@256294[token=Conne ctionToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 CLOSING rcvstate=STOPPED]
               11033 2005-11-10 00:49:17,689|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|Begin internalSendMessage, round-trip msg=org.jboss.mq.il.uil2.msgs.EnableConnectionMsg19220932[msgType: m_setEnabled, msgID: 15, error: null]
               11034 2005-11-10 00:49:17,689|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketMana ger|Write msg: org.jboss.mq.il.uil2.msgs.EnableConnectionMsg19220932[msgType: m_setEnabled, msgID: 15, error: null]
               11035 2005-11-10 00:49:17,689|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msgType: m_setEnabled, msgID: 15
               11036 2005-11-10 00:49:17,689|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Found replyMap msg: org.jboss.mq.il.uil2.msgs.EnableConnectionMsg19220932[msgType: m_setEnabled, msgID: 15, error: null]
               11037 2005-11-10 00:49:17,689|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msg reply: org.jboss.mq.il.uil2.msgs.EnableConnectionMsg19220932[msgType: m_setEnabled, msgID: 15, error: null ]
               11038 2005-11-10 00:49:17,689|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|End internalSendMessage, msg=org.jboss .mq.il.uil2.msgs.EnableConnectionMsg19220932[msgType: m_setEnabled, msgID: 15, error: null]
               2005-11-10 00:49:17,689|TP-Processor24|TRACE|org.jboss.mq.Connection|Closing sessions Connection@256294[token=Connecti onToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 CLOSING rcvstate=STOPPED]
               11040 2005-11-10 00:49:17,689|TP-Processor24|TRACE|org.jboss.mq.Connection|Closed sessions Connection@256294[token=Connectio nToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 CLOSING rcvstate=STOPPED]
               11041 2005-11-10 00:49:17,689|TP-Processor24|TRACE|org.jboss.mq.Connection|Notifying the server of close Connection@256294[t oken=ConnectionToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 CLOSING rcvstate=STOPPED]
               11042 2005-11-10 00:49:17,689|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|Begin internalSendMessage, round-trip msg=org.jboss.mq.il.uil2.msgs.CloseMsg17691874[msgType: m_connectionClosing, msgID: 16, error: null]
               11043 2005-11-10 00:49:17,689|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketMana ger|Write msg: org.jboss.mq.il.uil2.msgs.CloseMsg17691874[msgType: m_connectionClosing, msgID: 16, error: null]
               11044 2005-11-10 00:49:17,689|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msgType: m_connectionClosing, msgID: 16
               11045 2005-11-10 00:49:17,689|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Found replyMap msg: org.jboss.mq.il.uil2.msgs.CloseMsg17691874[msgType: m_connectionClosing, msgID: 16, error: null ]
               11046 2005-11-10 00:49:17,689|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Read msg reply: org.jboss.mq.il.uil2.msgs.CloseMsg17691874[msgType: m_connectionClosing, msgID: 16, error: null]
               11047 2005-11-10 00:49:17,690|TP-Processor24|TRACE|org.jboss.mq.il.uil2.SocketManager|End internalSendMessage, msg=org.jboss .mq.il.uil2.msgs.CloseMsg17691874[msgType: m_connectionClosing, msgID: 16, error: null]
               11048 2005-11-10 00:49:17,690|TP-Processor24|TRACE|org.jboss.mq.Connection|Stopping ping thread Connection@256294[token=Conn ectionToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 CLOSING rcvstate=STOPPED]
               11049 2005-11-10 00:49:17,690|TP-Processor24|TRACE|org.jboss.mq.Connection|Stopping the ClientIL service Connection@256294[t oken=ConnectionToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 CLOSING rcvstate=STOPPED]
               11050 2005-11-10 00:49:17,690|TP-Processor24|DEBUG|org.jboss.mq.il.uil2.UILClientILService|Stopping
               11051 2005-11-10 00:49:17,690|TP-Processor24|TRACE|org.jboss.mq.Connection|Disconnected from server Connection@256294[token= ConnectionToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 CLOSED rcvstate=STOPPED]
               11052 2005-11-10 00:49:17,690|TP-Processor24|DEBUG|tptpgateway.init.InitServlet|No Messages were found
               11053 2005-11-10 00:49:17,690|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketMana ger|WriteTask was interrupted
               11054 java.lang.InterruptedException
               11055 at java.lang.Object.wait(Native Method)
               11056 at java.lang.Object.wait(Object.java:474)
               11057 at EDU.oswego.cs.dl.util.concurrent.LinkedQueue.take(LinkedQueue.java:122)
               11058 at org.jboss.mq.il.uil2.SocketManager$WriteTask.run(SocketManager.java:492)
               11059 at java.lang.Thread.run(Thread.java:595)
               11060 2005-11-10 00:49:17,690|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.il.uil2.SocketManag er|Exiting on IOE
               11061 java.net.SocketException: Socket closed
               11062 at java.net.SocketInputStream.socketRead0(Native Method)
               11063 at java.net.SocketInputStream.read(SocketInputStream.java:129)
               11064 at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
               11065 at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
               11066 at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:67)
               11067 at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2200)
               11068 at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2380)
               11069 at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2447)
               11070 at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2519)
               11071 at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2668)
               11072 at java.io.ObjectInputStream.readByte(ObjectInputStream.java:864)
               11073 at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:290)
               11074 at java.lang.Thread.run(Thread.java:595)
               11075 2005-11-10 00:49:17,690|UIL2.SocketManager.WriteTask#4 client=3.130.233.117:8093|DEBUG|org.jboss.mq.il.uil2.SocketMana ger|End WriteTask.run
               11076 2005-11-10 00:49:17,690|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|TRACE|org.jboss.mq.Connection|Notified of failure reason=Exiting on IOE Connection@256294[token=ConnectionToken:ID:17534/aa78f5118553f8356edc91e2780e6af9 CL OSED rcvstate=STOPPED]
               11077 java.net.SocketException: Socket closed
               11078 at java.net.SocketInputStream.socketRead0(Native Method)
               11079 at java.net.SocketInputStream.read(SocketInputStream.java:129)
               11080 at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
               11081 at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
               11082 at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:67)
               11083 at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2200)
               11084 at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2380)
               11085 at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2447)
               11086 at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2519)
               11087 at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2668)
               11088 at java.io.ObjectInputStream.readByte(ObjectInputStream.java:864)
               11089 at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:290)
               11090 at java.lang.Thread.run(Thread.java:595)
               11091 2005-11-10 00:49:17,691|UIL2.SocketManager.ReadTask#3 client=3.130.233.117:8093|DEBUG|org.jboss.mq.il.uil2.SocketManag er|End ReadTask.run



              • 5. Re: JBoss client API seems to leak files !
                Adrian Brock Master

                The logging is useless

                If it couldn't even create the connection:

                2005-11-08 06:51:09,482|TP-Processor24|ERROR|org.jboss.mq.SpyJMSException|org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable: (java.net.SocketException: Socket closed)
                at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:66)
                at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:51)
                at org.jboss.mq.Connection.authenticate(Connection.java:1118)
                at org.jboss.mq.Connection.(Connection.java:267)
                at org.jboss.mq.Connection.(Connection.java:338)
                at org.jboss.mq.SpyConnection.(SpyConnection.java:68)
                at org.jboss.mq.SpyConnectionFactory.createConnection(SpyConnectionFactory.java:87)
                at tptpgateway.init.InitServlet.areThereNewMessages(InitServlet.java:205)
                


                how did it manage to create the session?
                11011 2005-11-10 00:49:17,687|TP-Processor24|TRACE|org.jboss.mq.SpySession|New session SpySession@
                20730792[tx=false ack=AUTO txid=null RUNNING connection=Connection@256294[token=ConnectionTo
                ken:ID:17534/aa78f5118553f8356edc91e2780e6af9 rcvsta te=STOPPED]]
                


                Answer: Because these are not the same event.

                • 6. Re: JBoss client API seems to leak files !
                  gerald zhou Newbie

                  Oh, i have same problem withe you. When i increase the max open file number on my linux system. It would hold on more than one or two days.

                  • 7. Re: JBoss client API seems to leak files !
                    Adrian Brock Master

                    Obviously broken code, that is described in the FAQ:

                    } finally {
                     if (connection != null) {
                     try {
                     browser.close(); // ERROR -> NO CLOSE
                     session.close();
                     connection.close();
                     } catch (JMSException exception) {
                     logger.alert("JMSException while disconnection connection",
                     exception.toString());
                     }
                     }
                    


                    And the whole thing is an anti-pattern.
                    You should be using one permenant connection with one session per thread.
                    Or use a pool.

                    • 8. Re: JBoss client API seems to leak files !
                      Adrian Brock Master

                       

                      "geniusfox" wrote:
                      Oh, i have same problem withe you. When i increase the max open file number on my linux system. It would hold on more than one or two days.


                      http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp
                      ME TOO

                      • 9. Re: JBoss client API seems to leak files !
                        Adrian Brock Master

                         

                        When i increase the max open file number on my linux system


                        Speak to your system administrator about to use lsof.

                        • 10. Re: JBoss client API seems to leak files !
                          Vignesh C K Newbie

                          Adrian,
                          Iam using a single connection and things seems to be working.
                          (And stopping/starting the connection without closing them)

                          Iam not sure of the anti-pattern theing.

                          Why do you call it anti-pattern ?

                          I dont see why should it keep the connections establised from the client to the server. One more intresting this is that there are timout values for the sockets on the server config xmls and i dont see them work on these conditions.



                          lsof could give you files open , a netstat can give more info (tp connection from the client to the server seems to be on a establised condition)or /proc/'PID'/fd dir can give the file handles . From there you could analyze the state of them.

                          Thanks
                          Vignesh

                          • 11. Re: JBoss client API seems to leak files !
                            Adrian Brock Master

                             

                            "viky4u" wrote:

                            Why do you call it anti-pattern ?


                            http://wiki.jboss.org/wiki/Wiki.jsp?page=HelpBugReport
                            Read the spec


                            One more intresting this is that there are timout values for the sockets on the server config xmls and i dont see them work on these conditions.


                            Why would the timeout happen? The client still has the connection open and it hasn't crashed.

                            • 12. Re: JBoss client API seems to leak files !
                              Vignesh C K Newbie

                              I ran the whole thing with a debugger at different points. The call to connection.close() occurs everytime. I didnt run the debugger ,for the continous while loop.

                              One more question , this is totally out of this context. Iam trying to build a standard image of JBoss which abides to our existing standard setup. I want all the logs to be sent to my own mount point. But the boot.log is pointed to ${jboss.server.home.dir}/log/boot.log at run.jar.

                              How do i overide this behaviour as log4j.xml is considerd after bootstrap.

                              Thanks and warm regards
                              Vignesh
                              vignesh.kc@ge.com

                              • 13. Re: JBoss client API seems to leak files !
                                Adrian Brock Master

                                Correct it is offtopic and the wrong forum.

                                But it was also missing from the wiki page:
                                http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProperties

                                Though it can be easily found in the log4j doco.