Thanks a lot for your help, the problem is solved. There were new wrong libaries at the tomcat that caused the problem.
bastian ---- -------- Original-Nachricht -------- Datum: Mon, 04 Dec 2006 17:15:22 +0100 Von: Roland Weber <[EMAIL PROTECTED]> An: HttpClient User Discussion <[email protected]> Betreff: Re: deserialize bigger objects with ObjectInputstream on the client failed > Hello Bastian, > > the HTTP protocol has no known problems with larger files > (less than 2 GB), nor has HttpClient. Please try to narrow > down the problem to see whether it is on the transport layer > or above. > - check whether the server sends a Content-Encoding header > - generate a binary file on the server > - deserialize the file on the client to verify it's consistency > and the client environment (that's what you've done) > - let the client read the data from the server and, instead > of deserializing it, write it to a file > - compare the file downloaded by the client with the one > generated by the server > > We need more information to help you. The exception is of > no use at all, it only tells us that an object can't be > deserialized. It doesn't tell us where the problem comes > from, and it is in no way related to HttpClient. > > cheers, > Roland > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
