2 Replies Latest reply on Jun 20, 2007 12:46 PM by maulik shah

    in access logs 500(Page can't displayed) comes sometimes for

    maulik shah Newbie

      Dear All,

      I had setup JBoss 4.0.3 AS in our development environment and also use the load balancing with sticky sessions enabled.
      Everything works fine, but what I observe in access.log is that it gives lots of 500 error for the resource that is already on AS. Immediatewly it gives 200 as return code in the logs, meaning it serve the request for the next client. It happens sometimes. I really don;t know what went wrong when it got 500 error.
      Is it something related to memory settings? But i also checked the status page, it give 75% of memory as free.
      Please let me know if someone faced the same problem and got success to overcome this.

      Thanks

        • 1. Re: in access logs 500(Page can't displayed) comes sometimes
          Elias Ross Master

          Is this performance related question? server.log should have information, if not you need to change your logging settings.

          • 2. Re: in access logs 500(Page can't displayed) comes sometimes
            maulik shah Newbie

            Thanks Genman,

            Here is the server.log :

            2007-06-18 06:58:24,083 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/].[Sta
            tus Servlet]] Servlet.service() for servlet Status Servlet threw exception
            javax.management.InstanceNotFoundException: jboss.web:name=JkRequest6676,type=RequestProcessor,worker=
            jk-xxxxx <port No.> is not registered.
            at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:508)
            at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:535)
            at org.apache.catalina.manager.StatusTransformer.writeProcessorState(StatusTransformer.java:370)
            at org.apache.catalina.manager.StatusTransformer.writeConnectorState(StatusTransformer.java:249)
            at org.jboss.web.tomcat.tc5.StatusServlet.doGet(StatusServlet.java:246)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            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:81)
            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.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
            at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
            at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
            at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
            at org.apache.catalina.valves.RequestFilterValve.process(RequestFilterValve.java:275)
            at org.apache.catalina.valves.RemoteAddrValve.invoke(RemoteAddrValve.java:80)
            at org.apache.catalina.valves.FastCommonAccessLogValve.invoke(FastCommonAccessLogValve.java:481)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
            at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.processHttp11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)

            Can you please explain why the above error occured?
            Also, want to let you know that without doing anything after a min. it was again working fine. Please note that no network issue at that time.

            The above log is for /status link.

            Thanks