3 Replies Latest reply on Mar 5, 2009 6:13 AM by jaikiran

    jboss tomcat issue ...?

    itlche

      Hi All,



      We have a test environment with 2 apaches and clustered 4 Jboss instances .



      We have setup load balancing via modjk properties in apache box.



      Our setup is like each apache is in separate box and 2 Jboss instances in separate box. [Totally 4 linux boxes]



      During the peak load of users, we get lot of errors in modjk logs like as shown

      
      
       [Tue Feb 17 10:33:27 2009][22106:1241577824] [error] ajp_send_request::jk_ajp_common.c (1359): (snode4) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=110)
      
      



      I felt this may be due to insufficient threads dedicated to tomcat container to process the requests from apache modjk to tomcat. But I am not sure whether this is correct or not.



      Please let me know if any one have encountered such errors ?



      Configuration details below:

      
      
      ModJK Properties: [Apache]
      
      
      
      
      
      
      
      worker.list=lb,slb,status
      
      
      
      worker.node1.port=8009
      
      worker.node1.host=lm014
      
      worker.node1.type=ajp13
      
      worker.node1.lbfactor=1
      
      worker.node1.connect_timeout=10000
      
      worker.node1.prepost_timeout=10000
      
      worker.node1.socket_timeout=10
      
      worker.node1.connection_pool_timeout=600
      
      # worker.node1.connection_pool_size=10 (1)
      
      worker.node1.domain=snode1
      
      
      
      worker.node2.reference=worker.node1
      
      worker.node2.host=lm014
      
      worker.node2.domain=snode2
      
      
      
      worker.node3.reference=worker.node1
      
      worker.node3.host=lm015
      
      worker.node3.domain=snode3
      
      
      
      worker.node4.reference=worker.node1
      
      worker.node4.host=lm015
      
      worker.node4.domain=snode4
      
      
      
      # Load-balancing behaviour
      
      worker.lb.type=lb
      
      worker.lb.balance_workers=node1,node2,node3,node4
      
      worker.lb.sticky_session=1
      
      # worker.lb.sticky_session_force=1
      
      
      
      
      
      worker.snode1.reference=worker.node1
      
      worker.snode1.host= lm014
      
      worker.snode1.port=8010
      
      
      
      worker.snode2.reference=worker.snode1
      
      worker.snode2.host= lm014
      
      
      
      worker.snode3.reference=worker.snode1
      
      worker.snode3.host=lm015
      
      
      
      worker.snode4.reference=worker.snode1
      
      worker.snode4.host= lm015
      
      
      
      # Load-balancing behaviour
      
      worker.slb.type=lb
      
      worker.slb.balance_workers=snode1,snode2,snode3,snode4
      
      worker.slb.sticky_session=1
      
      # worker.slb.sticky_session_force=1
      
      
      
      worker.status.type=status
      
      
      
      
      






      Server.xml [JBOSS Server]

      
       <Connector port="8080" address="${jboss.bind.address}"
      
       maxThreads="250" maxHttpHeaderSize="8192"
      
       emptySessionPath="true" protocol="HTTP/1.1"
      
       enableLookups="false" redirectPort="8443" acceptCount="100"
      
       connectionTimeout="20000" disableUploadTimeout="true" />
      
      
      
       <!-- Define an AJP 1.3 Connector on port 8009 -->
      
       <Connector port="8009" address="${jboss.bind.address}" protocol="AJP/1.3"
      
       emptySessionPath="true" enableLookups="false" redirectPort="443"
      
       scheme="http" secure="false" useIPVHosts="true" proxyPort="80" connectionTimeout="600000" />
      
      
      
       <!-- Define an AJP 1.3 Connector on port 8010 -->
      
       <Connector port="8010" address="${jboss.bind.address}" protocol="AJP/1.3"
      
       emptySessionPath="true" enableLookups="false" redirectPort="80"
      
       scheme="https" secure="true" useIPVHosts="true" proxyPort="443" connectionTimeout="600000" />
      


        • 1. Re: jboss tomcat issue ...?
          gmaheshwari

          Hi, I am facing an issue while running the project in Net Beans with Jboss server 4.0. The server log states that :

          ERROR [Tomcat5] Problem in init
          java.util.zip.ZipException: unexpected EOF

          The error is while deploying my application .war file from D:\program_files\jboss\server\default\deploy\Application.war

          Please help me out.

          Thanks in advance..

          • 2. Re: jboss tomcat issue ...?
            gmaheshwari

             

            "gmaheshwari" wrote:
            Hi, I am facing an issue while running the project in Net Beans with Jboss server 4.0. The server log states that :

            ERROR [Tomcat5] Problem in init
            java.util.zip.ZipException: unexpected EOF

            The error is while deploying my application .war file from D:\program_files\jboss\server\default\deploy\Application.war

            Please help me out.

            Thanks in advance..


            • 3. Re: jboss tomcat issue ...?
              jaikiran

              gmaheshwari,

              Your issue different from what the original poster has reported. Please open a new thread to discuss your issue.