-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
Martin:
There was a bug in the IBM JVM that caused socket closes. They refreshed the
JVM on their site on August 19th. Can you do a 'java -fullversion' so that
you can compare it to the refresh on the IBM site:
http://alphaworks.ibm.com/tech/linuxjvm
I found that the refresh corrected the socket closure problems we saw, but it
may have a memory leak.
-MA
Martin Rode wrote:
> -----------------------------
> Please read the FAQ!
> <http://java.apache.org/faq/>
> -----------------------------
>
> Hi everybody!
>
> I'm experiencing a problem with JDK 1.1.6 from IBM, Apache
> 1.3.6 and Jserv 1.0b3.
>
> This is what's in jserv-trace.log:
>
> [14/09/1999 21:36:50:367 CEST] Content-Type: text/html
> [14/09/1999 21:36:50:368 CEST] Connection from localhost/127.0.0.1
> [14/09/1999 21:36:50:369 CEST] Initializing servlet request
> [14/09/1999 21:36:50:369 CEST] Reading request data
> [14/09/1999 21:36:50:385 CEST] Malformed request data: Malformed request:
> java.io.IOException: Malformed Request: reading line length
> [14/09/1999 21:36:50:385 CEST] Sending response headers.
> [14/09/1999 21:36:50:385 CEST] Status: 400 Bad Request
> [14/09/1999 21:36:50:385 CEST] Servlet-Error: Malformed data send to JServ
>
> The weird thing about the "Bad Request" is, that it sometimes works and
> it sometimes does not (just hit reload a couple of times :-). Most of
> the time it works fine with Linux/Netscape 4.6 JDK JIT enabled!, but I
> got quite a few "Bad Request" with Linux/Netscape 4.6 JDK JIT disabled.
> Even worse is by the way IE or Netscape either latest on a MacG3.
>
> I'have just switched my Servlet-Setup from a glibc2.0.7 based Suse6.0 with
> JDK Blackdown 1.2preAlpha-2 with GreenThreads No JIT (the only one which
> works for now) to glibc2.1 based Redhat6.0 with JDK IDM Linux 1.1.6 (which
> feels quite a little bit faster). With the Blackdown JDK on glibc2.0.7 I
> have never experienced any "Bad Requests" so far.
>
> So, I'm basically wondering if I have a JDK only problem here or if there
> might be a glitch with Jserv interacting with the IBM JDK.
>
>
> Here's what I found where the error msg comes from...
>
>
> JServConnection.java:
> =====================
>
> /**
> * Read a line from the input.
> */
> private String readHexLine() throws IOException {
> byte str[];
>
> try {
> // Read four bytes from the input stream
> byte hex[] = new byte[4];
> if (in.read(hex) != 4) {
> // Fail read..
> ------>>>> throw new IOException("Malformed Request: reading
> line length");
> }
>
>
> ======================
>
> Martin Rode
>
> --
> ------------------------------------------------------
> Martin Rode Tel 040-46093632
> Fax 040-46774884
> Programmfabrik GmbH Mobil 0171-1259525
> [EMAIL PROTECTED]
> ------------------------------------------------------
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
--
~-~-~-~-~-~-~-~-~-~-~-~-~-~-WEBEASY-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Michael Amster [EMAIL PROTECTED]
4676 Admiralty Way, Suite 300 Tel: 310.576.0770
Marina Del Rey, CA 90292 Fax: 310.576.2011
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
