We have developed an application that makes use of JBoss HA facilities by deploying the main application as an hasingleton app.
On one machine in our production environment we started seeing the following error messages two days ago:
2005-02-22 15:43:25,139 ERROR [org.jboss.ha.jndi.HANamingService] Error writing response
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1639)
at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1548)
at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1146)
at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1241)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1355)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281)
at org.jboss.ha.jndi.DetachedHANamingService.run(DetachedHANamingService.java:349)
at java.lang.Thread.run(Thread.java:534)
These happen at infrequent times (several hours apart) and occured several hours after JBoss successfully started.
Has anyone else had seen these errors, or can shed any light on why we might be seeing it on only one machine (not on the other two)?
Thanks and Regards,
Thad Smith
FYI. This turned out to be a hardware problem with our disk array.