Interesting Bug in Outgoing Rest Requests

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Interesting Bug in Outgoing Rest Requests

OpenESB Community Forum mailing list

Hi,

 

I have found what a appears to be an interesting bug in the RESTBC

 

When setting up an outgoing POST request, all is well if the CDATA section of the WSDL contains a URL like

 

http://localhost:8080/test

 

But. If the URL has a second component to the path (thus http://localhost:8080/test/fred) then explosion below takes place. This holds true even when all other defaults are accepted, and is therefore easily reproducible. The RESTBC is version 3.1.2.3

 

Regards,

Dave

 

2018-12-20T18:24:27.815+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.MessageProcessor] (pool-8-thread-1) RESTBC-7075: error when processing MessageExchange: id=76100765598552-15658-137646230677510155, com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused (Connection refused)

2018-12-20T18:24:27.826+0000 WARNING [com.sun.jbi.engine.bpel.BPELSEHelper] (sun-bpel-engine-thread-9) BPJBI-6001: Sending ERROR status (Service Name = {http://enterprise.netbeans.org/bpel/TestRESCTBC/testRESCTBC}InputRequest, Endpoint Name = RestInboundPortTypeRole_myRole, Operation Name = {http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/TestRESTBC}PostWithBody, Message Exchange Id = 76100765598552-15658-137646230675390154)

Error properties

  com.sun.jbi.crl.faultcode = Server

  com.sun.jbi.crl.faultstring = BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

  com.sun.jbi.crl.faultactor = sun-bpel-engine

  com.sun.jbi.crl.faultdetail =

   BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

   Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=ForwardPostRequest, portType={http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/ForwardPostRequest}RestOutboundPortType, operation=TestingPost)

BPCOR-6129: Line Number is 72

BPCOR-6130: Activity Name is Invoke1

   Caused by: java.net.ConnectException: Connection refused (Connection refused)

   Caused by: Connection refused (Connection refused)

2018-12-20T18:24:27.828+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.inbound.InboundDelegator] (Grizzly-9696(2)) RESTBC-7114: Error during inbound request java.lang.Exception: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

2018-12-20T18:24:27.828+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.inbound.JerseyRootResource] (Grizzly-9696(2)) RESTBC-7102: Error while serving inbound request java.lang.Exception: RESTBC-7114: Error during inbound request java.lang.Exception: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

2018-12-20T18:24:27.830+0000 WARNING [com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl] (sun-bpel-engine-thread-9) BPCOR-6151: The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>

com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=ForwardPostRequest, portType={http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/ForwardPostRequest}RestOutboundPortType, operation=TestingPost)

BPCOR-6129: Line Number is 72

BPCOR-6130: Activity Name is Invoke1

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:970)

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:567)

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:186)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:164)

                at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1091)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:274)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1332)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:384)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:241)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:193)

Caused by: com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused (Connection refused)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:128)

                at com.sun.jersey.api.client.Client.handle(Client.java:435)

                at com.sun.jbi.restbc.jbiadapter.JerseyClientWrapper.makeRequest(JerseyClientWrapper.java:678)

                at com.sun.jbi.restbc.jbiadapter.MessageProcessor.processOutboundInOut(MessageProcessor.java:114)

                at com.sun.jbi.restbc.jbiadapter.MessageProcessor.run(MessageProcessor.java:63)

                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

                at java.lang.Thread.run(Thread.java:748)

Caused by: java.net.ConnectException: Connection refused (Connection refused)

                at java.net.PlainSocketImpl.socketConnect(Native Method)

                at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

                at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)

                at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)

                at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

                at java.net.Socket.connect(Socket.java:589)

                at java.net.Socket.connect(Socket.java:538)

                at sun.net.NetworkClient.doConnect(NetworkClient.java:180)

                at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)

                at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)

                at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)

                at sun.net.www.http.HttpClient.New(HttpClient.java:339)

                at sun.net.www.http.HttpClient.New(HttpClient.java:357)

                at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)

                at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)

                at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)

                at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)

                at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1334)

                at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1309)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler$1$1.getOutputStream(URLConnectionClientHandler.java:200)

                at com.sun.jersey.api.client.CommittingOutputStream.commitWrite(CommittingOutputStream.java:114)

                at com.sun.jersey.api.client.CommittingOutputStream.write(CommittingOutputStream.java:86)

                at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)

                at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)

                at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)

                at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)

                at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)

                at java.io.BufferedWriter.flush(BufferedWriter.java:254)

                at com.sun.jersey.core.provider.AbstractMessageReaderWriterProvider.writeToAsString(AbstractMessageReaderWriterProvider.java:100)

                at com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:85)

                at com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:57)

                at com.sun.jersey.api.client.TerminatingClientHandler.writeRequestEntity(TerminatingClientHandler.java:317)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:179)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:126)

                ... 7 more

 

 

Reply | Threaded
Open this post in threaded view
|

CORRECTION: Re: Interesting Bug in Outgoing Rest Requests

OpenESB Community Forum mailing list

I apologise, the logging information should be as below. Interestingly, I note that the request is actually sent - perhaps this is due to the response handling of a POST? This service returns a json success message.

2018-12-21T09:57:27.685+0000 FINEST [com.sun.jbi.restbc.jbiadapter.RestSUManager] (VyoptaAlertIntegrationCA-sun-rest-binding)ClassName=com.sun.jbi.restbc.jbiadapter.RestSUManager;MethodName=init; RESTBC-1033: ServiceUnitManager.init() successful serviceUnitName=VyoptaAlertIntegrationCA-sun-rest-binding

2018-12-21T09:57:27.687+0000 INFO [com.sun.jbi.engine.bpel.BPELSEDeployer] (VyoptaAlertIntegrationCA-VyoptaAlertIntegration) BPJBI-5011: SU.start for VyoptaAlertIntegrationCA-VyoptaAlertIntegration is started

2018-12-21T09:57:27.688+0000 INFO [com.sun.jbi.engine.bpel.BPELSEDeployer] (VyoptaAlertIntegrationCA-VyoptaAlertIntegration) BPJBI-5012: SU.start for VyoptaAlertIntegrationCA-VyoptaAlertIntegration is completed

2018-12-21T09:57:27.698+0000 FINEST [com.sun.jbi.restbc.jbiadapter.RestSUManager] (VyoptaAlertIntegrationCA-sun-rest-binding)ClassName=com.sun.jbi.restbc.jbiadapter.RestSUManager;MethodName=start; RESTBC-1035: ServiceUnitManager.start() called serviceUnitName=VyoptaAlertIntegrationCA-sun-rest-binding

2018-12-21T09:57:27.698+0000 FINEST [com.sun.jbi.restbc.jbiadapter.ServiceUnit] (VyoptaAlertIntegrationCA-sun-rest-binding)ClassName=com.sun.jbi.restbc.jbiadapter.ServiceUnit;MethodName=start; RESTBC-1051: ServiceUnit.start() called serviceUnitName=VyoptaAlertIntegrationCA-sun-rest-binding

2018-12-21T09:57:27.698+0000 FINEST [com.sun.jbi.restbc.jbiadapter.wsdl.WSDLEndpoint] (VyoptaAlertIntegrationCA-sun-rest-binding)ClassName=com.sun.jbi.restbc.jbiadapter.wsdl.WSDLEndpoint;MethodName=start; RESTBC-1121: WSDLEndpoint.start()

2018-12-21T09:57:27.698+0000 INFO [com.sun.jbi.restbc.jbiadapter.wsdl.WSDLEndpoint] (VyoptaAlertIntegrationCA-sun-rest-binding) RESTBC-4121: activating endpoint for WSDLEndpoint: serviceName={http://j2ee.netbeans.org/wsdl/VyoptaAlertIntegration/src/SplunkSender}RestOutboundService, endpointName=RestOutboundWSDL_OutboundPort

2018-12-21T09:57:53.523+0000 FINEST [com.sun.jbi.restbc.jbiadapter.Receiver] (pool-9-thread-1)ClassName=com.sun.jbi.restbc.jbiadapter.Receiver;MethodName=run; RESTBC-1064: received a MessageExchange: id=191367726916614-26937-137646790735230011

2018-12-21T09:57:53.544+0000 FINEST [com.sun.jbi.restbc.jbiadapter.JerseyClientWrapper] (pool-8-thread-6)ClassName=com.sun.jbi.restbc.jbiadapter.JerseyClientWrapper;MethodName=makeRequest; Client Request:

  URI = http://localhost:8080/splunk/test

  Method = POST

  Headers = {Accept-Charset=[utf-8], Content-Type=[application/json], Accept=[application/json]}

 

2018-12-21T09:57:53.549+0000 FINEST [com.sun.jbi.restbc.jbiadapter.JerseyClientWrapper] (pool-8-thread-6)ClassName=com.sun.jbi.restbc.jbiadapter.JerseyClientWrapper;MethodName=makeRequest; Client Response:

  Status = OK

  Type = application/json

  Headers = {Matched-Stub-Id=[cc14b54f-eaed-4fcb-974a-7cc051b82c2f], Transfer-Encoding=[chunked], Content-Type=[application/json], Server=[Jetty(9.2.z-SNAPSHOT)]}

 

2018-12-21T09:57:53.549+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.MessageProcessor] (pool-8-thread-6) RESTBC-7075: error when processing MessageExchange: id=191367726916614-26937-137646790735230011, java.lang.NullPointerException

2018-12-21T09:57:53.550+0000 FINER [com.sun.jbi.restbc.com.sun.jbi.common.qos.messaging.MessagingChannel] (pool-8-thread-6)ClassName=com.sun.jbi.common.qos.messaging.BaseMessagingChannel;MethodName=removeTemplates; Removed template 191367726916614-26937-137646790735230011 from mTemplatesMap, now have: []

2018-12-21T09:57:53.558+0000 WARNING [com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl] (sun-bpel-engine-thread-6) BPCOR-6151: The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>null</jbi:part></jbi:message>

com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=PartnerLink1, portType={http://j2ee.netbeans.org/wsdl/VyoptaAlertIntegration/src/SplunkSender}RestOutboundPortType, operation=AlertSplunk)

BPCOR-6129: Line Number is 51

BPCOR-6130: Activity Name is Invoke2

at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:970)

at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:567)

at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:186)

at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:164)

at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)

at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1091)

at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:274)

at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1332)

at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:384)

at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:241)

at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:193)

Caused by: java.lang.NullPointerException

at com.sun.jbi.restbc.jbiadapter.JerseyClientWrapper.getOutputMessageNamespace(JerseyClientWrapper.java:729)

at com.sun.jbi.restbc.jbiadapter.JerseyClientWrapper.addNameSpaceToRawXML(JerseyClientWrapper.java:766)

at com.sun.jbi.restbc.jbiadapter.JerseyClientWrapper.buildNormalizedReplyMessage(JerseyClientWrapper.java:545)

at com.sun.jbi.restbc.jbiadapter.MessageProcessor.processOutboundInOut(MessageProcessor.java:117)

at com.sun.jbi.restbc.jbiadapter.MessageProcessor.run(MessageProcessor.java:63)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

 

On 20/12/2018 18:30, Dave Woodman via User wrote:

Hi,

 

I have found what a appears to be an interesting bug in the RESTBC

 

When setting up an outgoing POST request, all is well if the CDATA section of the WSDL contains a URL like

 

http://localhost:8080/test

 

But. If the URL has a second component to the path (thus http://localhost:8080/test/fred) then explosion below takes place. This holds true even when all other defaults are accepted, and is therefore easily reproducible. The RESTBC is version 3.1.2.3

 

Regards,

Dave

 

2018-12-20T18:24:27.815+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.MessageProcessor] (pool-8-thread-1) RESTBC-7075: error when processing MessageExchange: id=76100765598552-15658-137646230677510155, com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused (Connection refused)

2018-12-20T18:24:27.826+0000 WARNING [com.sun.jbi.engine.bpel.BPELSEHelper] (sun-bpel-engine-thread-9) BPJBI-6001: Sending ERROR status (Service Name = {http://enterprise.netbeans.org/bpel/TestRESCTBC/testRESCTBC}InputRequest, Endpoint Name = RestInboundPortTypeRole_myRole, Operation Name = {http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/TestRESTBC}PostWithBody, Message Exchange Id = 76100765598552-15658-137646230675390154)

Error properties

  com.sun.jbi.crl.faultcode = Server

  com.sun.jbi.crl.faultstring = BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

  com.sun.jbi.crl.faultactor = sun-bpel-engine

  com.sun.jbi.crl.faultdetail =

   BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

   Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=ForwardPostRequest, portType={http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/ForwardPostRequest}RestOutboundPortType, operation=TestingPost)

BPCOR-6129: Line Number is 72

BPCOR-6130: Activity Name is Invoke1

   Caused by: java.net.ConnectException: Connection refused (Connection refused)

   Caused by: Connection refused (Connection refused)

2018-12-20T18:24:27.828+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.inbound.InboundDelegator] (Grizzly-9696(2)) RESTBC-7114: Error during inbound request java.lang.Exception: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

2018-12-20T18:24:27.828+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.inbound.JerseyRootResource] (Grizzly-9696(2)) RESTBC-7102: Error while serving inbound request java.lang.Exception: RESTBC-7114: Error during inbound request java.lang.Exception: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

2018-12-20T18:24:27.830+0000 WARNING [com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl] (sun-bpel-engine-thread-9) BPCOR-6151: The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>

com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=ForwardPostRequest, portType={http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/ForwardPostRequest}RestOutboundPortType, operation=TestingPost)

BPCOR-6129: Line Number is 72

BPCOR-6130: Activity Name is Invoke1

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:970)

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:567)

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:186)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:164)

                at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1091)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:274)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1332)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:384)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:241)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:193)

Caused by: com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused (Connection refused)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:128)

                at com.sun.jersey.api.client.Client.handle(Client.java:435)

                at com.sun.jbi.restbc.jbiadapter.JerseyClientWrapper.makeRequest(JerseyClientWrapper.java:678)

                at com.sun.jbi.restbc.jbiadapter.MessageProcessor.processOutboundInOut(MessageProcessor.java:114)

                at com.sun.jbi.restbc.jbiadapter.MessageProcessor.run(MessageProcessor.java:63)

                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

                at java.lang.Thread.run(Thread.java:748)

Caused by: java.net.ConnectException: Connection refused (Connection refused)

                at java.net.PlainSocketImpl.socketConnect(Native Method)

                at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

                at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)

                at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)

                at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

                at java.net.Socket.connect(Socket.java:589)

                at java.net.Socket.connect(Socket.java:538)

                at sun.net.NetworkClient.doConnect(NetworkClient.java:180)

                at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)

                at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)

                at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)

                at sun.net.www.http.HttpClient.New(HttpClient.java:339)

                at sun.net.www.http.HttpClient.New(HttpClient.java:357)

                at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)

                at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)

                at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)

                at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)

                at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1334)

                at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1309)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler$1$1.getOutputStream(URLConnectionClientHandler.java:200)

                at com.sun.jersey.api.client.CommittingOutputStream.commitWrite(CommittingOutputStream.java:114)

                at com.sun.jersey.api.client.CommittingOutputStream.write(CommittingOutputStream.java:86)

                at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)

                at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)

                at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)

                at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)

                at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)

                at java.io.BufferedWriter.flush(BufferedWriter.java:254)

                at com.sun.jersey.core.provider.AbstractMessageReaderWriterProvider.writeToAsString(AbstractMessageReaderWriterProvider.java:100)

                at com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:85)

                at com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:57)

                at com.sun.jersey.api.client.TerminatingClientHandler.writeRequestEntity(TerminatingClientHandler.java:317)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:179)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:126)

                ... 7 more

 

 


Reply | Threaded
Open this post in threaded view
|

Re: Interesting Bug in Outgoing Rest Requests

Paul Perez
Administrator
In reply to this post by OpenESB Community Forum mailing list

Hello Dave,

 

First I would like to thank you for your feedback.

Before starting my answer I would like to inform you that the predicates used in the BPEL mapper are described in the BPEL documentation.

Regarding the bug in the REST BC, it is not a bug a misunderstanding about the way you defined the path of your applications.

When you create an endpoint with the path http://localhost:8080/test, the REST component searches if an existing path already exists in your composite application.

Let’s suppose that in this case that not paths matching http://localhost:8080/test.

Then you deploy another application with the path http://localhost:8080/test/fred the REST Component check the path and does not find a path matching it.

 

Next case:

You deploy http://localhost:8080/test/fred first and then http://localhost:8080/test. In that case unfortunately, the first path matches the second one and the component rejects the second deployment.

 

You must define your applications in that way:

The first must be http://localhost:8080/test/application01 and the second is http://localhost:8080/test/application02

It is a best practice in REST API definition

 

I put the two applications in attachments for your test.

Thank you for your feedback  

 

Best regards

 

Paul Perez Chief Architect

Pymma Consulting

--------------------------

Tel: +44 79 44 36 04 65

Skype ID : polperez

 

From: User <[hidden email]> On Behalf Of Dave Woodman via User
Sent: 20 December 2018 18:31
To: 'OpenESB user list' <[hidden email]>
Cc: Dave Woodman <[hidden email]>
Subject: [User] Interesting Bug in Outgoing Rest Requests

 

Hi,

 

I have found what a appears to be an interesting bug in the RESTBC

 

When setting up an outgoing POST request, all is well if the CDATA section of the WSDL contains a URL like

 

http://localhost:8080/test

 

But. If the URL has a second component to the path (thus http://localhost:8080/test/fred) then explosion below takes place. This holds true even when all other defaults are accepted, and is therefore easily reproducible. The RESTBC is version 3.1.2.3

 

Regards,

Dave

 

2018-12-20T18:24:27.815+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.MessageProcessor] (pool-8-thread-1) RESTBC-7075: error when processing MessageExchange: id=76100765598552-15658-137646230677510155, com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused (Connection refused)

2018-12-20T18:24:27.826+0000 WARNING [com.sun.jbi.engine.bpel.BPELSEHelper] (sun-bpel-engine-thread-9) BPJBI-6001: Sending ERROR status (Service Name = {http://enterprise.netbeans.org/bpel/TestRESCTBC/testRESCTBC}InputRequest, Endpoint Name = RestInboundPortTypeRole_myRole, Operation Name = {http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/TestRESTBC}PostWithBody, Message Exchange Id = 76100765598552-15658-137646230675390154)

Error properties

  com.sun.jbi.crl.faultcode = Server

  com.sun.jbi.crl.faultstring = BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

  com.sun.jbi.crl.faultactor = sun-bpel-engine

  com.sun.jbi.crl.faultdetail =

   BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

   Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=ForwardPostRequest, portType={http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/ForwardPostRequest}RestOutboundPortType, operation=TestingPost)

BPCOR-6129: Line Number is 72

BPCOR-6130: Activity Name is Invoke1

   Caused by: java.net.ConnectException: Connection refused (Connection refused)

   Caused by: Connection refused (Connection refused)

2018-12-20T18:24:27.828+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.inbound.InboundDelegator] (Grizzly-9696(2)) RESTBC-7114: Error during inbound request java.lang.Exception: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

2018-12-20T18:24:27.828+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.inbound.JerseyRootResource] (Grizzly-9696(2)) RESTBC-7102: Error while serving inbound request java.lang.Exception: RESTBC-7114: Error during inbound request java.lang.Exception: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

2018-12-20T18:24:27.830+0000 WARNING [com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl] (sun-bpel-engine-thread-9) BPCOR-6151: The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>

com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=ForwardPostRequest, portType={http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/ForwardPostRequest}RestOutboundPortType, operation=TestingPost)

BPCOR-6129: Line Number is 72

BPCOR-6130: Activity Name is Invoke1

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:970)

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:567)

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:186)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:164)

                at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1091)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:274)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1332)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:384)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:241)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:193)

Caused by: com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused (Connection refused)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:128)

                at com.sun.jersey.api.client.Client.handle(Client.java:435)

                at com.sun.jbi.restbc.jbiadapter.JerseyClientWrapper.makeRequest(JerseyClientWrapper.java:678)

                at com.sun.jbi.restbc.jbiadapter.MessageProcessor.processOutboundInOut(MessageProcessor.java:114)

                at com.sun.jbi.restbc.jbiadapter.MessageProcessor.run(MessageProcessor.java:63)

                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

                at java.lang.Thread.run(Thread.java:748)

Caused by: java.net.ConnectException: Connection refused (Connection refused)

                at java.net.PlainSocketImpl.socketConnect(Native Method)

                at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

                at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)

                at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)

                at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

                at java.net.Socket.connect(Socket.java:589)

                at java.net.Socket.connect(Socket.java:538)

                at sun.net.NetworkClient.doConnect(NetworkClient.java:180)

                at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)

                at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)

                at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)

                at sun.net.www.http.HttpClient.New(HttpClient.java:339)

                at sun.net.www.http.HttpClient.New(HttpClient.java:357)

                at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)

                at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)

                at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)

                at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)

                at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1334)

                at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1309)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler$1$1.getOutputStream(URLConnectionClientHandler.java:200)

                at com.sun.jersey.api.client.CommittingOutputStream.commitWrite(CommittingOutputStream.java:114)

                at com.sun.jersey.api.client.CommittingOutputStream.write(CommittingOutputStream.java:86)

                at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)

                at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)

                at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)

                at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)

                at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)

                at java.io.BufferedWriter.flush(BufferedWriter.java:254)

                at com.sun.jersey.core.provider.AbstractMessageReaderWriterProvider.writeToAsString(AbstractMessageReaderWriterProvider.java:100)

                at com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:85)

                at com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:57)

                at com.sun.jersey.api.client.TerminatingClientHandler.writeRequestEntity(TerminatingClientHandler.java:317)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:179)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:126)

                ... 7 more

 

 


test-OpenESB.zip (118K) Download Attachment
www.pymma.com The best services on OpenESB
Reply | Threaded
Open this post in threaded view
|

Re: Interesting Bug in Outgoing Rest Requests - NOT A BUG IN OpenESB

OpenESB Community Forum mailing list
In reply to this post by OpenESB Community Forum mailing list

This is a bug, but not in OpenESB - this is due to an invalid response being returned by the invoked service (the json response was not correct).

Correcting response from the up-stream server will resolve this.


Dave.


On 20/12/2018 18:30, Dave Woodman via User wrote:

Hi,

 

I have found what a appears to be an interesting bug in the RESTBC

 

When setting up an outgoing POST request, all is well if the CDATA section of the WSDL contains a URL like

 

http://localhost:8080/test

 

But. If the URL has a second component to the path (thus http://localhost:8080/test/fred) then explosion below takes place. This holds true even when all other defaults are accepted, and is therefore easily reproducible. The RESTBC is version 3.1.2.3

 

Regards,

Dave

 

2018-12-20T18:24:27.815+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.MessageProcessor] (pool-8-thread-1) RESTBC-7075: error when processing MessageExchange: id=76100765598552-15658-137646230677510155, com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused (Connection refused)

2018-12-20T18:24:27.826+0000 WARNING [com.sun.jbi.engine.bpel.BPELSEHelper] (sun-bpel-engine-thread-9) BPJBI-6001: Sending ERROR status (Service Name = {http://enterprise.netbeans.org/bpel/TestRESCTBC/testRESCTBC}InputRequest, Endpoint Name = RestInboundPortTypeRole_myRole, Operation Name = {http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/TestRESTBC}PostWithBody, Message Exchange Id = 76100765598552-15658-137646230675390154)

Error properties

  com.sun.jbi.crl.faultcode = Server

  com.sun.jbi.crl.faultstring = BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

  com.sun.jbi.crl.faultactor = sun-bpel-engine

  com.sun.jbi.crl.faultdetail =

   BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

   Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=ForwardPostRequest, portType={http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/ForwardPostRequest}RestOutboundPortType, operation=TestingPost)

BPCOR-6129: Line Number is 72

BPCOR-6130: Activity Name is Invoke1

   Caused by: java.net.ConnectException: Connection refused (Connection refused)

   Caused by: Connection refused (Connection refused)

2018-12-20T18:24:27.828+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.inbound.InboundDelegator] (Grizzly-9696(2)) RESTBC-7114: Error during inbound request java.lang.Exception: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

2018-12-20T18:24:27.828+0000 SEVERE [com.sun.jbi.restbc.jbiadapter.inbound.JerseyRootResource] (Grizzly-9696(2)) RESTBC-7102: Error while serving inbound request java.lang.Exception: RESTBC-7114: Error during inbound request java.lang.Exception: BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance

2018-12-20T18:24:27.830+0000 WARNING [com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl] (sun-bpel-engine-thread-9) BPCOR-6151: The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>java.net.ConnectException: Connection refused (Connection refused)</jbi:part></jbi:message>

com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=ForwardPostRequest, portType={http://j2ee.netbeans.org/wsdl/TestRESCTBC/src/ForwardPostRequest}RestOutboundPortType, operation=TestingPost)

BPCOR-6129: Line Number is 72

BPCOR-6130: Activity Name is Invoke1

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:970)

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:567)

                at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:186)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:164)

                at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1091)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:274)

                at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1332)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:384)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:241)

                at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:193)

Caused by: com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused (Connection refused)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:128)

                at com.sun.jersey.api.client.Client.handle(Client.java:435)

                at com.sun.jbi.restbc.jbiadapter.JerseyClientWrapper.makeRequest(JerseyClientWrapper.java:678)

                at com.sun.jbi.restbc.jbiadapter.MessageProcessor.processOutboundInOut(MessageProcessor.java:114)

                at com.sun.jbi.restbc.jbiadapter.MessageProcessor.run(MessageProcessor.java:63)

                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

                at java.lang.Thread.run(Thread.java:748)

Caused by: java.net.ConnectException: Connection refused (Connection refused)

                at java.net.PlainSocketImpl.socketConnect(Native Method)

                at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

                at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)

                at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)

                at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

                at java.net.Socket.connect(Socket.java:589)

                at java.net.Socket.connect(Socket.java:538)

                at sun.net.NetworkClient.doConnect(NetworkClient.java:180)

                at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)

                at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)

                at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)

                at sun.net.www.http.HttpClient.New(HttpClient.java:339)

                at sun.net.www.http.HttpClient.New(HttpClient.java:357)

                at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)

                at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)

                at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)

                at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)

                at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1334)

                at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1309)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler$1$1.getOutputStream(URLConnectionClientHandler.java:200)

                at com.sun.jersey.api.client.CommittingOutputStream.commitWrite(CommittingOutputStream.java:114)

                at com.sun.jersey.api.client.CommittingOutputStream.write(CommittingOutputStream.java:86)

                at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)

                at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)

                at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)

                at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)

                at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)

                at java.io.BufferedWriter.flush(BufferedWriter.java:254)

                at com.sun.jersey.core.provider.AbstractMessageReaderWriterProvider.writeToAsString(AbstractMessageReaderWriterProvider.java:100)

                at com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:85)

                at com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:57)

                at com.sun.jersey.api.client.TerminatingClientHandler.writeRequestEntity(TerminatingClientHandler.java:317)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:179)

                at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:126)

                ... 7 more