You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alexey Ousov (JIRA)" <ji...@apache.org> on 2008/03/31 14:14:27 UTC
[jira] Created: (ODE-255) NPE when process received error response
from partner with empty
NPE when process received error response from partner with empty <details>
--------------------------------------------------------------------------
Key: ODE-255
URL: https://issues.apache.org/jira/browse/ODE-255
Project: ODE
Issue Type: Bug
Components: BPEL Runtime
Affects Versions: 1.2
Environment: Windows XP Pro, JDK 1.5.0.07, Oracle 10g XE, Apache Tomcat 5.5.25, OpenJPA
Reporter: Alexey Ousov
Fix For: 1.2
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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-255) NPE when process received error response
from partner with empty
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou resolved ODE-255.
-------------------------------
Resolution: Fixed
Assignee: Matthieu Riou
Fixed some time ago.
> NPE when process received error response from partner with empty <details>
> --------------------------------------------------------------------------
>
> Key: ODE-255
> URL: https://issues.apache.org/jira/browse/ODE-255
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: Windows XP Pro, JDK 1.5.0.07, Oracle 10g XE, Apache Tomcat 5.5.25, OpenJPA
> Reporter: Alexey Ousov
> Assignee: Matthieu Riou
> Fix For: 1.2
>
>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-255) NPE when process received error
response from partner with empty
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585147#action_12585147 ]
Matthieu Riou commented on ODE-255:
-----------------------------------
Could you update your build to use the 1.1 branch? I think this has been fixed on the branch.
> NPE when process received error response from partner with empty <details>
> --------------------------------------------------------------------------
>
> Key: ODE-255
> URL: https://issues.apache.org/jira/browse/ODE-255
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: Windows XP Pro, JDK 1.5.0.07, Oracle 10g XE, Apache Tomcat 5.5.25, OpenJPA
> Reporter: Alexey Ousov
> Fix For: 1.2
>
>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-255) NPE when process received error
response from partner with empty
Posted by "Alexey Ousov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586260#action_12586260 ]
Alexey Ousov commented on ODE-255:
----------------------------------
Yep, it was fixed on 1.1 branch
> NPE when process received error response from partner with empty <details>
> --------------------------------------------------------------------------
>
> Key: ODE-255
> URL: https://issues.apache.org/jira/browse/ODE-255
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: Windows XP Pro, JDK 1.5.0.07, Oracle 10g XE, Apache Tomcat 5.5.25, OpenJPA
> Reporter: Alexey Ousov
> Fix For: 1.2
>
>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.