AnsweredAssumed Answered

SSH Connector is giving error after provisioning.

Question asked by Hemant Mandle on Jun 23, 2020
Latest reply on Jul 7, 2020 by Hemant Mandle

Hello -

Did anyone of you ever received below error from SSH connector after successful provisioning?

 

So, in my case, it is returning Exit Code "0" but then it is retuning below Error message continuously. This error is not allow change request item to move to "Pending Verification". It Is getting stuck in pending action. is there any configuration missing on AFX connector?

 

 

Message : Failed to route event via endpoint: DefaultOutboundEndpoint{endpointUri=https://<url>:<port>/aveksa/afx/fulfillment-state?state=C&date=1592931683122, connector=HttpsConnector { name=afxRequestHttpsConnector lifecycle=start this=5ee92158 numberOfConcurrentTransactedReceivers=4 createMultipleTransactedReceivers=true connected=true supportedProtocols=[https] serviceOverrides= session.handler=org.mule.session.NullSessionHandler } , name='<endpointurl>.int.<port>.aveksa.afx.fulfillment.state.state.C.date.1592931683122', mep=REQUEST_RESPONSE, properties={date=1592931683122, state=C, exceptionOnMessageError=true, http.method=POST, followRedirects=false}, transactionConfig=Transaction{factory=null, action=INDIFFERENT, timeout=0}, deleteUnacceptedMessages=false, initialState=started, responseTimeout=60000, endpointEncoding=UTF-8, disableTransportTransformer=false}. Message payload is of type: PostMethod Code : MULE_ERROR--2 -------------------------------------------------------------------------------- Exception stack is: 1. Read timed out (java.net.SocketTimeoutException) java.net.SocketInputStream:-2 (null) 2. Failed to route event via endpoint: DefaultOutboundEndpoint{endpointUri=https://<url>:<port>/aveksa/afx/fulfillment-state?state=C&date=1592931683122, connector=HttpsConnector { name=afxRequestHttpsConnector lifecycle=start this=5ee92158 numberOfConcurrentTransactedReceivers=4 createMultipleTransactedReceivers=true connected=true supportedProtocols=[https] serviceOverrides= session.handler=org.mule.session.NullSessionHandler } , name=’<endpoint_url’:<port>.aveksa.afx.fulfillment.state.state.C.date.1592931683122', mep=REQUEST_RESPONSE, properties={date=1592931683122, state=C, exceptionOnMessageError=true, http.method=POST, followRedirects=false}, transactionConfig=Transaction{factory=null, action=INDIFFERENT, timeout=0}, deleteUnacceptedMessages=false, initialState=started, responseTimeout=60000, endpointEncoding=UTF-8, disableTransportTransformer=false}. Message payload is of type: PostMethod (org.mule.api.transport.DispatchException) org.mule.transport.http.HttpClientMessageDispatcher:151 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/transport/DispatchException.html) -------------------------------------------------------------------------------- Root Exception stack trace: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:171) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)

Outcomes