You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Tom Jordahl (JIRA)" <ax...@ws.apache.org> on 2005/06/14 16:54:47 UTC

[jira] Closed: (AXIS-2052) Slow Response time and CPU utilization shoots up.

     [ http://issues.apache.org/jira/browse/AXIS-2052?page=all ]
     
Tom Jordahl closed AXIS-2052:
-----------------------------

    Resolution: Duplicate

duplicate of 2051

> Slow Response time and CPU utilization shoots up.
> -------------------------------------------------
>
>          Key: AXIS-2052
>          URL: http://issues.apache.org/jira/browse/AXIS-2052
>      Project: Apache Axis
>         Type: Bug
>     Versions: 1.1
>  Environment: Sun Solaris, Tomcat 5.5.7, AXIS 1.1, XERCES (the one that comes with AXIS)
>     Reporter: Naveenkumar D
>     Priority: Blocker

>
> We are facing a problem and we are thinking that it is because of axis / tomcat.
>  
> Our AXIS 1.1 is integrated with tomcat (5.5.7). maxThreads value in server xml of tomcat is 400. Memory for JVM has been set to 2GB.
>  
> At one particular time (cant  simulate this..happens suddenly) the CPU utilization by this tomcat process shoots up to 30 % (normally its 5%) and  it never comes down unless we bounce the tomcat server.
>  
> When this happens we get very bad response times even though our web service application completes the request quickly. Once the control moves out of our application we dont know what happens !! (only AXIS serialization and sending response to client are two events)..
>  
> we ruled out network delay as other instances of tomcat in the same node are running fine.
> Is there any way to know why the response is delivered so late...Enabling AXIS logging is very costly for us...any other suggestions?
> Any help in this would be highly appreciable.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira