Applied the patch

Thanks,
Chamikara

On 6/22/06, Andrew Gatford (JIRA) <[EMAIL PROTECTED]> wrote:
     [ http://issues.apache.org/jira/browse/SANDESHA2-6?page=all ]

Andrew Gatford updated SANDESHA2-6:
-----------------------------------

    Attachment: SOAPFaultPatch.patch

The fix appears to be to move the  faultReason.getSOAPFaultText("en") until after the null check in the doSOAP11Encoding method.  This means that there will always be a faultText object available to add the data to.  Also, when the object returned is null the factory creates a new FaultText object, but never sets it back into the SOAPFault.  This has been added.

> NullPointerException when generating a SOAP 1.1 fault.
> ------------------------------------------------------
>
>          Key: SANDESHA2-6
>          URL: http://issues.apache.org/jira/browse/SANDESHA2-6
>      Project: Apache Sandesha2
>         Type: Bug

>     Reporter: Andrew Gatford
>  Attachments: SOAPFaultPatch.patch
>
> When an ack is sent to a sequence which doesn't exist the following NullPointerException is generated.
> Enter: Sender::isFaultEnvelope, <soapenv:Fault xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/"><faultcode>soapenv:Client</faultcode><faultstring>Sandesha2 got an exception when processing the in message</faultstring><detail><Exception> org.apache.axis2.AxisFault: Sandesha2 got an exception when processing the in message; nested exception is:
> java.lang.NullPointerException&#13;
> at org.apache.sandesha2.handlers.SandeshaInHandler.invoke (SandeshaInHandler.java:145)&#13;
> at org.apache.axis2.engine.Phase.invoke(Phase.java:381)&#13;
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473)&#13;
> at org.apache.axis2.engine.AxisEngine.receive (AxisEngine.java:445)&#13;
> at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)&#13;
> at org.apache.axis2.transport.http.HTTPWorker.processRequest (HTTPWorker.java:255)&#13;
> at org.apache.axis2.transport.http.server.SimpleConnectionThread.run(SimpleConnectionThread.java:92)&#13;
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask (ThreadPoolExecutor.java:650)&#13;
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)&#13;
> at java.lang.Thread.run(Thread.java:797)&#13;
> Caused by: java.lang.NullPointerException&#13;
> at org.apache.sandesha2.util.SOAPFaultEnvelopeCreator.doSOAP11Encoding(SOAPFaultEnvelopeCreator.java:152)&#13;
> at org.apache.sandesha2.util.SOAPFaultEnvelopeCreator.addSOAPFaultEnvelope (SOAPFaultEnvelopeCreator.java:72)&#13;
> at org.apache.sandesha2.util.FaultManager.getFault(FaultManager.java:475)&#13;
> at org.apache.sandesha2.util.FaultManager.checkForUnknownSequence(FaultManager.java :267)&#13;
> at org.apache.sandesha2.msgprocessors.AcknowledgementProcessor.processInMessage(AcknowledgementProcessor.java:96)&#13;
> at org.apache.sandesha2.handlers.SandeshaInHandler.invoke(SandeshaInHandler.java :122)&#13;
> ... 9 more&#13;
> </Exception></detail></soapenv:Fault>
> The problem appears to be that the faultReason.getSOAPFaultText("en") in SOAPFaultEnvelopeCreator.doSOAP11Encoding returns null.  Later in this method there is a check for this being null, but not before it NullPointer's.

--
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to