]
Kevin Conner commented on JBESB-2946:
-------------------------------------
This is not an exception and can be safely ignored. It should result in the EPR being
removed from the SI cache and the invocation being retried with a subsequent EPR.
Integration with Riftsaw - ESB service orchestration raises
exception
---------------------------------------------------------------------
Key: JBESB-2946
URL:
https://jira.jboss.org/jira/browse/JBESB-2946
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.6
Environment: ESB 4.6
Riftsaw - from trunk
Reporter: Len DiMaggio
See example code here:
http://riftsaw.blogspot.com/2009/11/from-bpel-to-esb-and-back-introductio...
The integration successfully orchestrates the ESB service, but it raises this exception:
22:38:51,160 INFO [ServiceInvoker] Badly formed EPR [EPR:PortReference <>
<wsa:Address
http://localhost:8081/> >] for Service>
[FirstServiceESB:SimpleListener] and Message [header: [ ]].Courier for > EPR not
supported: ESB-unaware EPR used!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: