Re: java.io.EOFException in Jini Client: server is fine

If I may also add a voice to the other replies, suggesting that you perhaps look at a different protocol for transmitting such a large list of objects? If there are no data dependencies between processing individual objects (whatever "processing" means - I have no idea what is in these objects,

Re: java.io.EOFException in Jini Client: server is fine

One suggestion is to separate the messages from the payload and use a different protocol for the payload. For example, having the receiver reach back across the network when it is ready to read the payload. This has several advantages: - The receiver can impose flow control on the heavy

Re: java.io.EOFException in Jini Client: server is fine

The other detail to look at is the ObjectOutputStream cache. If a persistent/long-lived version of that class is used to write all the objects across the network, it can present a problem. That class caches objects and sends object ids for duplicates instead of the entire object, so that

Re: java.io.EOFException in Jini Client: server is fine

Those are tiny heaps for large objects. Bryan Bryan Thompson Chief Scientist & Founder SYSTAP, LLC 4501 Tower Road Greensboro, NC 27410 br...@systap.com http://blazegraph.com http://blog.bigdata.com http://mapgraph.io Blazegraph™ is our

java.io.EOFException in Jini Client: server is fine

Hi, I have a Jini server, and I am doing a lookup from a Jini registry and then making a call on the remote. The client code is: LookupLocator lookupLocator = new LookupLocator(jiniRegistryUrl); return (Remote) lookupLocator.getRegistrar().lookup(new ServiceTemplate(null,