public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "greenrd at greenrd dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/17035] New: gnu.java.rmi should not reuse ObjectInputStreams and ObjectOutputStreams between RMI calls Date: Sat, 14 Aug 2004 22:57:00 -0000 [thread overview] Message-ID: <20040814225737.17035.greenrd@greenrd.org> (raw) 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
next reply other threads:[~2004-08-14 22:57 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-14 22:57 greenrd at greenrd dot org [this message] 2004-08-14 22:59 ` [Bug libgcj/17035] " pinskia at gcc dot gnu dot org 2004-08-14 22:59 ` greenrd at greenrd dot org 2004-08-17 21:07 ` greenrd at greenrd dot org 2004-08-17 23:00 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040814225737.17035.greenrd@greenrd.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).