AnsweredAssumed Answered

Read Time out While provisioning

Question asked by Ashish Kumar Dwivedi on Oct 25, 2017
Latest reply on Oct 25, 2017 by Ashish Kumar Dwivedi

What could be the reason of getting "read time out" error in AFX(restful connector) while provisioning ?

 

2017-10-25 13:51:32.998 [ERROR] org.mule.exception.DefaultMessagingExceptionStrategy:337 - 
******************************************************************************** 
Message : Failed to route event via endpoint: DefaultOutboundEndpoint{endpointUri=https://172.21.26.2:12443/rest/accounts/, connector=HttpsConnector 
{ 
name=RACF-Connector_restRef 
lifecycle=start 
this=75b25194 
numberOfConcurrentTransactedReceivers=4 
createMultipleTransactedReceivers=true 
connected=true 
supportedProtocols=[https] 
serviceOverrides=<none> 
} 
, name='endpoint.https.172.21.26.2.12443.rest.accounts', mep=REQUEST_RESPONSE, properties={exceptionOnMessageError=true}, transactionConfig=Transaction{factory=null, action=INDIFFERENT, timeout=0}, deleteUnacceptedMessages=false, initialState=started, responseTimeout=10000, endpointEncoding=UTF-8, disableTransportTransformer=false}. Message payload is of type: PutMethod 
Code : MULE_ERROR-42999 
-------------------------------------------------------------------------------- 
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://172.21.26.2:12443/rest/accounts/, connector=HttpsConnector 
{ 
name=RACF-Connector_restRef 
lifecycle=start 
this=75b25194 
numberOfConcurrentTransactedReceivers=4 
createMultipleTransactedReceivers=true 
connected=true 
supportedProtocols=[https] 
serviceOverrides=<none> 
} 
, name='endpoint.https.172.21.26.2.12443.rest.accounts', mep=REQUEST_RESPONSE, properties={exceptionOnMessageError=true}, transactionConfig=Transaction{factory=null, action=INDIFFERENT, timeout=0}, deleteUnacceptedMessages=false, initialState=started, responseTimeout=10000, endpointEncoding=UTF-8, disableTransportTransformer=false}. Message payload is of type: PutMethod (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:170) 
+ 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) 
******************************************************************************** 

 

2017-10-25 13:51:32.999 [INFO] org.mule.api.processor.LoggerMessageProcessor:193 - EXCEPTION redirect flow invoked... 
2017-10-25 13:51:33.006 [INFO] org.mule.api.processor.LoggerMessageProcessor:193 - AFX_OUT redirect flow invoked... 
2017-10-25 13:51:33.018 [WARN] org.mule.transport.jms.JmsMessageUtils:265 - Header: http.method is not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications. Please update your application code to correct this. Mule renamed it to http_method 
2017-10-25 13:51:33.019 [WARN] org.mule.transport.jms.JmsMessageUtils:265 - Header: Content-Type is not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications. Please update your application code to correct this. Mule renamed it to Content_Type 
2017-10-25 13:51:33.020 [INFO] org.mule.transport.service.DefaultTransportServiceDescriptor:193 - Loading default outbound transformer: org.mule.transport.jms.transformers.ObjectToJMSMessage 
2017-10-25 13:51:33.021 [INFO] org.mule.transport.service.DefaultTransportServiceDescriptor:193 - Loading default response transformer: org.mule.transport.jms.transformers.ObjectToJMSMessage 
2017-10-25 13:51:33.021 [WARN] com.mulesoft.mule.transport.jms.EeJmsMessageDispatcher:265 - Starting patched JmsMessageReceiver 
2017-10-25 13:51:33.021 [INFO] org.mule.lifecycle.AbstractLifecycleManager:193 - Initialising: 'jmsConnector.dispatcher.264465658'. Object is: EeJmsMessageDispatcher 
2017-10-25 13:51:33.022 [INFO] org.mule.lifecycle.AbstractLifecycleManager:193 - Starting: 'jmsConnector.dispatcher.264465658'. Object is: EeJmsMessageDispatcher 
2017-10-25 13:51:33.022 [WARN] org.mule.transport.jms.JmsMessageUtils:265 - Header: http.method is not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications. Please update your application code to correct this. Mule renamed it to http_method 
2017-10-25 13:51:33.023 [WARN] org.mule.transport.jms.JmsMessageUtils:265 - Header: Content-Type is not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications. Please update your application code to correct this. Mule renamed it to Content_Type

Outcomes