Petals BC SOAP

Operation not found in endpoint

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 4.1, 4.2.0, 4.3.0
  • Fix Version/s: 4.4.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The following error occurs when proxy-ing an external web-service:

    sample-0 2013/09/30 17:31:01,405 GMT+0200 SEVERE [Petals.Container.Components.petals-bc-soap] : Operation '{....}infoPersonne' not found in endpoint 'edpt-ad5d45e0-29d9-11e3-9003-0024e8ae9b85' description
javax.jbi.messaging.MessagingException: Operation '{....}infoPersonne' not found in endpoint 'edpt-ad5d45e0-29d9-11e3-9003-0024e8ae9b85' description
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:463)
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:344)
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:259)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:662)

    FYI: the operation mentioned in the log trace is a binding operation that is different from the expected operation declared in the port type.

    Show
    The following error occurs when proxy-ing an external web-service: 
    sample-0 2013/09/30 17:31:01,405 GMT+0200 SEVERE [Petals.Container.Components.petals-bc-soap] : Operation '{....}infoPersonne' not found in endpoint 'edpt-ad5d45e0-29d9-11e3-9003-0024e8ae9b85' description
javax.jbi.messaging.MessagingException: Operation '{....}infoPersonne' not found in endpoint 'edpt-ad5d45e0-29d9-11e3-9003-0024e8ae9b85' description
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.processAsProvider(MessageExchangeProcessor.java:463)
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.process(MessageExchangeProcessor.java:344)
	at org.ow2.petals.component.framework.process.MessageExchangeProcessor.run(MessageExchangeProcessor.java:259)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:662)
    FYI: the operation mentioned in the log trace is a binding operation that is different from the expected operation declared in the port type.
  • Environment:
    -

Issue Links

Depends
 

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
2m 18s
1
Christophe DENEUX
Mon, 30 Sep 2013 - 18:40:22 +0200
Open Open In Progress In Progress
4s
1
Christophe DENEUX
Mon, 30 Sep 2013 - 18:40:26 +0200
In Progress In Progress Resolved Resolved
14h 50m
1
Christophe DENEUX
Tue, 1 Oct 2013 - 09:31:12 +0200

People

Dates

  • Created:
    Mon, 30 Sep 2013 - 18:38:04 +0200
    Updated:
    Wed, 2 Oct 2013 - 13:43:45 +0200
    Resolved:
    Tue, 1 Oct 2013 - 09:31:11 +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.