2 Replies Latest reply on Sep 25, 2007 10:26 AM by glad01

    JBoss deployment on XP loops

    iyerji2

      Hi
      I have a jboss app (that is copied off of default.)
      It runs fine on my desktop (windows XP)
      when I try running it on another XP box it
      starts up and immediately ends up w/ the socket exception below
      which loops and makes a big server.log file.

      conf/jboss-service.xml file looks fine. There are no differences
      (i'm zipping up the server/myApp directory and deploying to the
      other machine)
      Something is different on the new machine.
      Any clues would help
      -Thanks

      2007-08-28 14:56:13,328 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
      2007-08-28 14:56:13,328 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)] Started in 21s:500ms
      2007-08-28 14:56:14,031 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.Listener_2] Listener - IOException
      2007-08-28 14:56:14,031 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.Listener_2] Listener - IOException
      2007-08-28 14:56:14,031 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.Listener_2] Listener - IOException
      2007-08-28 14:56:14,031 ERROR [org.jboss.naming.Naming] Naming accept handler stopping
      java.net.SocketException: socket closed
       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.jnp.server.Main$AcceptHandler.run(Main.java:481)
       at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:148)
       at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
       at java.lang.Thread.run(Thread.java:595)
      2007-08-28 14:56:14,031 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.Listener_2] Listener - IOException
      2007-08-28 14:56:14,046 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[127.0.0.1:3873] failed to handle socket
      java.net.SocketException: socket closed
       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.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
       at java.lang.Thread.run(Thread.java:595)
      2007-08-28 14:56:14,046 ERROR [org.jboss.invocation.pooled.server.PooledInvoker] Failed to accept socket connection
      java.net.SocketException: socket closed
       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.invocation.pooled.server.PooledInvoker.run(PooledInvoker.java:262)
       at java.lang.Thread.run(Thread.java:595)
      2007-08-28 14:56:14,046 ERROR [org.apache.tomcat.util.net.JIoEndpoint] Socket accept failed
      java.net.SocketException: socket closed
       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.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:61)
       at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:310)
       at java.lang.Thread.run(Thread.java:595)
      2007-08-28 14:56:14,046 ERROR [org.jboss.naming.Naming] Naming accept handler stopping
      java.net.SocketException: socket closed
       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.jnp.server.Main$AcceptHandler.run(Main.java:481)
       at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:148)
       at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
       at java.lang.Thread.run(Thread.java:595)
      2007-08-28 14:56:14,046 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.Listener_2] Listener - IOException
      2007-08-28 14:56:14,046 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[127.0.0.1:3873] failed to handle socket
      java.net.SocketException: socket closed


        • 1. Re: JBoss deployment on XP loops
          iyerji2

          btw
          I am running jboss 4.2.0GA w/ jdk 1.5.0.12
          The new machine has a static ip and is not
          on the network.
          Turning the firewall on/off does not make a difference
          -thanks
          -Ganesh

          • 2. Re: JBoss deployment on XP loops

            I have been experiencing the same looping on socket exceptions with JBossAS 4.2.1.GA with Messaging 1.3. Recently an application running on 4.0.3 sp1 had the same issue. This inconsistent exception has shown up on XP and Server2003 with various JDKs.