[ http://issues.apache.org/jira/browse/AXIS-2051?page=comments#action_12313591 ]
Tom Jordahl commented on AXIS-2051: ----------------------------------- You will have to try with at least Axis 1.2, but we would prefer you try to reproduce with the latest CVS source which will soon become 1.2.1. Many memory and performance issues have been resolved over the past few years. > Slow response and CPU Utilization increases of the java process increases. > --------------------------------------------------------------------------- > > Key: AXIS-2051 > URL: http://issues.apache.org/jira/browse/AXIS-2051 > Project: Apache Axis > Type: Bug > Components: Serialization/Deserialization > Versions: 1.1 > Environment: Sun solaris, Tomcat 5.5.7, 2 GB memory set for tomcat process > and maxThreadCount in tomcat is 400. > Reporter: Naveenkumar D > Priority: Blocker > > We are facing a problem and we are thinking that it is because of axis. > Our AXIS 1.1 is integrated with tomcat (5.5.7). We used to have max > concurrent threads of 100 for tomcat and now we have changed it to 400. > memory for JVM has been changed to 2GB from 1GB. > > Sometimes (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. > 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
