From: Anthony Green <green@redhat.com>
To: Christophe Roux <ch_roux@club-internet.fr>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: serialization problem with tomcat with gcj
Date: Sat, 08 Jun 2002 12:52:00 -0000 [thread overview]
Message-ID: <1023566001.2060.4.camel@dhcppc2> (raw)
In-Reply-To: <E17Glex-00087J-00@smarthost2.mail.easynet.fr>
Hi Christophe,
I suspect a bug in gcj's serialization implementation. Would it be
possible for you to try and reproduce the bug with a stand-alone program
which serializes/deserializes the same data? This might be easier to
debug. If you can reproduce this, then I suggest filing a bug with the
`gccbug' program.
Thanks,
AG
On Sat, 2002-06-08 at 12:15, Christophe Roux wrote:
> I try to port a java set of servlet from jdk1.2 / tomcat-2.3.2 to gcj
> (gcc-3.1) with tomcat-3.2.3 from rhug.
> I met a problem with object deserialization as transmitting data from a first
> servlet to a second one with a POST request.
> I build a scenario to reproduce my problem simply (tgz joined).
> I put flags in the second servlet to see where tomcat stops (I have no
> stack-trace and the servlet never hands back).
> The servlet stops on the instruction which create an ObjectInputStream from
> the servlet InputStream (before flag "POST2").
> I build gcc and rhug/jakarta-tomcat with UTF-8 encoding.
> But I build my program with ISO-8859-1 encoding for my program, as I use
> french accents in my strings.
> If you need anything more to investigate, or if you think I should contact
> someone in charge of gcj, tell me.
> Thanks a lot.
> Christophe Roux
next parent reply other threads:[~2002-06-08 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17Glex-00087J-00@smarthost2.mail.easynet.fr>
2002-06-08 12:52 ` Anthony Green [this message]
2002-06-08 19:43 ` Anthony Green
[not found] ` <E17H9G3-0006fn-00@smarthost2.mail.easynet.fr>
2002-06-10 1:25 ` Anthony Green
[not found] ` <E17JzAT-0000dx-00@smarthost1.mail.easynet.fr>
2002-06-17 11:11 ` Anthony Green
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=1023566001.2060.4.camel@dhcppc2 \
--to=green@redhat.com \
--cc=ch_roux@club-internet.fr \
--cc=rhug-rhats@sources.redhat.com \
/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: link
Be 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).