AFX Server intermittently shuts down in RSA Identity Governance & Lifecycle
Originally Published: 2019-10-07
Article Number
Applies To
RSA Version/Condition: 7.1.0
Issue
The aveksaServer.log shows the following warnings and errors:
12/12/2018 04:00:00.015 WARN (ThreadPool-5) [com.aveksa.server.scheduler.SchedulerServiceProvider] ScheduledTask: Heartbeat_TASK could not be persisted
12/12/2018 04:04:29.887 WARN (EmailSenderServiceProvider) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 17002, SQLState: 08006
12/12/2018 04:04:29.887 ERROR (EmailSenderServiceProvider) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] IO Error: The Network Adapter could not establish the connection DSRA0010E: SQL State = 08006, Error Code = 17,002
12/12/2018 04:00:00.010 WARN (ThreadPool-5) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 17002, SQLState: 08006
12/12/2018 04:00:00.010 ERROR (ThreadPool-5) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] IO Error: The Network Adapter could not establish the connection DSRA0010E: SQL State = 08006, Error Code = 17,002
12/12/2018 04:00:00.010 ERROR (ThreadPool-5) [com.aveksa.server.node.HeartbeatServiceProvider] Unable to update Server Node status
com.aveksa.server.system.SystemServiceException: com.aveksa.server.db.PersistenceException: n/a
Please refer to RSA Knowledge Base Article 00000327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment.
The home/afxuser/AFX/esb/logs/esb.AFX-MAIN.log file shows the following errors:
2018-12-11 21:33:12.656 [WARN] com.aveksa.afx.server.component.ResponseTransformerComponent:159 - Unable to process primary response from ACM (http status 401):2018-12-11 21:33:12.656 [WARN] com.aveksa.afx.server.component.ResponseTransformerComponent:159 - Unable to process primary response from ACM (http status 401):Error 401: SRVE0295E: Error reported: 401
2018-12-11 21:34:13.080 [ERROR] org.mule.exception.DefaultMessagingExceptionStrategy:337 - ********************************************************************************Message : Failed to route event via endpoint: DefaultOutboundEndpoint{endpointUri=https://<server-name>:8444/aveksa/afx/settings-test, connector=HttpsConnector{ name=afxRequestHttpsConnector lifecycle=start this=11e9cd82 numberOfConcurrentTransactedReceivers=4 createMultipleTransactedReceivers=true connected=true supportedProtocols=[https] serviceOverrides= session.handler=org.mule.session.NullSessionHandler}, name='endpoint.https.<server-name>.8444.aveksa.afx.settings.test', mep=REQUEST_RESPONSE, properties={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: PostMethodCode : 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://<server-name>:8444/aveksa/afx/settings-test, connector=HttpsConnector{ name=afxRequestHttpsConnector lifecycle=start this=11e9cd82 numberOfConcurrentTransactedReceivers=4 createMultipleTransactedReceivers=true connected=true supportedProtocols=[https] serviceOverrides= session.handler=org.mule.session.NullSessionHandler}, name='endpoint.https.<server-name>.8444.aveksa.afx.settings.test', mep=REQUEST_RESPONSE, properties={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)********************************************************************************
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.1.0 P07
- RSA Identity Governance & Lifecycle 7.1.1 P01
- RSA Identity Governance & Lifecycle 7.2
Workaround
afx restart
Related Articles
RSA Identity Governance & Lifecycle 6.8.x and above remote Access Fulfilment Express (AFX) server fails to start with the … Number of Views How to shut down Authentication Manager 8.x primary, replicas and web tiers Number of Views Violation dialog in RSA Via Lifecycle & Governance shows the error "Request could not be handled" after importing an entit… Number of Views Remote AFX Server fails to start with an SSLHandshakeException error in RSA Identity Governance & Lifecycle Number of Views Form control type 'Drop Down Select with Web Service' displays Unauthorized error in RSA Identity Governance & Lifecycle 7… Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA-2026-10: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA SecurID Desktop Token 5.0.3 for Windows Administrator's Guide RSA SecurID Software Token 4.2.1 for Mac OS X Administrator's Guide
Don't see what you're looking for?
