You are viewing a plain text version of this content. The canonical link for it is here.

Posted to savan-dev@ws.apache.org by "Ishwardeep Singh (JIRA)" <ji...@apache.org> on 2010/06/11 16:45:13 UTC

[jira] Created: (AXIS2-4736) Axis Servlet consumes 100% cpu

Axis Servlet consumes 100% cpu
------------------------------

                 Key: AXIS2-4736
                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
             Project: Axis2
          Issue Type: Bug
          Components: kernel
         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
            Reporter: Ishwardeep Singh


As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.

"TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
   java.lang.Thread.State: RUNNABLE
        at java.lang.String.substring(String.java:1939)
        at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
        at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
        at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
        at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
        at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
        at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
        at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
        at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
        at java.lang.Thread.run(Thread.java:619)



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "shivendra tripathi (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882575#action_12882575 ] 

shivendra tripathi commented on AXIS2-4736:
-------------------------------------------

Uncomment "org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger" in commons-logging.properties file. Set log4j.rootCategory= DEBUG, CONSOLE, LOGFILE in log4j.properties file.

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878225#action_12878225 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Thank you for your response. We are not able to figure out the request that is causing this issue. Can you please let us know how we can enabled logging in Axis 1.5 so that we can capture that request?

This is happening on our production server which is accessed by many clients. We are not sure this client is send a request.
Regards,
Ishwardeep


> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882503#action_12882503 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Can you please provide some input on how we can resolve this issue? We are not able to trace the request that causes this behaviour. How can we enable logs to debug the issue?
Regards,
Ishwardeep

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Sanka Samaranayake (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882541#action_12882541 ] 

Sanka Samaranayake commented on AXIS2-4736:
-------------------------------------------

Perhaps the following[1] mailing thread could help 

[1] http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200503.mbox/%3Cf43ea57905030206142de5bb7d@mail.gmail.com%3E

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878226#action_12878226 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Thank you for your response. We are not able to figure out the request that is causing this issue. Can you please let us know how we can enabled logging in Axis 1.5 so that we can capture that request?

This is happening on our production server which is accessed by many clients. We are not sure this client is send a request.
Regards,
Ishwardeep




      




> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "shivendra tripathi (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882575#action_12882575 ] 

shivendra tripathi commented on AXIS2-4736:
-------------------------------------------

Uncomment "org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger" in commons-logging.properties file. Set log4j.rootCategory= DEBUG, CONSOLE, LOGFILE in log4j.properties file.

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878225#action_12878225 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Thank you for your response. We are not able to figure out the request that is causing this issue. Can you please let us know how we can enabled logging in Axis 1.5 so that we can capture that request?

This is happening on our production server which is accessed by many clients. We are not sure this client is send a request.
Regards,
Ishwardeep


> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Sanka Samaranayake (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882541#action_12882541 ] 

Sanka Samaranayake commented on AXIS2-4736:
-------------------------------------------

Perhaps the following[1] mailing thread could help 

[1] http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200503.mbox/%3Cf43ea57905030206142de5bb7d@mail.gmail.com%3E

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877928#action_12877928 ] 

Andreas Veithen commented on AXIS2-4736:
----------------------------------------

This behavior is probably triggered by some malformed URLs. Can you provide a sample request that reproduces the issue?

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Updated: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ishwardeep Singh updated AXIS2-4736:
------------------------------------

    Attachment: thread_dump

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882503#action_12882503 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Can you please provide some input on how we can resolve this issue? We are not able to trace the request that causes this behaviour. How can we enable logs to debug the issue?
Regards,
Ishwardeep

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882503#action_12882503 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Can you please provide some input on how we can resolve this issue? We are not able to trace the request that causes this behaviour. How can we enable logs to debug the issue?
Regards,
Ishwardeep

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877928#action_12877928 ] 

Andreas Veithen commented on AXIS2-4736:
----------------------------------------

This behavior is probably triggered by some malformed URLs. Can you provide a sample request that reproduces the issue?

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882503#action_12882503 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Can you please provide some input on how we can resolve this issue? We are not able to trace the request that causes this behaviour. How can we enable logs to debug the issue?
Regards,
Ishwardeep

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Updated: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ishwardeep Singh updated AXIS2-4736:
------------------------------------

    Attachment: thread_dump

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Sanka Samaranayake (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882541#action_12882541 ] 

Sanka Samaranayake commented on AXIS2-4736:
-------------------------------------------

Perhaps the following[1] mailing thread could help 

[1] http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200503.mbox/%3Cf43ea57905030206142de5bb7d@mail.gmail.com%3E

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Sanka Samaranayake (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882541#action_12882541 ] 

Sanka Samaranayake commented on AXIS2-4736:
-------------------------------------------

Perhaps the following[1] mailing thread could help 

[1] http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200503.mbox/%3Cf43ea57905030206142de5bb7d@mail.gmail.com%3E

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882503#action_12882503 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Can you please provide some input on how we can resolve this issue? We are not able to trace the request that causes this behaviour. How can we enable logs to debug the issue?
Regards,
Ishwardeep

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878225#action_12878225 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Thank you for your response. We are not able to figure out the request that is causing this issue. Can you please let us know how we can enabled logging in Axis 1.5 so that we can capture that request?

This is happening on our production server which is accessed by many clients. We are not sure this client is send a request.
Regards,
Ishwardeep


> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Sanka Samaranayake (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882541#action_12882541 ] 

Sanka Samaranayake commented on AXIS2-4736:
-------------------------------------------

Perhaps the following[1] mailing thread could help 

[1] http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200503.mbox/%3Cf43ea57905030206142de5bb7d@mail.gmail.com%3E

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877928#action_12877928 ] 

Andreas Veithen commented on AXIS2-4736:
----------------------------------------

This behavior is probably triggered by some malformed URLs. Can you provide a sample request that reproduces the issue?

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "shivendra tripathi (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882575#action_12882575 ] 

shivendra tripathi commented on AXIS2-4736:
-------------------------------------------

Uncomment "org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger" in commons-logging.properties file. Set log4j.rootCategory= DEBUG, CONSOLE, LOGFILE in log4j.properties file.

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "shivendra tripathi (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882575#action_12882575 ] 

shivendra tripathi commented on AXIS2-4736:
-------------------------------------------

Uncomment "org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger" in commons-logging.properties file. Set log4j.rootCategory= DEBUG, CONSOLE, LOGFILE in log4j.properties file.

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Updated: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ishwardeep Singh updated AXIS2-4736:
------------------------------------

    Attachment: thread_dump

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878226#action_12878226 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Thank you for your response. We are not able to figure out the request that is causing this issue. Can you please let us know how we can enabled logging in Axis 1.5 so that we can capture that request?

This is happening on our production server which is accessed by many clients. We are not sure this client is send a request.
Regards,
Ishwardeep




      




> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878226#action_12878226 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Thank you for your response. We are not able to figure out the request that is causing this issue. Can you please let us know how we can enabled logging in Axis 1.5 so that we can capture that request?

This is happening on our production server which is accessed by many clients. We are not sure this client is send a request.
Regards,
Ishwardeep




      




> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878226#action_12878226 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Thank you for your response. We are not able to figure out the request that is causing this issue. Can you please let us know how we can enabled logging in Axis 1.5 so that we can capture that request?

This is happening on our production server which is accessed by many clients. We are not sure this client is send a request.
Regards,
Ishwardeep




      




> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "shivendra tripathi (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882575#action_12882575 ] 

shivendra tripathi commented on AXIS2-4736:
-------------------------------------------

Uncomment "org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger" in commons-logging.properties file. Set log4j.rootCategory= DEBUG, CONSOLE, LOGFILE in log4j.properties file.

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878225#action_12878225 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Thank you for your response. We are not able to figure out the request that is causing this issue. Can you please let us know how we can enabled logging in Axis 1.5 so that we can capture that request?

This is happening on our production server which is accessed by many clients. We are not sure this client is send a request.
Regards,
Ishwardeep


> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877928#action_12877928 ] 

Andreas Veithen commented on AXIS2-4736:
----------------------------------------

This behavior is probably triggered by some malformed URLs. Can you provide a sample request that reproduces the issue?

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Updated: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ishwardeep Singh updated AXIS2-4736:
------------------------------------

    Attachment: thread_dump

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877928#action_12877928 ] 

Andreas Veithen commented on AXIS2-4736:
----------------------------------------

This behavior is probably triggered by some malformed URLs. Can you provide a sample request that reproduces the issue?

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878225#action_12878225 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Thank you for your response. We are not able to figure out the request that is causing this issue. Can you please let us know how we can enabled logging in Axis 1.5 so that we can capture that request?

This is happening on our production server which is accessed by many clients. We are not sure this client is send a request.
Regards,
Ishwardeep


> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Commented: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878226#action_12878226 ] 

Ishwardeep Singh commented on AXIS2-4736:
-----------------------------------------

Dear Andreas,
Thank you for your response. We are not able to figure out the request that is causing this issue. Can you please let us know how we can enabled logging in Axis 1.5 so that we can capture that request?

This is happening on our production server which is accessed by many clients. We are not sure this client is send a request.
Regards,
Ishwardeep




      




> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

[jira] Updated: (AXIS2-4736) Axis Servlet consumes 100% cpu

Posted by "Ishwardeep Singh (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ishwardeep Singh updated AXIS2-4736:
------------------------------------

    Attachment: thread_dump

> Axis Servlet consumes 100% cpu
> ------------------------------
>
>                 Key: AXIS2-4736
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4736
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>         Environment: Redhat Linux 5.0, Tomcat 6.0, jdk 1.6.0.18
>            Reporter: Ishwardeep Singh
>         Attachments: thread_dump
>
>
> As soon as tomcat server is started and processes a couple of requests it starts to consume 100% cpu on the machine. Upon taking the thread dump it seems that it is stuck in the query parser. The thread dump for the same is attached.
> "TP-Processor51" daemon prio=10 tid=0x6f242800 nid=0x3764 runnable [0x6a041000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.String.substring(String.java:1939)
>         at org.apache.axis2.transport.http.util.QueryStringParser.getName(QueryStringParser.java:99)
>         at org.apache.axis2.transport.http.util.QueryStringParser.search(QueryStringParser.java:82)
>         at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:246)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
>         at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>         at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>         at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>         at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>         at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>         at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org