This was due to a bug, fixed now. Please take a latest checkout of Sandesha2.
Chamikara
On 7/3/06, Mancinelli Elodie <[EMAIL PROTECTED]> wrote:
Sorry I forget the StackTrace:
java.lang.NullPointerException
org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor.setUpHighestMsgNumbers(TerminateSeqMsgProcessor.java:185)
org.apache.sandesha2.msgprocessors.TerminateSeqMsgProcessor.processInMessage (TerminateSeqMsgProcessor.java:128)
org.apache.sandesha2.handlers.SandeshaInHandler.invoke(SandeshaInHandler.java:87)
org.apache.axis2.engine.Phase.invoke(Phase.java:381)
org.apache.axis2.engine.AxisEngine.invoke (AxisEngine.java:473)
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:445)
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
org.apache.axis2.transport.http.AxisServlet.doPost (AxisServlet.java:136)
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)</pre>
This error appear in the response at the TerminateSequence.
Elodie
Mancinelli Elodie wrote:
> Hi Chamikara,
>
> Thanks you for your help.
>
> I change the 'InvokeInOrder' policy in the module.xml to 'false' in
> the sandesha2_1.0 mar.
> And now,I have an other error. I give you the catalina log:
>
> 3 juil. 2006 15:01:45 org.apache.catalina.core.StandardHostValve custom
> GRAVE: Exception Processing ErrorPage[errorCode=500,
> location=/axis2-web/Error/error500.jsp]
> org.apache.jasper.JasperException: "getOutputStream()" a déjà été
> appelé pour cette réponse
> at
> org.apache.jasper.servlet.JspServletWrapper.handleJspException (JspServletWrapper.java:510)
>
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
>
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:314)
> at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:252)
>
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke (ApplicationDispatcher.java:672)
>
> at
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:465)
>
> at
> org.apache.catalina.core.ApplicationDispatcher.doForward (ApplicationDispatcher.java:398)
>
> at
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>
> at
> org.apache.catalina.core.StandardHostValve.custom (StandardHostValve.java:363)
>
> at
> org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284)
>
> at
> org.apache.catalina.core.StandardHostValve.throwable (StandardHostValve.java:228)
>
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:134)
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>
> at
> org.apache.catalina.connector.CoyoteAdapter.service (CoyoteAdapter.java:148)
>
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>
> at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection (Http11BaseProtocol.java:667)
>
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:80)
>
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
>
> at java.lang.Thread.run(Thread.java:595)
>
> I search in the mailling list,and I don't find if there is a solution
> but I find a JIRA bug(http://issues.apache.org/jira/browse/AXIS2-707).
>
> Have you an idea?
>
> Elodie
>
>
>
>
> Chamikara Jayalath wrote:
>
>> Hi Elodie, Paul,
>>
>> It seems like MTOM + Sandesha2 + NotInOrder case is working.
>> But MTOM + Sadesha2 + InOrder case is not working.
>>
>> When InOrder Invocation is enabled Sandesha2 always pauses the
>> message before its actual invocation and Axis2 closes the InPutStream
>> when the message get paused and the thread get returned.
>>
>> Because of that the service Impl. get exceptions when tring to read
>> the MTOM attachments from the already closed stream. This seems to be
>> a general problem with message pausing.
>>
>> So Elodie, for now disable InOrder invocation in Sandesha2. To do
>> that change the 'InvokeInOrder' policy in the module.xml to 'false'
>> (this is 'true' by default).
>>
>> Chamikara
>>
>
