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 "Dong Liu (JIRA)" <ji...@apache.org> on 2006/04/12 05:31:19 UTC
[jira] Updated: (AXIS2-564) Addressing throwing
java.lang.NullPointerException when load is heavy
[ http://issues.apache.org/jira/browse/AXIS2-564?page=all ]
Dong Liu updated AXIS2-564:
---------------------------
Attachment: axis2.jmx
The number of threads that will trigger the scenario may depend on the machine and the servlet container.
> Addressing throwing java.lang.NullPointerException when load is heavy
> ---------------------------------------------------------------------
>
> Key: AXIS2-564
> URL: http://issues.apache.org/jira/browse/AXIS2-564
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core
> Versions: 0.95
> Environment: WinXP+SP2 java version "1.5.0_06" Jetty 5.1.10 Axis2 0.95
> Reporter: Dong Liu
> Attachments: axis2.jmx
>
> I use JMeter to generate the requests of the web service. The tested service is MyService with the release. Please see the JMeter test case file for details.
> When the load is relatively heavy, such warnings are thrown as the following
> 17:10:56.750 WARN!! [P1-31] org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:589) >11> /axis2/service
> s/MyService:
> java.lang.NullPointerException
> at org.apache.axis2.handlers.addressing.AddressingOutHandler.invoke (AddressingOutHandler.java:95)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:378)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:427)
> at org.apache.axis2.engine.AxisEngine.send (AxisEngine.java:527)
> at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:43)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java :408)
> at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:288)
> at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:160)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:616)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
> at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
> at org.mortbay.http.HttpContext.handle (HttpContext.java:1530)
> at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
> at org.mortbay.http.HttpServer.service (HttpServer.java:909)
> at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
> at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
> at org.mortbay.http.HttpConnection.handle (HttpConnection.java:833)
> at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
> at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
> at org.mortbay.util.ThreadPool$PoolThread.run (ThreadPool.java:534)
--
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