Petals BC SOAP

NPE calling an external web-service under load

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.4.0
  • Fix Version/s: 4.4.1
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The following error occurs sometimes running load tests:

    container-node_0 2015/10/23 13:01:15,901 GMT+0000 MONIT [Petals.Container.Components.petals-bc-soap] : traceCode = 'provideFlowStepBegin', flowInstanceId = '250d5f02-7986-11e5-94ed-0242ac11000e', flowStepId = '250f5ad1-7986-11e5-a72e-0242ac110012', flowStepInterfaceName = '{http://petals.ow2.org/samples/se-bpmn/notifyVacationService}notifyVacation', flowStepServiceName = '{http://petals.ow2.org/samples/se-bpmn/notifyVacationService}notifyVacationService', flowStepOperationName = '{http://petals.ow2.org/samples/se-bpmn/notifyVacationService}newVacationRequest', flowStepEndpointName = 'edpt-23367c20-7986-11e5-a72e-0242ac110012', flowPreviousStepId = '250d5f03-7986-11e5-94ed-0242ac11000e'
container-node_0 2015/10/23 13:01:15,903 GMT+0000 WARNING [Petals.Container.Components.petals-bc-soap] : An error occured during message processing, let's send it back since the exchange was active before.
java.lang.NullPointerException
        at org.ow2.petals.binding.soap.listener.outgoing.SOAPCaller.call(SOAPCaller.java:110)
        at org.ow2.petals.binding.soap.listener.outgoing.JBIListener.onJBIMessage(JBIListener.java:59)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.invokeJBIListener(MessageExchangeProcessor.java:469)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:408)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:275)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:199)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
container-node_0 2015/10/23 13:01:15,934 GMT+0000 MONIT [Petals.Container.Components.petals-bc-soap] : traceCode = 'provideFlowStepFailure', flowInstanceId = '250d5f02-7986-11e5-94ed-0242ac11000e', flowStepId = '250f5ad1-7986-11e5-a72e-0242ac110012', failureMessage = 'A unknown error occurs (org.ow2.petals.binding.soap.listener.outgoing.SOAPCaller.call(SOAPCaller.java:110))'
    Show
    The following error occurs sometimes running load tests: 
    container-node_0 2015/10/23 13:01:15,901 GMT+0000 MONIT [Petals.Container.Components.petals-bc-soap] : traceCode = 'provideFlowStepBegin', flowInstanceId = '250d5f02-7986-11e5-94ed-0242ac11000e', flowStepId = '250f5ad1-7986-11e5-a72e-0242ac110012', flowStepInterfaceName = '{http://petals.ow2.org/samples/se-bpmn/notifyVacationService}notifyVacation', flowStepServiceName = '{http://petals.ow2.org/samples/se-bpmn/notifyVacationService}notifyVacationService', flowStepOperationName = '{http://petals.ow2.org/samples/se-bpmn/notifyVacationService}newVacationRequest', flowStepEndpointName = 'edpt-23367c20-7986-11e5-a72e-0242ac110012', flowPreviousStepId = '250d5f03-7986-11e5-94ed-0242ac11000e'
container-node_0 2015/10/23 13:01:15,903 GMT+0000 WARNING [Petals.Container.Components.petals-bc-soap] : An error occured during message processing, let's send it back since the exchange was active before.
java.lang.NullPointerException
        at org.ow2.petals.binding.soap.listener.outgoing.SOAPCaller.call(SOAPCaller.java:110)
        at org.ow2.petals.binding.soap.listener.outgoing.JBIListener.onJBIMessage(JBIListener.java:59)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.invokeJBIListener(MessageExchangeProcessor.java:469)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:408)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:275)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:199)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
container-node_0 2015/10/23 13:01:15,934 GMT+0000 MONIT [Petals.Container.Components.petals-bc-soap] : traceCode = 'provideFlowStepFailure', flowInstanceId = '250d5f02-7986-11e5-94ed-0242ac11000e', flowStepId = '250f5ad1-7986-11e5-a72e-0242ac110012', failureMessage = 'A unknown error occurs (org.ow2.petals.binding.soap.listener.outgoing.SOAPCaller.call(SOAPCaller.java:110))'
  • Environment:
    -

Issue Links

Depends

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Thu, 29 Oct 2015 - 16:49:43 +0100

This NPE should occur when processing incoming requests:

  • the SU provide has been just deployed, the endpoint has been just activated,
  • the SU provide is not completely started.
Show
Christophe DENEUX added a comment - Thu, 29 Oct 2015 - 16:49:43 +0100 This NPE should occur when processing incoming requests:
  • the SU provide has been just deployed, the endpoint has been just activated,
  • the SU provide is not completely started.
Hide
Permalink
Christophe DENEUX added a comment - Thu, 29 Oct 2015 - 17:04:42 +0100

With the current 4.4.1-SNAPSHOT version (svn#38660), I get the following stack trace that should be the same problem symptom:

container-node_1 2015/10/29 15:32:47,375 GMT+0000 WARNING [Petals.Container.Components.petals-bc-soap] : An error occured during message processing, let's send it back since the exchange was active before.
java.lang.NullPointerException
        at org.ow2.petals.binding.soap.listener.outgoing.SOAPCaller.call(SOAPCaller.java:120)
        at org.ow2.petals.binding.soap.listener.outgoing.JBIListener.onJBIMessage(JBIListener.java:59)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.invokeJBIListener(MessageExchangeProcessor.java:475)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:414)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:276)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:200)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Show
Christophe DENEUX added a comment - Thu, 29 Oct 2015 - 17:04:42 +0100 With the current 4.4.1-SNAPSHOT version (svn#38660), I get the following stack trace that should be the same problem symptom: 
container-node_1 2015/10/29 15:32:47,375 GMT+0000 WARNING [Petals.Container.Components.petals-bc-soap] : An error occured during message processing, let's send it back since the exchange was active before.
java.lang.NullPointerException
        at org.ow2.petals.binding.soap.listener.outgoing.SOAPCaller.call(SOAPCaller.java:120)
        at org.ow2.petals.binding.soap.listener.outgoing.JBIListener.onJBIMessage(JBIListener.java:59)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.invokeJBIListener(MessageExchangeProcessor.java:475)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:414)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:276)
        at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:200)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Hide
Permalink
Victor NOËL added a comment - Thu, 29 Oct 2015 - 17:52:35 +0100

This is caused by PETALSCDK-150.

Show
Victor NOËL added a comment - Thu, 29 Oct 2015 - 17:52:35 +0100 This is caused by PETALSCDK-150.
Hide
Permalink
Victor NOËL added a comment - Wed, 4 Nov 2015 - 13:37:48 +0100

A fix has been committed, could you test and tell me if it's ok?

Show
Victor NOËL added a comment - Wed, 4 Nov 2015 - 13:37:48 +0100 A fix has been committed, could you test and tell me if it's ok?
Hide
Permalink
Victor NOËL added a comment - Thu, 5 Nov 2015 - 09:02:23 +0100

It seems ok now.

Show
Victor NOËL added a comment - Thu, 5 Nov 2015 - 09:02:23 +0100 It seems ok now.

People

Dates

  • Created:
    Fri, 23 Oct 2015 - 15:59:32 +0200
    Updated:
    Thu, 5 Nov 2015 - 09:02:23 +0100
    Resolved:
    Thu, 5 Nov 2015 - 09:02:23 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.