You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Andrew Gatford (JIRA)" <ji...@apache.org> on 2006/06/22 12:52:30 UTC
[jira] Updated: (SANDESHA2-6) NullPointerException when generating
a SOAP 1.1 fault.
[ 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
> at org.apache.sandesha2.handlers.SandeshaInHandler.invoke(SandeshaInHandler.java:145)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:445)
> at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
> at org.apache.axis2.transport.http.HTTPWorker.processRequest(HTTPWorker.java:255)
> at org.apache.axis2.transport.http.server.SimpleConnectionThread.run(SimpleConnectionThread.java:92)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:797)
> Caused by: java.lang.NullPointerException
> at org.apache.sandesha2.util.SOAPFaultEnvelopeCreator.doSOAP11Encoding(SOAPFaultEnvelopeCreator.java:152)
> at org.apache.sandesha2.util.SOAPFaultEnvelopeCreator.addSOAPFaultEnvelope(SOAPFaultEnvelopeCreator.java:72)
> at org.apache.sandesha2.util.FaultManager.getFault(FaultManager.java:475)
> at org.apache.sandesha2.util.FaultManager.checkForUnknownSequence(FaultManager.java:267)
> at org.apache.sandesha2.msgprocessors.AcknowledgementProcessor.processInMessage(AcknowledgementProcessor.java:96)
> at org.apache.sandesha2.handlers.SandeshaInHandler.invoke(SandeshaInHandler.java:122)
> ... 9 more
> </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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: [jira] Updated: (SANDESHA2-6) NullPointerException when generating a SOAP 1.1 fault.
Posted by Chamikara Jayalath <ch...@gmail.com>.
Applied the patch
Thanks,
Chamikara
On 6/22/06, Andrew Gatford (JIRA) <ji...@apache.org> 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
> > at org.apache.sandesha2.handlers.SandeshaInHandler.invoke(
> SandeshaInHandler.java:145)
> > at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
> > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473)
> > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:445)
> > at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
> HTTPTransportUtils.java:284)
> > at org.apache.axis2.transport.http.HTTPWorker.processRequest(
> HTTPWorker.java:255)
> > at org.apache.axis2.transport.http.server.SimpleConnectionThread.run(
> SimpleConnectionThread.java:92)
> > at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:650)
> > at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:675)
> > at java.lang.Thread.run(Thread.java:797)
> > Caused by: java.lang.NullPointerException
> > at org.apache.sandesha2.util.SOAPFaultEnvelopeCreator.doSOAP11Encoding(
> SOAPFaultEnvelopeCreator.java:152)
> > at
> org.apache.sandesha2.util.SOAPFaultEnvelopeCreator.addSOAPFaultEnvelope(
> SOAPFaultEnvelopeCreator.java:72)
> > at org.apache.sandesha2.util.FaultManager.getFault(FaultManager.java
> :475)
> > at org.apache.sandesha2.util.FaultManager.checkForUnknownSequence(
> FaultManager.java:267)
> > at
> org.apache.sandesha2.msgprocessors.AcknowledgementProcessor.processInMessage
> (AcknowledgementProcessor.java:96)
> > at org.apache.sandesha2.handlers.SandeshaInHandler.invoke(
> SandeshaInHandler.java:122)
> > ... 9 more
> > </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: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>
Re: [jira] Updated: (SANDESHA2-6) NullPointerException when generating a SOAP 1.1 fault.
Posted by Chamikara Jayalath <ch...@gmail.com>.
Applied the patch
Thanks,
Chamikara
On 6/22/06, Andrew Gatford (JIRA) <ji...@apache.org> 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
> > at org.apache.sandesha2.handlers.SandeshaInHandler.invoke(
> SandeshaInHandler.java:145)
> > at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
> > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473)
> > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:445)
> > at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
> HTTPTransportUtils.java:284)
> > at org.apache.axis2.transport.http.HTTPWorker.processRequest(
> HTTPWorker.java:255)
> > at org.apache.axis2.transport.http.server.SimpleConnectionThread.run(
> SimpleConnectionThread.java:92)
> > at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:650)
> > at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:675)
> > at java.lang.Thread.run(Thread.java:797)
> > Caused by: java.lang.NullPointerException
> > at org.apache.sandesha2.util.SOAPFaultEnvelopeCreator.doSOAP11Encoding(
> SOAPFaultEnvelopeCreator.java:152)
> > at
> org.apache.sandesha2.util.SOAPFaultEnvelopeCreator.addSOAPFaultEnvelope(
> SOAPFaultEnvelopeCreator.java:72)
> > at org.apache.sandesha2.util.FaultManager.getFault(FaultManager.java
> :475)
> > at org.apache.sandesha2.util.FaultManager.checkForUnknownSequence(
> FaultManager.java:267)
> > at
> org.apache.sandesha2.msgprocessors.AcknowledgementProcessor.processInMessage
> (AcknowledgementProcessor.java:96)
> > at org.apache.sandesha2.handlers.SandeshaInHandler.invoke(
> SandeshaInHandler.java:122)
> > ... 9 more
> > </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: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>