I do not think you will find what you are looking for. In the "old days" systems gave error codes, and then you had to look those codes up on a list to find out what they meant. This was, to the best of my knowledge, done simply because of memory constants. A 3 digit number or short 3 or 4 character
string was very small in comparison to a large string. It also had to do with the inner workings and design of the programming language itself.
Since an Exception in Java can contain a full description of the error as an error message, there is no need for such a reference chart. For example, the error you list:
StateTransfering::An existing connection was forcibly closed by the remote host (reading length) tells us everything we need to know. The remote host forcibly closed the connection. What more could a reference list tell me? Troubleshooting a possible cause is still necessary, but a reference list wouldn't help me there; good troubleshooting techniques and a Google search will. I would also check any reference documentation for the application I was using (which gave the error). I need to determine why my remote host forced the connection closed. The remote host didn't get the acknowledgement it expected? A timeout issue? A firewall? Dropped packets? Someone unplugged the network cable? Antivirus software detected a threat?
If you are locking for a list simply to know what possible errors might occur, even that would be a difficult issue. Since Java is multi-platform, the sockets errors that might occur on Linux are different then those that might occur on my cell phone, PDA or windows machine.
Lastly, since these type of errors will be JVM dependent, and different vendors can (and do) implement JVMs, the "list" would be different for each JVM. And then on top of that, an application developer would (or should) catch any Java SocketExceptionss, BondExceptions, ConnectExceptions, etc and then either handle them, or wrap them in a more meaningful error message (which is relevant to the code at hand and what it was doing) for the end user. This appears to be what is happening with the errors you posted.
You can take a look at all the Exceptions in the java.net package in the
api docs. That may help you some.
I hope that helps. I know it is not what you are looking for, but as I said, I don't think such a thing exists. If the gurus in the "Sockets and Internet Protocols" forum didn't know of one, then I would suspect such is the case.
[ March 05, 2005: Message edited by: Mark Vedder ]
