what I get is normal ascii - but then I left everything ascii except the shell scripts. index.jsp doens't function (that has to do with "chunked" encoding I think because non-chunked-encoded jsp's seem to be fine). Most of the servlets function all right; I'll have a look at HalloWorld on Monday. Manager and admin do not work at the moment.
Anna ----- Original Message ----- From: "jean-frederic clere" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Friday, October 31, 2003 9:06 AM Subject: Re: TOMCAT-fix for os/390?? > Anna Fuhrmann wrote: > > Hi List, > > > > 4.1.28 does the job - but: > > /webapps/ROOT/index.jsp is screwed up; the browser cannot GET it, supposedly > > because > > of "chunked" encoded. It is HTTP1.1, which the browser does have. > > The first big chunk is "2000" big, we noticed when GETting it with a script. The > > browser GETs and GETs > > and GETs and never stops GETting ... Any remedies? > > Do you get ASCII or EBCDIC in the Tomcat response? - I am gettting EBCDIC for > the moment - > > While using Servlets I have problems with ResourceBundle. Does it works ok for > you (HelloWorldExample for example does not work)? > > > > > Anna > > > > ----- Original Message ----- > > From: "Bill Barker" <[EMAIL PROTECTED]> > > To: "Tomcat Developers List" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Friday, October 10, 2003 9:06 AM > > Subject: Re: Re: TOMCAT-fix for os/390?? > > > > > > > >>Try http://www.apache.org/dist/jakarta/tomcat-4/v4.1.28-alpha/. The 'alpha' > >>is just because it is still in it's evaluation stage. It's likely to > >>graduate to at least beta (if not 'stable'). However, your ability to test > >>it on an os/390 system makes you particularly valuable to the developers, so > >>I hope that you will try it out :). > >> > >>----- Original Message ----- > >>From: <[EMAIL PROTECTED]> > >>To: "Tomcat Developers List" <[EMAIL PROTECTED]> > >>Sent: Friday, October 10, 2003 12:35 AM > >>Subject: Re: Re: TOMCAT-fix for os/390?? > >> > >> > >> > >>>Well well ... being a simpleton (=user) I don't quite manage to manage > >> > >>cvs ... > >> > >>>I would love to install tomcat 4.1.28 (having 4.1.27), bit I cannot find > >> > >>such a distribution. > >> > >>>So what it boils down to if I cannot get 4.1.28 is: install rls 6 BETA - > >> > >>does it go well with JDK 1.3? > >> > >>>thank you very much for your help > >>>Anna > >>> > >>>>Von: Dirk Verbeeck <[EMAIL PROTECTED]> > >>>>Datum: 2003/10/09 Do PM 10:53:59 GMT+02:00 > >>>>An: Tomcat Developers List <[EMAIL PROTECTED]> > >>>>Betreff: Re: TOMCAT-fix for os/390?? > >>>> > >>>>Hi Anna > >>>> > >>>>I don't use tomcat on os390 but by reading you problem I suspect your > >>>>problem is solved in cvs, you need at least revision 1.16.2.1 > >>>> > >> > >><http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-tomcat-connectors/http > >>11/src/java/org/apache/coyote/http11/InternalOutputBuffer.java?rev=1.16.2.1> > >> > >>>>or 1.18 > >>>> > >> > >><http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-tomcat-connectors/http > >>11/src/java/org/apache/coyote/http11/InternalOutputBuffer.java?rev=1.18> > >> > >>>>of the following file: > >>>> > >> > >>http://cvs.apache.org/viewcvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/InternalOutputBuffer.java > >> > >>>>Releases including this fix are TOMCAT_5_0_13 > >>>> > >> > >><http://cvs.apache.org/viewcvs/jakarta-tomcat-connectors/http11/src/java/org > >>/apache/coyote/http11/InternalOutputBuffer.java?only_with_tag=TOMCAT_5_0_13> > >>, > >> > >>>>TOMCAT_5_0_12 > >>>> > >> > >><http://cvs.apache.org/viewcvs/jakarta-tomcat-connectors/http11/src/java/org > >>/apache/coyote/http11/InternalOutputBuffer.java?only_with_tag=TOMCAT_5_0_12> > >>, > >> > >>>>TOMCAT_4_1_28 > >>>> > >> > >><http://cvs.apache.org/viewcvs/jakarta-tomcat-connectors/http11/src/java/org > >>/apache/coyote/http11/InternalOutputBuffer.java?only_with_tag=TOMCAT_4_1_28> > >> > >>>>Cheers > >>>>Dirk > >>>> > >>>>Anna Fuhrmann wrote: > >>>> > >>>> > >>>>>Hi all, > >>>>>like a good girl I have been using the user-mailing-list up to now to > >> > >>search for > >> > >>>>>user experience installing tomcat on os390. > >>>>> > >>>>>Most (if not all) contributions are in the form "has anyone > >> > >>successfully installed > >> > >>>>>tomcat on os390?" From some other I got partly valuable ideas. > >>>>> > >>>>>I have been TRYING to get tomcat run on os390 in the last couple of > >> > >>days. > >> > >>>>>Done everything I could - everything seems to be allright up to this > >> > >>pont: tomcat IS running at last > >> > >>>>>without any serious signs of disbehaviour - no error messages at all, > >> > >>xml's behaving well. But if we connect to > >> > >>>>>localhost:tomcatport/index.jsp (or wahtever else for that matter), the > >> > >>browser does not show > >> > >>>>>anything. Doing the same with a perl script shows that the server is > >> > >>ansering and is supplying the > >> > >>>>>requested page, BUT EACH LINE OF THE HTTP_HEADER CONTAINS AN INVALID > >>>>>(i.e.: ebcdic) LINE SEPARATOR. So thats the reason why. > >>>>> > >>>>>Today I tried to identify the .java-file giving us the header (looking > >> > >>for \r\n) . I thought I found it, > >> > >>>>>by my hex.editor did not show me any 0x0d15 (which ought to be the > >> > >>suspect, i.e. Newline > >> > >>>>>in ebcdic). > >>>>> > >>>>>What I would like to know: Is there any kind of patch for os/390? Do > >> > >>you have any suggestions? > >> > >>>>>Is anybody working on it? What should I do? I want to have this beast > >> > >>running. > >> > >>>>>PLEASE. > >>>>> > >>>>>We have os390 2.10 > >>>>>IBM-JDK 1.3 > >>>>>tomcat 4.1.27 > >>>>> > >>>>>Anna Fuhrmann > >>>>> > >>>>> > >>>> > >>>> > >>>> > >>>> > >>>>--------------------------------------------------------------------- > >>>>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>>For additional commands, e-mail: [EMAIL PROTECTED] > >>>> > >>>> > >>> > >>> > >>>--------------------------------------------------------------------- > >>>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >> > >> > > > > > > -------------------------------------------------------------------------------- > > > > > > > >>This message is intended only for the use of the person(s) listed above as the > >>intended recipient(s), and may contain information that is PRIVILEGED and > >>CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or > >>distribute this message or any attachment. If you received this communication in > >>error, please notify us immediately by e-mail and then delete all copies of this > >>message and any attachments. > >> > >>In addition you should be aware that ordinary (unencrypted) e-mail sent through > >>the Internet is not secure. Do not send confidential or sensitive information, > >>such as social security numbers, account numbers, personal identification numbers > >>and passwords, to us via ordinary (unencrypted) e-mail. > >> > >> > > > > > > > > -------------------------------------------------------------------------------- > > > > > > > >>--------------------------------------------------------------------- > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
