1 Reply Latest reply on Nov 9, 2003 6:08 AM by Jon Barnett

    JBoss 3.2.2 SocketTimeoutException using JK

    erikrj Newbie

      I have JBoss 3.2.2 installed and connected to Apache 2 via mod_jk2. I am recieving a SocketTimeoutException about every hour and a half or so. It is not fatal and does not seem to be causing any side effects other than annoying me and filling up my logs. I have this exact same setup using JBoss 3.2.1 wich uses Jetty and have no problems at all. Does anyone have any ideas? Is it a problem with Tomcat? The trace is below.

      Erik R. Jensen

      printStackTrace:

      12:39:28,274 ERROR [ChannelSocket] Error, processing connection
      java.net.SocketTimeoutException: read
      at java.net.AbstractSocketImpl$1.read(II)I(Unknown Source)
      at COM.jrockit.io.NativeIOInputStream.read([BII)I(Unknown Source)
      at java.io.BufferedInputStream.fill()V(BufferedInputStream.java:183)
      at java.io.BufferedInputStream.read1([BII)I(BufferedInputStream.java:222)
      at java.io.BufferedInputStream.read([BII)I(BufferedInputStream.java:277)
      at org.apache.jk.common.ChannelSocket.read(Lorg.apache.jk.core.MsgContext;[BII)I(ChannelSocket.java:498)
      at org.apache.jk.common.ChannelSocket.receive(Lorg.apache.jk.core.Msg;Lorg.apache.jk.core.MsgContext;)I(ChannelSocket.java:436)
      at org.apache.jk.common.ChannelSocket.processConnection(Lorg.apache.jk.core.MsgContext;)V(ChannelSocket.java:551)
      at org.apache.jk.common.SocketConnection.runIt([Ljava.lang.Object;)V(ChannelSocket.java:679)
      at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run()V(ThreadPool.java:619)
      at java.lang.Thread.run()V(Unknown Source)
      at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)

        • 1. Re: JBoss 3.2.2 SocketTimeoutException using JK
          Jon Barnett Master

          Have you got enough JK listeners/connectors for your load? Do you notice any content serving issues when this problem occurs? Are there a batch of requests that happen when the error occurs? Have you tried changing the connectionTimeout value to see the effect? And is there anything different between the two set ups - e.g. different OS? You could also try changing the enableLookups false to cut the DNS search delay, but this is more of a longshot.

          I'm not sure if there is much more to offer. You may want to check the Tomcat e-mail lists if you are still stuck and can't deduce anything more from these suggestions.