3 Replies Latest reply on Mar 10, 2008 10:24 AM by Brian Stansberry

    Strange error - accessing a jsp via load balancer (error occ

    siva ganesh Newbie

      I have 2 cluster nodes in "Mac 1" and "Mac 2" load balanced with mod_jk.

      If i try to access a particular jsp page thru the load balancer machine,
      it shows a blank page saying "Page cannot be displayed".

      This error is not consistent, and it works well sometimes and sometimes does not.

      I am able to access the jsp page when directly accessing "Mac 1" and "Mac 2", but not consistent when accessed thru the load balancer machine.

      Has anyone come across this type of error. Let me know if you are aware of this.

        • 1. Re: Strange error - accessing a jsp via load balancer (error
          siva ganesh Newbie

          Hi .. I am getting the following exception in the server log in cluster node, when the request is moved from apache machine.
          We are not sure if the request is actually moving from the apache machine to the cluster node.

          Exception on cluster node:
          at2007-07-25 10:35:15,250 INFO [org.apache.jk.common.JkInputStream] Receiving: getting request body chunk 0 0
          2007-07-25 10:35:15,252 INFO [org.apache.jk.common.JkInputStream] Receiving: getting request body chunk 0 0
          2007-07-25 10:35:15,253 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/ppm].[action]] Servlet.service() for servlet action threw exception
          javax.servlet.ServletException: MultipartIterator: no multipart request data sent
          at org.apache.struts.upload.MultipartIterator.parseRequest(MultipartIterator.java:341)
          at org.apache.struts.upload.MultipartIterator.(MultipartIterator.java:152)
          at org.apache.struts.upload.DiskMultipartRequestHandler.handleRequest(DiskMultipartRequestHandler.java:65)
          at org.apache.struts.util.RequestUtils.populate(RequestUtils.java:735)
          at org.apache.struts.action.ActionServlet.processPopulate(ActionServlet.java:2061)
          at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1563)
          at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:509)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
          at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
          at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
          at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
          at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
          at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
          at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
          at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
          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:199)
          at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
          at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
          at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
          at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
          at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
          at java.lang.Thread.run(Thread.java:595)


          Log Trace in the apache machine:
          [Tue Jul 24 17:24:38 2007] [11361:0005] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1043): 03f0 70 6C 61 79 3A 6E 6F 6E 65 22 3E 0A 3C 74 61 62 - play:none">.<tab

          [Tue Jul 24 17:24:38 2007] [11361:0005] [debug] ws_write::mod_jk.c (452): written 8184 out of 8184

          [Tue Jul 24 17:24:38 2007] [11361:0005] [info] ajp_process_callback::jk_ajp_common.c (1448): Writing to client aborted or client network problems

          [Tue Jul 24 17:24:38 2007] [11361:0005] [info] ajp_service::jk_ajp_common.c (1857): (diuapp03) request failed, because of client write error without recovery in send loop attempt=0

          [Tue Jul 24 17:24:38 2007] [11361:0005] [debug] ajp_done::jk_ajp_common.c (2257): will be shutting down socket 23 for worker diuapp03

          [Tue Jul 24 17:24:38 2007] [11361:0005] [debug] ajp_done::jk_ajp_common.c (2279): Shutting down held socket 23 in worker diuapp03

          [Tue Jul 24 17:24:38 2007] [11361:0005] [debug] ajp_done::jk_ajp_common.c (2286): recycling connection pool slot=0 for worker diuapp03

          [Tue Jul 24 17:24:38 2007] [11361:0005] [info] service::jk_lb_worker.c (1068): unrecoverable error 200, request failed. Client failed in the middle of request, we can't recover to another instance.

          [Tue Jul 24 17:24:38 2007] [11361:0005] [info] jk_handler::mod_jk.c (2247): Aborting connection for worker=jboss

          [Tue Jul 24 17:24:38 2007] [11362:0025] [debug] map_uri_to_worker::jk_uri_worker_map.c (589): Attempting to map URI '/alteon.html' from 4 maps

          [Tue Jul 24 17:24:38 2007] [11362:0025] [debug] map_uri_to_worker::jk_uri_worker_map.c (601): Attempting to map context URI '/jmx-console/*=jboss' source 'uriworkermap'





          [Tue Jul 24 17:32:22 2007] [11361:0017] [debug] ajp_connection_tcp_send_message::jk_ajp_common.c (896): sending to ajp13 pos=4 len=4 max=8192

          [Tue Jul 24 17:32:22 2007] [11361:0017] [debug] ajp_connection_tcp_send_message::jk_ajp_common.c (896): 0000 12 34 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - .4..............

          [Tue Jul 24 17:32:22 2007] [11361:0017] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1043): received from ajp13 pos=0 len=94 max=8192

          [Tue Jul 24 17:32:22 2007] [11361:0017] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1043): 0000 04 01 F4 00 15 49 6E 74 65 72 6E 61 6C 20 53 65 - .....Internal.Se

          [Tue Jul 24 17:32:22 2007] [11361:0017] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1043): 0010 72 76 65 72 20 45 72 72 6F 72 00 00 02 00 0C 43 - rver.Error.....C

          [Tue Jul 24 17:32:22 2007] [11361:0017] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1043): 0020 6F 6E 74 65 6E 74 2D 54 79 70 65 00 00 17 74 65 - ontent-Type...te

          [Tue Jul 24 17:32:22 2007] [11361:0017] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1043): 0030 78 74 2F 68 74 6D 6C 3B 63 68 61 72 73 65 74 3D - xt/html;charset=

          • 2. Re: Strange error - accessing a jsp via load balancer (error
            Amit Kumar Newbie

            I am also facing the same problem at loadbalancer machine, the error is inconsistent and comes when I refresh any page many a times quickly. The timeout for the application is though 5 minutes.

            Any clues?

            Regards

            • 3. Re: Strange error - accessing a jsp via load balancer (error
              Brian Stansberry Master

              Not really. You might have better luck posting on the JBossWeb user forums here (http://www.jboss.com/index.html?module=bb&op=viewforum&f=50) or even better, on the Tomcat user mailing list at apache.org. The mod_jk gurus are more likely to see your question there.