ODE
  1. ODE
  2. ODE-255

NPE when process received error response from partner with empty <details>

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.2
    • Fix Version/s: 1.2
    • Component/s: BPEL Runtime
    • Labels:
      None
    • Environment:
      Windows XP Pro, JDK 1.5.0.07, Oracle 10g XE, Apache Tomcat 5.5.25, OpenJPA

      Description

      When process recieved error response from external service with empty <detail> element, for example:
      <?xml version='1.0' encoding='utf-8'?>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">
      <soapenv:Header>
      <wsa:Action>http://www.w3.org/2005/08/addressing/soap/fault</wsa:Action>
      <wsa:RelatesTo>uuid:hqejbhcnphr35ptj6ib53m</wsa:RelatesTo>
      </soapenv:Header>
      <soapenv:Body>
      <soapenv:Fault>
      <faultcode>soapenv:Server</faultcode>
      <faultstring>org.xml.sax.SAXParseException: Content is not allowed in prolog.</faultstring>
      <detail />
      </soapenv:Fault>
      </soapenv:Body>
      </soapenv:Envelope>

      the following exception occur:
      java.lang.NullPointerException
      at org.apache.ode.axis2.util.SoapMessageConverter.inferFault(SoapMessageConverter.java:553)
      at org.apache.ode.axis2.util.SoapMessageConverter.parseSoapFault(SoapMessageConverter.java:529)
      at org.apache.ode.axis2.ExternalService.reply(ExternalService.java:278)
      at org.apache.ode.axis2.ExternalService.invoke(ExternalService.java:152)
      at org.apache.ode.axis2.MessageExchangeContextImpl.invokePartnerUnreliable(MessageExchangeContextImpl.java:67)
      at org.apache.ode.bpel.engine.PartnerLinkPartnerRoleImpl$UnreliableInvoker.run(PartnerLinkPartnerRoleImpl.java:339)
      at org.apache.ode.bpel.engine.BpelProcess$ProcessRunnable.run(BpelProcess.java:1123)
      at org.apache.ode.bpel.engine.BpelServerImpl$ServerRunnable.run(BpelServerImpl.java:793)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
      at java.util.concurrent.FutureTask.run(FutureTask.java:123)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
      at java.lang.Thread.run(Thread.java:595)

        Activity

        Hide
        Matthieu Riou added a comment -

        Could you update your build to use the 1.1 branch? I think this has been fixed on the branch.

        Show
        Matthieu Riou added a comment - Could you update your build to use the 1.1 branch? I think this has been fixed on the branch.
        Hide
        Alexey Ousov added a comment -

        Yep, it was fixed on 1.1 branch

        Show
        Alexey Ousov added a comment - Yep, it was fixed on 1.1 branch
        Hide
        Matthieu Riou added a comment -

        Fixed some time ago.

        Show
        Matthieu Riou added a comment - Fixed some time ago.

          People

          • Assignee:
            Matthieu Riou
            Reporter:
            Alexey Ousov
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development