2 Replies Latest reply on Jul 21, 2005 7:54 AM by Vishal Chaddha

    WARN  [org.jboss.jbossweb] WARNING: No thread for Socket

    Vishal Chaddha Newbie

      We have a setup with tomcat as web server and jboss as appserver. We are facing with problem of "low threads" at jboss end. All this is backed by pool of jboss and tomcat servers supported by loadbalancer.

      Going through jboss logs we get following messages -

      2005-06-09 08:36:28,379 WARN [org.jboss.jbossweb] WARNING: No thread for Socket[addr=/122.128.12.20,port=11204,localport=8081]
      2005-06-09 08:37:06,049 WARN [org.jboss.jbossweb] WARNING: No thread for Socket[addr=/122.128.12.21,port=37367,localport=8081]

      Consequently we are getting following message in tomcat logs. I believe its due to unavailabilty of jboss for taking more requests from tomcat.

      2005-06-09 09:01:19 CoyoteAdapter An exception or error occurred in the container during the request processing
      java.lang.NullPointerException
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164)
      at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
      at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
      at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
      at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
      at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:261)
      at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360)
      at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:604)
      at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:562)
      at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679)
      at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
      at java.lang.Thread.run(Thread.java:536)



      It would be great help if someone can provide us with details to get out of this problem. Is it due to some application erros or some problem with jboss/tomcat?