RE: [JBoss-user] Urgent - NamingService - Error writing response
Thanks Scott. Any color on why we're getting the messages every minute? We have no idea which client might be causing this, any way to tell? Eric -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Tuesday, November 18, 2003 5:33 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Urgent - NamingService - Error writing response The client trying to lookup the naming stub on the bootstrap port is not reading the socket stream. -- Scott Stark Chief Technology Officer JBoss Group, LLC Eric J Kaplan wrote: Hi We have been running on jboss 3.0.4 for a while. Last night, just after midnight, for the first time, we started getting these messages about every minute: 2003-11-18 08:36:33,015 ERROR [org.jboss.naming.NamingService] 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(ObjectOutputStrea m.java:1637) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Object OutputStream.java:1546) at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:114 6) at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1 239) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1 353) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281) at org.jnp.server.Main.run(Main.java:285) at java.lang.Thread.run(Thread.java:536) The server actually seems to be functioning ok. What might these messages mean? It's strange it just started at midnight. When we reboot the server, we still get those messages. Urgent. Please help. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Urgent - NamingService - Error writing response
Use netstat to see who is connecting to 1099. -- Scott Stark Chief Technology Officer JBoss Group, LLC Eric J Kaplan wrote: Thanks Scott. Any color on why we're getting the messages every minute? We have no idea which client might be causing this, any way to tell? Eric --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Urgent - NamingService - Error writing response
The client trying to lookup the naming stub on the bootstrap port is not reading the socket stream. -- Scott Stark Chief Technology Officer JBoss Group, LLC Eric J Kaplan wrote: Hi We have been running on jboss 3.0.4 for a while. Last night, just after midnight, for the first time, we started getting these messages about every minute: 2003-11-18 08:36:33,015 ERROR [org.jboss.naming.NamingService] 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:1637) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1546) at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1146) at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1239) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1353) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281) at org.jnp.server.Main.run(Main.java:285) at java.lang.Thread.run(Thread.java:536) The server actually seems to be functioning ok. What might these messages mean? Its strange it just started at midnight. When we reboot the server, we still get those messages. Urgent. Please help. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
