From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17508 invoked by alias); 14 Aug 2004 22:57:39 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 17493 invoked by uid 48); 14 Aug 2004 22:57:39 -0000 Date: Sat, 14 Aug 2004 22:57:00 -0000 From: "greenrd at greenrd dot org" To: java-prs@gcc.gnu.org Message-ID: <20040814225737.17035.greenrd@greenrd.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libgcj/17035] New: gnu.java.rmi should not reuse ObjectInputStreams and ObjectOutputStreams between RMI calls X-Bugzilla-Reason: CC X-SW-Source: 2004-q3/txt/msg00260.txt.bz2 List-Id: gnu.java.rmi tries to reuse ObjectOutputStreams between remote method invocations, which means that second and subsequent invocations in a connection don't start with the necessary Java serialization magic, 0xaced. This can be clearly seen in pcap.txt in the attached test case, which is a hexdump of packets captured by ethereal. The first invocation starts 50 ac ed 00 05 77 22 00 00 which is correct (note the magic "ac ed" indicating the start of a serialization stream). However, the second invocation is still using the same ObjectOutputStream, so it starts with: 50 77 22 00 00 which is _not_ correct, and hence the Sun VM complains. (However, because of a similar bug with incorrectly reusing the _input_ stream, gij is unable to decipher the error from the Sun VM and thinks the stream is corrupted.) -- Summary: gnu.java.rmi should not reuse ObjectInputStreams and ObjectOutputStreams between RMI calls Product: gcc Version: 3.4.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: greenrd at greenrd dot org CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17035