java.net.SocketException: Connection reset
In my production UCM (10.1.3.3) I have a clustered pair of UCM nodes. In the log files, I am seeing the below error messages???
From log file located in : u01/app/oracle/product/ucmstub2/etc/log…
system 03.15 20:02:50.114 IdcServerThread-54797 Network message format error. Unable to parse browser environment or content item. Connection reset (!csUnableToParseBrowserEnvironment!$Connection reset)-exception stack
intradoc.data.DataException: !csUnableToParseBrowserEnvironment!$Connection reset
at intradoc.server.IdcServerThread.run(IdcServerThread.java:189)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
at intradoc.serialize.DataBinderSerializer.readStreamLineByteEx(DataBinderSerializer.java:1587)
at intradoc.serialize.DataBinderSerializer.readLineRaw(DataBinderSerializer.java:1542)
at intradoc.serialize.DataBinderSerializer.readInputLine(DataBinderSerializer.java:1456)
at intradoc.serialize.DataBinderSerializer.readProperties(DataBinderSerializer.java:613)
at intradoc.serialize.DataBinderSerializer.prepareParseRequest(DataBinderSerializer.java:993)
at intradoc.data.DataSerializeUtils.prepareParseRequest(DataSerializeUtils.java:109)
at intradoc.server.ServiceManager.init(ServiceManager.java:123)
at intradoc.server.IdcServerThread.run(IdcServerThread.java:169)
system 03.15 20:02:50.115 IdcServerThread-54797 Broken pipe-exception stack
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:124)
at intradoc.server.ServiceManager.onError(ServiceManager.java:722)
at intradoc.server.IdcServerThread.run(IdcServerThread.java:218)
It looks like tihs one node is not even being used and is idle so why all of the broken pipe messages? Any suggestions or ideas?