Petals BC SOAP

NPE in the Petals console

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.0.3
  • Fix Version/s: 4.0.3
  • Component/s: None
  • Description:
    Hide

    petals@localhost:/> [Petals.Container.Components.petals-se-bpel]-INFO 2010-07-01 11:39:05,655 the receiver gives the message to workflow engine
    [Petals.Container.Components.petals-se-bpel]-SEVERE 2010-07-01 11:39:05,756 null
    java.lang.NullPointerException
    at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processInOptionalOutAsProvider(MessageExchangeProcessor.java:568)
    at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:391)
    at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:233)
    at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:177)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)

    Reproduction guidelines :

    • Start Petals in console mode (startup.sh -C)
    • Deploy & start the SE-BPEL
    • Deploy & start the BC-SOAP
    • Deploy the given configuration artifacts
    • Try to call the process using the given SoapUI 3.5 mock
    Show
    petals@localhost:/> [Petals.Container.Components.petals-se-bpel]-INFO 2010-07-01 11:39:05,655 the receiver gives the message to workflow engine [Petals.Container.Components.petals-se-bpel]-SEVERE 2010-07-01 11:39:05,756 null java.lang.NullPointerException at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processInOptionalOutAsProvider(MessageExchangeProcessor.java:568) at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:391) at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:233) at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:177) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Reproduction guidelines :
    • Start Petals in console mode (startup.sh -C)
    • Deploy & start the SE-BPEL
    • Deploy & start the BC-SOAP
    • Deploy the given configuration artifacts
    • Try to call the process using the given SoapUI 3.5 mock
  • Environment:
    Platform : Ubuntu 10.4, JDK 1.6u20
    Petals Version : Petals ESB 3.1
    Components :
    - Petals-SE-BPEL 1.0.4-SNAPSHOT (using snapshot versions of easyviper / easybpel)
    - Petals-BC-SOAP 4.0.3-SNAPSHOT

Attachments

  1. Zip Archive
    sa-BPEL-process-provide.zip
    (5 kB)
    Charles Casadei
    Tue, 3 Aug 2010 - 08:59:34 +0200
  2. Zip Archive
    sa-BPEL-process-provide.zip
    (5 kB)
    Charles Casadei
    Tue, 3 Aug 2010 - 08:59:34 +0200
  3. Zip Archive
    sa-SOAP-process-consume.zip
    (1 kB)
    Charles Casadei
    Tue, 3 Aug 2010 - 08:59:34 +0200
  4. Zip Archive
    sa-SOAP-process-consume.zip
    (1 kB)
    Charles Casadei
    Tue, 3 Aug 2010 - 08:59:34 +0200
  5. XML File
    Test-wsdl-soapui-project.xml
    (14 kB)
    Charles Casadei
    Tue, 3 Aug 2010 - 08:59:34 +0200
  6. XML File
    Test-wsdl-soapui-project.xml
    (14 kB)
    Charles Casadei
    Tue, 3 Aug 2010 - 08:59:34 +0200

Activity

Ascending order - Click to sort in descending order
Charles Casadei made changes - Tue, 3 Aug 2010 - 08:59:57 +0200
Field Original Value New Value
Project Support PROD - Veolia Eau [ 10057 ] Petals-BC-SOAP [ 10038 ]
Key SPVEOLIAE-30 PETALSBCSOAP-26
Issue Type Incident [ 6 ] Bug [ 1 ]
Workflow pl-support-workflow [ 10421 ] pl-bugtracker-workflow [ 10422 ]
Component/s PetalsESB [ 10027 ]
Security Public [ 10000 ]
Charles Casadei made changes - Tue, 3 Aug 2010 - 09:00:38 +0200
Summary NPE dans la console de Petals NPE in the Petals console
Charles Casadei made changes - Tue, 3 Aug 2010 - 09:01:08 +0200
Assignee Marc Jambert [ mjambert ] Nicolas Oddoux [ noddoux ]
Charles Casadei made changes - Tue, 3 Aug 2010 - 09:01:53 +0200
Description petals@localhost:/> [Petals.Container.Components.petals-se-bpel]-INFO 2010-07-01 11:39:05,655 the receiver gives the message to workflow engine
[Petals.Container.Components.petals-se-bpel]-SEVERE 2010-07-01 11:39:05,756 null
java.lang.NullPointerException
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processInOptionalOutAsProvider(MessageExchangeProcessor.java:568)
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:391)
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:233)
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:177)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619) 		petals@localhost:/> [Petals.Container.Components.petals-se-bpel]-INFO 2010-07-01 11:39:05,655 the receiver gives the message to workflow engine
[Petals.Container.Components.petals-se-bpel]-SEVERE 2010-07-01 11:39:05,756 null
java.lang.NullPointerException
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processInOptionalOutAsProvider(MessageExchangeProcessor.java:568)
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:391)
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:233)
at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:177)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

Reproduction guidelines :
- Start Petals in console mode (startup.sh -C)
- Deploy & start the SE-BPEL
- Deploy & start the BC-SOAP
- Deploy the given configuration artifacts
- Try to call the process using the given SoapUI 3.5 mock
Hide
Permalink
Charles Casadei added a comment - Tue, 3 Aug 2010 - 09:02:07 +0200

This is a known issue in the BC-SOAP in consume mode, which does not know how to guess MEPs for WSDL 1.1. May be a feature to be added in EasyWSDL.

Show
Charles Casadei added a comment - Tue, 3 Aug 2010 - 09:02:07 +0200 This is a known issue in the BC-SOAP in consume mode, which does not know how to guess MEPs for WSDL 1.1. May be a feature to be added in EasyWSDL.
Charles Casadei made changes - Tue, 3 Aug 2010 - 09:02:46 +0200
Link This issue blocks SPVEOLIAE-29 [ SPVEOLIAE-29 ]
Hide
Permalink
mjambert added a comment - Wed, 4 Aug 2010 - 10:18:43 +0200

Actually, there is already a method in EasyWSDL to guess the pattern of an operation in a WSDL1.1 : getPattern on AbsItfOperation.

Show
mjambert added a comment - Wed, 4 Aug 2010 - 10:18:43 +0200 Actually, there is already a method in EasyWSDL to guess the pattern of an operation in a WSDL1.1 : getPattern on AbsItfOperation.
Hide
Permalink
noddoux added a comment - Wed, 4 Aug 2010 - 17:41:18 +0200

Fixed on the branch petals-bc-soap-4.x.

Show
noddoux added a comment - Wed, 4 Aug 2010 - 17:41:18 +0200 Fixed on the branch petals-bc-soap-4.x.
Hide
Permalink
noddoux added a comment - Wed, 4 Aug 2010 - 18:38:25 +0200

not to merge on the trunk. cf PETALSBCSOAP-29.

Show
noddoux added a comment - Wed, 4 Aug 2010 - 18:38:25 +0200 not to merge on the trunk. cf PETALSBCSOAP-29.
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
1d 57m
1
noddoux
Wed, 4 Aug 2010 - 09:56:42 +0200
Open Open In Progress In Progress
19s
1
noddoux
Wed, 4 Aug 2010 - 09:57:01 +0200
In Progress In Progress Resolved Resolved
7h 44m
1
noddoux
Wed, 4 Aug 2010 - 17:41:18 +0200



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.