|Applies To||RSA Product Set: SecurID|
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1
There was a problem processing your request.
A replication or backup task is in progress. Please wait for the current task to finish.
<Jul 20, <BEA-090166> <Failed to load identity keystore
<BEA-101083> <Connection failure. java.io.IOException: A complete message could not be read on socket: 'weblogic.socket.JSSEFilterImpl@1cc41d54 with delegate: weblogic.servlet.internal.MuxableSocketHTTP@1ccf04f6:Socket[addr=/172.21.155.70,port=42737,localport=7002] - idle timeout: '60000' ms, socket timeout: '25000' ms', in the configured timeout period of '60' secs
<BEA-101019> <[ServletContext@451376777[app:am-app module:/remoting path:null spec-version:3.0]] Servlet failed with an IOException java.net.SocketTimeoutException: Read timed out
2014-03-11: Unable to get configuration data for scope 0000-Global-0000 and section auth_manager.backup.scheduler.job%
Caused by: org.springframework.dao.DataAccessResourceFailure Exception: PreparedStatementCallback; SQL [SELECT NAME, VALUE FROM IMS_CONFIG_VALUE WHERE INSTANCE_ID=? AND NAME LIKE ?]; Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.; nested exception is org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
2014-05-16 [[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] GUILog.traceException(587) | exception: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://<Server>.<subdomain>.local:7082: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out; No available router to destination]
Attention! The following critical system event occurred: Your deployment is at risk. A backup has not been created successfully in the last 7 days. Log on to the Operations Console, and select "Backup and Restore > Back Up Now" or "Backup and Restore > Schedule Backups".
|Cause||It appears that a network problem broke the connection to the Windows File Share during a write operation of the scheduled backup. |
RSA Customer Support reproduced this symptom with RSA Authentication Manager 8.1 patch 2 (188.8.131.52.0) by disabling the Windows Server Network adapter during the write operation.
However with Authentication Manager 184.108.40.206.0, this problem self-healed when the Windows File Share problem was fixed (enabled NIC), while customer reported at Authentication Manager 220.127.116.11.0 with no patches that it never self-healed.
The fix in Authentication Manager 8.1 patch 2 is not documented because the customer reported the problem after the release of patch 2 while running Authentication Manager 8.1 base, then reported problem no longer occurred after patch 2 was applied
|Resolution||Apply Authentication Manager patch 2 (18.104.22.168.0) for Authentication Manager 8.1.0.|
|Legacy Article ID||a67320|