AnsweredAssumed Answered

AFX - INIT - Read Time Out

Question asked by Pradeep Kadambar Employee on Nov 3, 2017
Latest reply on Feb 28, 2018 by Ohad Demri

Environment : 7.0.1 / Web Sphere

 

I deployed the AFX archive and during startup the below error appears during INIT. I did not notice the usual SSL errors.Both the client.keystore and server.keystore have matching certificates.

 

I can also telnet the host name and port.

myacmhost:/home/afx/AFX/esb/logs # telnet myacmhost 8444 
Trying 10.4.37.240...
Connected to myacmhost.
Escape character is '^]'.
^CConnection closed by foreign host

The read from port 8444 fails

2017-11-03 18:09:48.153 [INFO] org.mule.lifecycle.AbstractLifecycleManager:193 - Starting connector: connector.https.mule.default 
2017-11-03 18:09:48.196 [INFO] org.mule.transport.service.DefaultTransportServiceDescriptor:193 - Loading default outbound transformer: org.mule.transport.http.transformers.ObjectToHttpClientMethodRequest
2017-11-03 18:09:48.204 [INFO] org.mule.transport.service.DefaultTransportServiceDescriptor:193 - Loading default response transformer: org.mule.transport.http.transformers.MuleMessageToHttpResponse
2017-11-03 18:09:48.246 [INFO] org.mule.transport.service.DefaultTransportServiceDescriptor:193 - Loading default outbound transformer: org.mule.transport.http.transformers.ObjectToHttpClientMethodRequest
2017-11-03 18:09:48.249 [INFO] org.mule.lifecycle.AbstractLifecycleManager:193 - Initialising: 'connector.https.mule.default.dispatcher.1846499313'. Object is: HttpsClientMessageDispatcher
2017-11-03 18:09:48.255 [INFO] org.mule.lifecycle.AbstractLifecycleManager:193 - Starting: 'connector.https.mule.default.dispatcher.1846499313'. Object is: HttpsClientMessageDispatcher
2017-11-03 18:10:48.643 [ERROR] com.aveksa.afx.server.init.SubmitInitializationRequestComponent:78 - Unable to connect to Aveksa Server using URL: https://myacmhost:8444/aveksa/afx/initialization
org.mule.api.transport.DispatchException: Failed to route event via endpoint: DefaultOutboundEndpoint{endpointUri=https://myacmhost:8444/aveksa/afx/initialization, connector=HttpsConnector
{
  name=connector.https.mule.default
  lifecycle=start
  this=17cdf104
  numberOfConcurrentTransactedReceivers=4
  createMultipleTransactedReceivers=true
  connected=true
  supportedProtocols=[https]
  serviceOverrides=<none>
}
,  name='endpoint.https.myacmhost.8444.aveksa.afx.initialization', mep=REQUEST_RESPONSE, properties={}, 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
        at org.mule.transport.http.HttpClientMessageDispatcher.execute(HttpClientMessageDispatcher.java:151)
        at org.mule.transport.http.HttpClientMessageDispatcher.doSend(HttpClientMessageDispatcher.java:279)
        at org.mule.transport.AbstractMessageDispatcher.process(AbstractMessageDispatcher.java:84)
        at org.mule.transport.AbstractConnector$DispatcherMessageProcessor.process(AbstractConnector.java:2637)
        at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24)
        at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58)
        at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44)
        at org.mule.processor.chain.SimpleMessageProcessorChain.doProcess(SimpleMessageProcessorChain.java:43)
        at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:67)
        at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24)
        at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44)
     
..........................................................................

Caused by: java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:164)
        at java.net.SocketInputStream.read(SocketInputStream.java:134)
        at com.ibm.jsse2.a.a(a.java:170)
        at com.ibm.jsse2.a.a(a.java:120)
        at com.ibm.jsse2.qc.a(qc.java:209)
        at com.ibm.jsse2.qc.a(qc.java:454)
        at com.ibm.jsse2.e.read(e.java:49)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:247)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:266)
        at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
        at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)
        at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1115)
        at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1373)
        at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1832)
        at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590)
        at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995)
        at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
        at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
        at org.mule.transport.http.HttpClientMessageDispatcher.execute(HttpClientMessageDispatcher.java:144)
        ... 117 more
2017-11-03 18:10:48.687 [ERROR] com.aveksa.afx.server.init.SubmitInitializationRequestComponent:79 -

        *** Full exception stacktrace will not be logged again if connection error is encountered during retry attempt(s).
        *** Please verify that your Aveksa Server is running and Host & Port in URL are correct.

2017-11-03 18:10:58.689 [INFO] com.aveksa.afx.server.init.SubmitInitializationRequestComponent:86 - Initialization request retry attempt #1

Outcomes