000014908 - RSA Access Manger error message 'This stream has been closed'.

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000014908
IssueRSA Access Manger error message "This stream has been closed".
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)
CauseThis error occurs when the database does not return a result within the time specified in the parameter. 
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.
ResolutionIncrease the value of cleartrust.aserver.muxworker.write.timeout.   Recommmended value is 60000.
Investigate delays in the database response time. 
WorkaroundThis parameter was introduced in 6.2, 6.1.4 (SP4) and 6.0.4.63
NotesIn earlier versions of RSA Access Manager this error did not occur and after 15 seconds the aserver would respond with this message:
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.
Legacy Article IDa63025

Attachments

    Outcomes