Exceptions in Wildfire 3.0.0 beta

wroot said it might be useful to just post all of them, so here goes…

This kind of seems like it shouldn’'t generate an exception:

2006.06.26 10:24:01 Finishing Outgoing Server Reader. Closing session: org.jivesoftware.wildfire.server.OutgoingServerSession@1b21f5c status: -1 address: amessage.info id: 886f459a5f687e1cce7894951cba465e29ce2c4d

java.net.SocketException: Socket closed

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(SocketInputStream.java:129)

at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)

at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)

at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)

at java.io.InputStreamReader.read(InputStreamReader.java:167)

at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)

at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)

at org.jivesoftware.wildfire.net.MXParser.nextImpl(MXParser.java:75)

at org.xmlpull.mxp1.MXParser.nextToken(MXParser.java:1100)

at org.dom4j.io.XMPPPacketReader.parseDocument(XMPPPacketReader.java:303)

at org.jivesoftware.wildfire.server.OutgoingServerSocketReader$1.run(OutgoingServe rSocketReader.java:91)

Hey Manuzhai,

Thanks for the input. That exception is not really an error but debug information that may be useful for admins. That exception means that the outgoing socket to a remote server was closed for some reason.

Hope that helps,

– Gato

It is for the most users really confusing, that debugging and warning messages are shown as exceptions with stacktrace.

If you print a normal line like “server amessage.info closed the connection for some reason” in the warn.log everybody know his is not a wildfire bug/exception.

The problem is, if the most exceptions with stacktrace are know as debug output, nobody will look into the logs anymore, because they’'re full of stacktraces.

So really important Exceptions get lost in the mass of stacktraces.