Many compression errors reported by java
 

Hi, Folks.

When I go to the gnutella net page, I see a lot of 'Unexpected end of ZLIB input stream' messages go past. I also get a series of errors in the phex.log file that are related to this. The java stack dump looks like this:

3:05:12 PM.0643: Global(Severe)! Exception occured: java.util.zip.DataFormatException: unknown compression method
at java.util.zip.Inflater.inflateBytes(Native Method)
at java.util.zip.Inflater.inflate(Inflater.java:219)
at java.util.zip.Inflater.inflate(Inflater.java:236)
at phex.utils.IOUtil.inflate(Unknown Source)
at phex.utils.IOUtil.inflate(Unknown Source)
at phex.msg.GGEPBlock$GGEPParser.parseGGEPBlock(Unkno wn Source)
at phex.msg.GGEPBlock$GGEPParser.parseGGEPBlocks(Unkn own Source)
at phex.msg.GGEPBlock.parseGGEPBlocks(Unknown Source)
at phex.msg.MsgQueryResponse.parseBody(Unknown Source)
at phex.msg.MsgQueryResponse.getMsgRecord(Unknown Source)
at phex.msg.MsgManager.snoopMonitorResult(Unknown Source)
at phex.msg.MsgManager.processQueryResponse(Unknown Source)
at phex.connection.ConnectionEngine.handleQueryRespon se(Unknown Source)
at phex.connection.ConnectionEngine.processIncomingDa ta(Unknown Source)
at phex.connection.OutgoingConnectionDispatcher.conne ctToNextCaughtHost(Unknown Source)
at phex.connection.OutgoingConnectionDispatcher.run(U nknown Source)
at phex.common.ThreadPool$Worker.run(Unknown Source)

It appears as if we are not supporting or are not correctly handling compressed connections, which have become very common in some of the gnutella clients. I know that gtk-gnutella supports this now, and certainly some others do too.

Could we put this on the list of requested enhancements, please? I would like to connect to these hosts who are using compression, and the default for gtk-gnutella (for example) is to only allow a single uncompressed connection, once compressed connections are enabled. Since I have no control over the other user's choices, and no way to request that they disable compression, or increase the number of uncompressed connections that they allow, the only way to solve this is to provide complete support for this newer feature.

Thanks,
--Rockkeys

I think you are mixing here two different problems.
First of all the network compression is something new in this BETA and still has a few problems. But in general it is working correctly.

The message 'Unexpected end of ZLIB input stream' you are seeing in the network panel is actually not a real error.
More or less its a Bug in the Java implementation returning this error instead of telling me that the other side has closed the communication stream. For a not compressed connection you would instead get the error 'Connection closed from remote host'.
There is not much we can do about this and I dont have the feeling this is cased by a compression problem on our side.

The Exception you posted 'java.util.zip.DataFormatException: unknown compression method' is something completely different and not relegated to above problem. This indicates that we have received a message on the network which indicated to be compressed but could not be decompressed. Therefore the message could not be understand and will be dropped.
Even though this is not nice there is nothing to worry about, dropped messages are not unusual and do not cause the communication with a host to get disrupted.

Gregor