RSA Access Manger error message 'This stream has been closed'.
Originally Published: 2013-11-12
Article Number
Issue
The following error message is logged in the aserver.log (or lserver.log) file:
sequence_number=5311,2013-10-25 14:10:36:215 EDT,messageID=-2,internal_error,description='This stream has been closed.',details='java.io.IOException: This stream has been closed.'
The following exception is generated in the aserver.out standard output:
java.io.IOException: This stream has been closed.
at sirrus.util.io.FlushingByteArrayOutputStream.checkForStreamClosure(FlushingByteArrayOutputStream.java:162)
at sirrus.util.io.FlushingByteArrayOutputStream.write(FlushingByteArrayOutputStream.java:92)
at java.io.DataOutputStream.writeByte(DataOutputStream.java:136)
at sirrus.util.io.rpc.fope.ObjectNode.writeTypeToStream(ObjectNode.java:76)
at sirrus.util.io.rpc.fope.Node.writeToStream(Node.java:49)
at sirrus.util.io.rpc.fope.NodeFactory.convertNodeToStream(NodeFactory.java:78)
at sirrus.util.io.rpc.RPCManager.invokeLocalProcedure(RPCManager.java:179)
at sirrus.authserver.MuxRequestThreadPool$MuxWorkerTask.call(MuxRequestThreadPool.java:386)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Cause
cleartrust.aserver.muxworker.write.timeout = 10000
It indicates that the muxworker thread has abandoned the connection because it has been open too long, but the database still attempted to return a result.
Resolution
Investigate delays in the database response time.
Workaround
Notes
sequence_number=23519,remote_client=aserver1,2011-01-11 15:35:57:401 GMT,messageID=-2,internal_error,description='Unable to send data to receiver.',details='java.io.IOException: Unable to send data to receiver.'
The unable to send data to receiver message indicated the client had failed over. You will no longer see this message when the aserver is slow to respond.
Related Articles
The display names of the 'Contains Privilege Access' and 'Business Criticality' attributes fail to change after they have … Number of Views Unable to activate virtual host certificate; RSA Authentication Manager is unable to activate your selected certificate at… Number of Views RSA Identity Governance and Lifecycle fails to start after patching with error "Patching has failed" and "Closed Connection" Number of Views Error: '** FIND FIRST/LAST failed for table replace-token-buffer.(565)' when unassigning replacement token and 'this token… Number of Views RSA Authentication Manager 8.x import of replacement certificate fails with the error This certificate is already imported Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0.0 Administrators Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?
