Hi, Indeed, there is a general limit for serializing Strings - they may not become greater than 64K chars due to the fact that Sun only uses 2 bytes to store the length of a String in the serialized stream. This limit does not affect any other java object. Better than a vector you should use a StringBuffer (more efficient). We had the same problem here, and i could not believe, that you are allowed to create Strings with unlimited size, if noone is able to store them... Best Regards Jens Stutte -----Ursprüngliche Nachricht----- Von: cybermaster [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 7. März 2001 15:24 An: Orion-Interest Betreff: RE: com.evermind.server.rmi.RMIConnectionException: Object reference no longer valid (Disconnected) Eyal, I remember something about a limitation on the size of strings you can pass through RMI; if I recall correctly, sending a Vector will solve the problem. --peter -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Eyal Litman (Kamoon IL) Sent: Wednesday, March 07, 2001 2:27 AM To: Orion-Interest Subject: com.evermind.server.rmi.RMIConnectionException: Object reference no longer valid (Disconnected) Hi, I'm getting this exception when trying to sent a 72k string from my EJB(with orion) back to my client, using ORMI protocol (sun JDK 1.3, win 2000 and also on linux): com.evermind.server.rmi.RMIConnectionException: Object reference no longer valid (Disconnected) at com.evermind.server.rmi.a1.invoke(JAX) at __Proxy1.remove(Unknown Source) at kamoon.client.TestXmlTypesManager.main(TestXmlTypesManager.java:47) When i try to pass a smaller strings (i checked with 13k) it worked ok. 1. Does anybody had similar problems ? 2. What is wrong ? Eyal Litman Server Side Team, Kamoon Ltd.
