[switchyard-issues] [JBoss JIRA] (SWITCHYARD-674) Recursive handler activity when invoking a web service from a BPEL process using the wrong URL
Gary Brown (JIRA)
jira-events at lists.jboss.org
Wed Mar 7 10:48:38 EST 2012
Gary Brown created SWITCHYARD-674:
-------------------------------------
Summary: Recursive handler activity when invoking a web service from a BPEL process using the wrong URL
Key: SWITCHYARD-674
URL: https://issues.jboss.org/browse/SWITCHYARD-674
Project: SwitchYard
Issue Type: Bug
Reporter: Gary Brown
Attachments: loan-request.xml, switchyard-quickstart-bpel-service-loan-approval-WRONG-URL.jar, switchyard-quickstart-bpel-service-risk-assessment.jar
Using the latest 0.4-SNAPSHOT, I deployed two separate BPEL apps, one doing an external invoke of the other. When the URL to the external web service (i.e. BPEL process) is valid, there is no problem. However when the URL is deliberately set to an incorrect location (valid URL, just no web service at the endpoint), there is recursive behaviour establishing the handler chain.
This eventually results in no more file descriptors:
13:36:37,577 ERROR [org.switchyard.internal.DefaultHandlerChain] (pool-10-thread-318) org.switchyard.HandlerException was thrown by handler(provider): Unexpected exception handling SOAP Message --- Caused by javax.xml.soap.SOAPException: Cannot process SOAP request --- Caused by javax.xml.ws.WebServiceException: Could not send Message. --- Caused by java.net.SocketException: SocketException invoking http://127.0.0.1:18001/riskAssessorXXX: Too many open files --- Caused by java.net.SocketException: Too many open files
13:36:37,579 DEBUG [org.switchyard.internal.DefaultHandlerChain] (pool-10-thread-318) : org.switchyard.HandlerException: Unexpected exception handling SOAP Message
at org.switchyard.component.soap.OutboundHandler.handleMessage(OutboundHandler.java:153) [switchyard-component-soap-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT]
at org.switchyard.internal.DefaultHandlerChain.handleMessage(DefaultHandlerChain.java:148) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT]
at org.switchyard.internal.DefaultHandlerChain.handle(DefaultHandlerChain.java:121) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT]
at org.switchyard.internal.LocalDispatcher.dispatch(LocalExchangeBus.java:72) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT]
at org.switchyard.internal.ExchangeImpl.sendInternal(ExchangeImpl.java:255) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT]
at org.switchyard.internal.ExchangeImpl.send(ExchangeImpl.java:178) [switchyard-runtime-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT]
at org.switchyard.component.soap.InboundHandler.invoke(InboundHandler.java:218) [switchyard-component-soap-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT]
at org.switchyard.component.soap.BaseWebService.invoke(BaseWebService.java:69) [switchyard-component-soap-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT]
at org.switchyard.component.soap.BaseWebService.invoke(BaseWebService.java:34) [switchyard-component-soap-0.4.0-SNAPSHOT.jar:0.4.0-SNAPSHOT]
at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source) [:1.6.0_18]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the switchyard-issues
mailing list