Thanks Keith for quick response. couple of problems here.. First I could not figure out the link for nightly build, one visible on site is leading to axis2-C and is older one ..whereas I am on axis2-Java. Secondly I am getting this problem in production host(Windows server 2003) and not in my test setup as I haven't tried the load simulation. I can definitely try that on my test by simulating the load if I get the nightly build.
Another request is to know when this fix will be available in official release/patch so that I can push it to production. Thanks & Regards, Vishal Keithgchapman wrote: > > Can you test with the latest build please (nightly). I guess there was an > issue that got fixed in the trunk. > > Thanks, > Keith. > > On Fri, Nov 28, 2008 at 11:34 AM, vhgupta <[EMAIL PROTECTED]> wrote: > >> >> Hi All, >> >> We are using Apache 2.2 / tomcat/axis2 for web-service hosting. >> Apache 2.2 is used for load balancing for 3 instances of tomcat running >> on >> 3 >> different ports. >> Axis2 has load of around 1000 transactions per hour. >> >> >> ------------------------------------------------------------------------------ >> Earlier we were on Axis2.1.3 and everything was working fine for months, >> even with default Xmx of 64MB,. >> >> ------------------------------------------------------------------------------ >> >> When we moved to Axis2.1.4.1 we started getting "Heap Space Error" in few >> hours, >> Servlet.service() for servlet AxisServlet threw exception >> java.lang.OutOfMemoryError: Java heap space >> >> >> ------------------------------------------------------------------------------ >> I have tried the Xmx from 128MB to 256MB to 512 MB, only result was error >> getting delayed. >> >> ------------------------------------------------------------------------------ >> >> Please help urgently, Thanks in Advance. >> Regards, >> Vishal >> >> >> >> Tomcat Logs for additional info: >> 17-Nov-2008 17:20:56 org.apache.catalina.core.StandardWrapperValve invoke >> SEVERE: Servlet.service() for servlet AxisServlet threw exception >> java.lang.OutOfMemoryError: Java heap space >> 17-Nov-2008 17:21:33 org.apache.catalina.core.StandardWrapperValve invoke >> SEVERE: Servlet.service() for servlet AxisServlet threw exception >> java.lang.OutOfMemoryError: Java heap space >> 17-Nov-2008 17:21:33 org.apache.catalina.core.StandardWrapperValve invoke >> SEVERE: Servlet.service() for servlet AxisServlet threw exception >> java.lang.OutOfMemoryError: Java heap space >> 17-Nov-2008 17:21:36 org.apache.jk.core.MsgContext action >> WARNING: Error sending end packet >> java.net.SocketException: Software caused connection abort: socket write >> error >> at java.net.SocketOutputStream.socketWrite0(Native Method) >> at java.net.SocketOutputStream.socketWrite(Unknown Source) >> at java.net.SocketOutputStream.write(Unknown Source) >> at >> org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531) >> at >> org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121) >> at org.apache.jk.core.MsgContext.action(MsgContext.java:301) >> at org.apache.coyote.Response.action(Response.java:183) >> at org.apache.coyote.Response.finish(Response.java:305) >> at >> org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276) >> at >> org.apache.catalina.connector.Response.finishResponse(Response.java:486) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285) >> at >> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190) >> at >> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) >> at >> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) >> at >> >> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) >> at >> >> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) >> at >> >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686) >> at java.lang.Thread.run(Unknown Source) >> 17-Nov-2008 17:21:36 org.apache.catalina.core.StandardWrapperValve invoke >> SEVERE: Servlet.service() for servlet AxisServlet threw exception >> java.lang.OutOfMemoryError: Java heap space >> 17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher >> invoke >> SEVERE: Servlet.service() for servlet jsp threw exception >> java.lang.OutOfMemoryError: Java heap space >> 17-Nov-2008 17:23:31 org.apache.jk.common.ChannelSocket processConnection >> WARNING: processCallbacks status 2 >> 17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher >> invoke >> SEVERE: Servlet.service() for servlet jsp threw exception >> java.lang.OutOfMemoryError: Java heap space >> 17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher >> invoke >> SEVERE: Servlet.service() for servlet jsp threw exception >> java.lang.OutOfMemoryError: Java heap space >> 17-Nov-2008 17:23:31 org.apache.jk.core.MsgContext action >> WARNING: Error sending end packet >> java.net.SocketException: Software caused connection abort: socket write >> error >> at java.net.SocketOutputStream.socketWrite0(Native Method) >> at java.net.SocketOutputStream.socketWrite(Unknown Source) >> at java.net.SocketOutputStream.write(Unknown Source) >> at >> org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531) >> at >> org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121) >> at org.apache.jk.core.MsgContext.action(MsgContext.java:301) >> at org.apache.coyote.Response.action(Response.java:183) >> at org.apache.coyote.Response.finish(Response.java:305) >> at >> org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276) >> at >> org.apache.catalina.connector.Response.finishResponse(Response.java:486) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285) >> at >> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190) >> at >> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) >> at >> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) >> at >> >> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) >> at >> >> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) >> at >> >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686) >> at java.lang.Thread.run(Unknown Source) >> >> 17-Nov-2008 17:23:31 org.apache.jk.core.MsgContext action >> WARNING: Error sending end packet >> java.net.SocketException: Software caused connection abort: socket write >> error >> at java.net.SocketOutputStream.socketWrite0(Native Method) >> at java.net.SocketOutputStream.socketWrite(Unknown Source) >> at java.net.SocketOutputStream.write(Unknown Source) >> at >> org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531) >> at >> org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121) >> at org.apache.jk.core.MsgContext.action(MsgContext.java:301) >> at org.apache.coyote.Response.action(Response.java:183) >> at org.apache.coyote.Response.finish(Response.java:305) >> at >> org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276) >> at >> org.apache.catalina.connector.Response.finishResponse(Response.java:486) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285) >> at >> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190) >> at >> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) >> at >> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) >> at >> >> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) >> at >> >> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) >> at >> >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686) >> at java.lang.Thread.run(Unknown Source) >> 17-Nov-2008 17:23:34 org.apache.jk.common.ChannelSocket processConnection >> WARNING: processCallbacks status 2 >> 17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher >> invoke >> SEVERE: Servlet.service() for servlet jsp threw exception >> java.lang.IllegalStateException: getOutputStream() has already been >> called >> for this response >> at >> org.apache.catalina.connector.Response.getWriter(Response.java:604) >> at >> >> org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:198) >> at >> org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:125) >> at >> org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:118) >> at >> org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:186) >> at >> >> org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:118) >> at >> >> org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:77) >> at >> >> org.apache.jsp.axis2_002dweb.Error.error500_jsp._jspService(error500_jsp.java:110) >> at >> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) >> at >> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >> at >> >> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393) >> at >> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) >> at >> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266) >> at >> javax.servlet.http.HttpServlet.service(HttpServlet.java:803) >> 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.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) >> at >> >> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:447) >> at >> >> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379) >> at >> >> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292) >> at >> >> org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:424) >> at >> >> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:343) >> at >> >> org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:287) >> at >> >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) >> at >> >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) >> at >> >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) >> at >> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190) >> at >> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) >> at >> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) >> at >> >> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) >> at >> >> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) >> at >> >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686) >> at java.lang.Thread.run(Unknown Source) >> 17-Nov-2008 17:23:34 org.apache.jk.common.ChannelSocket processConnection >> WARNING: processCallbacks status 2 >> 17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher >> invoke >> SEVERE: Servlet.service() for servlet jsp threw exception >> java.lang.OutOfMemoryError: Java heap space >> 17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher >> invoke >> -- >> View this message in context: >> http://www.nabble.com/PLEASE-HELP%21%21%21-Any-known-issue-with-axis2.1.4.1-tomcat-6--Getting-heap-error-was-working-fine-with-axis2.1.3-tp20729407p20729407.html >> Sent from the Axis - Dev mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Keith Chapman > Senior Software Engineer > WSO2 Inc. > Oxygenating the Web Service Platform. > http://wso2.org/ > > blog: http://www.keith-chapman.org > > -- View this message in context: http://www.nabble.com/PLEASE-HELP%21%21%21-Any-known-issue-with-axis2.1.4.1-tomcat-6--Getting-heap-error-was-working-fine-with-axis2.1.3-tp20729407p20733541.html Sent from the Axis - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
