OKay, I left my webapp config in and added jk_mod.  jk_mod works like a
champ!  I will press on with this and watch webapp to see if it dies or
lives.
Thanks for the email attachment that worked well.
B

-----Original Message-----
From: Lauer, Oliver [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 07, 2001 7:31 AM
To: 'Tomcat Users List'
Subject: AW: ONE More Time! why does Tomcat 4 work this way


Maybe you try mod_jk for Linux due to I had the same comparable problems
with Solaris 2.6. You can easily built it from source using the mail
attached.
Oliver


> AXA eSolutions GmbH
> AXA Konzern AG Germany
> Oliver Lauer 
> Web Architect
> W�rthstra�e 34
> D-50668 K�ln
> Germany
> Tel.: +49 221 148 31277
> Fax: +49 221 148 43963
> Mobil: +49 179 59 064 59
> e-Mail: [EMAIL PROTECTED]
> _____________________________
> 


-----Urspr�ngliche Nachricht-----
Von: Sri K Ganjam [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 7. Dezember 2001 07:08
An: Tomcat Users List
Betreff: Re: ONE More Time! why does Tomcat 4 work this way


Hi,
I just subscribed to this list yesterday only. I am trying to port and
improve the mod_webapp on Linux /390. I successfully built it and ran it
under windows 2000 and RedHat linux  without any changes from source drop, I
downloaded from here
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/src/
but I find many problems with mod_webapp such as:
1. the requests are taking long to get served even a simple hello servlet
takes 90+ seconds to display from localhost.
2. the error "socket closed: connection reset by peer" comes up often (
every 3-4 request)
Does any one else faced the same problems?
Thanks and Regards,
Sri K Ganjam
----- Original Message -----
From: "Brian Adams" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Friday, December 07, 2001 2:47 AM
Subject: RE: ONE More Time! why does Tomcat 4 work this way


> clue please.  were is mod_webapp code?  no see cvs module
>
>
>
>
> -----Original Message-----
> From: Jeff Kilbride [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 06, 2001 3:09 PM
> To: Tomcat Users List
> Subject: Re: ONE More Time! why does Tomcat 4 work this way
>
>
> Sorry, but I forgot to mention that your other option would be to pull the
> latest mod_webapp code from CVS and see if that helps. I just checked the
> dev list and it looks like somebody is working on it -- though I don't
know
> who...
>
> --jeff
>
> ----- Original Message -----
> From: "Brian Adams" <[EMAIL PROTECTED]>
> To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
> Sent: Thursday, December 06, 2001 12:35 PM
> Subject: RE: ONE More Time! why does Tomcat 4 work this way
>
>
> > I think that is what I would like to do after looking WAY TOO CLOSE at
> this.
> >
> > Patrick I know your out there *peer* what do you say?  Let's move to
> mod_jk
> > *point*
> > B
> >
> > -----Original Message-----
> > From: Jeff Kilbride [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, December 06, 2001 2:57 PM
> > To: Tomcat Users List
> > Subject: Re: ONE More Time! why does Tomcat 4 work this way
> >
> >
> > Personally, I would drop mod_webapp in favor of mod_jk, if you really
need
> > to run a separate web server. TC 4 was the first release of mod_webapp,
> > while mod_jk has been around much longer -- and is better tested. AFAIK,
> > there was only one guy working on mod_webapp and he announced he was
> taking
> > a long vacation a few weeks ago. I don't know if anybody has picked up
> where
> > he left off. TC 4.0.1 has a configuration line for mod_jk already
included
> > in server.xml.
> >
> > Looking through the list lately, a large percentage of the messages I
see
> > all relate to problems with mod_webapp.
> >
> > Your call...
> >
> > --jeff
> >
> > P.S. -- I've found TC 4 to be faster without the use of Apache. I use a
> > small footprint webserver (i.e. Acme's thttpd or Dan Bernstein's
> publicfile)
> > to serve images from another port (81) and let TC handle all the dynamic
> > stuff -- I don't have any non-dynamic html files on my site...
> >
> >
> > ----- Original Message -----
> > From: "Brian Adams" <[EMAIL PROTECTED]>
> > To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
> > Sent: Thursday, December 06, 2001 12:15 PM
> > Subject: RE: ONE More Time! why does Tomcat 4 work this way
> >
> >
> > > I tried that and it does not work either.
> > > I noticed that the examples that come with tomcat 4 does not show the
> > images
> > > also!
> > > This is definitely a problem with WebAPP. I can connect to Tomcat
> directly
> > > 8080 and it works fine.  I've seen others on the list server asking
> about
> > > the same problem...
> > > Who is in charge of WebApp developement?  Their List Serve?
> > > B
> > >
> > > -----Original Message-----
> > > From: Jeff Kilbride [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, December 06, 2001 2:36 PM
> > > To: Tomcat Users List
> > > Subject: Re: ONE More Time! why does Tomcat 4 work this way
> > >
> > >
> > > What about  just "/images/butterfly.jpg"? This assumes that your
webapp
> is
> > > rooted at /bbb -- so you don't need to use that as part of your path.
> This
> > > is what I normally use with mod_jk. Don't know if it will work with
> > > mod_webapp, though.
> > >
> > > --jeff
> > >
> > > ----- Original Message -----
> > > From: "Brian Adams" <[EMAIL PROTECTED]>
> > > To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
> > > Sent: Thursday, December 06, 2001 11:12 AM
> > > Subject: RE: ONE More Time! why does Tomcat 4 work this way
> > >
> > >
> > > > there must be some sort of <filter> tag being enforced by tomcat 4.0
> > that
> > > > make me define the images directory before I just start using it...
> > > > any hints?
> > > >
> > > > -----Original Message-----
> > > > From: Carsten Lingemann
[mailto:[EMAIL PROTECTED]]
> > > > Sent: Thursday, December 06, 2001 1:31 PM
> > > > To: 'Tomcat Users List'
> > > > Subject: RE: ONE More Time! why does Tomcat 4 work this way
> > > >
> > > >
> > > > have you tried the following:
> > > >
> > > > <img border="0" src="<%= request.getContextPath()
> > > %>/images/butterfly.jpg">
> > > >
> > > > Carsten
> > > >
> > > > -----Original Message-----
> > > > From: Brian Adams [mailto:[EMAIL PROTECTED]]
> > > > Sent: Thursday, December 06, 2001 2:04 PM
> > > > To: '[EMAIL PROTECTED]'
> > > > Subject: ONE More Time! why does Tomcat 4 work this way
> > > >
> > > >
> > > > I hace Apache with WebApp warping to tomcat
> > > > my jsp page has this image:
> > > > <img border="0" src="/bbb/images/butterfly.jpg">
> > > > The web-app is named bbb and it has a directory called images.  The
> jsp
> > > page
> > > > WILL NOT SHOW THIS IMAGE!!!
> > > >
> > > > If I change it to:
> > > > <img border="0" src="http://localhost/bbb/images/butterfly.jpg";>  It
> > works
> > > > fine and fast!
> > > >
> > > > WHAT THE F*&(* is up with my config or Tomcat???
> > > >
> > > > my warp definition is:
> > > > everything that has a bbb after the url warps to Tomcat
> > > > WebAppConnection conn warp localhost:8008
> > > > WebAppDeploy examples conn /examples
> > > > WebAppDeploy bbb conn /bbb
> > > >
> > > > Am I missing something in my web.xml that should say how to handle
the
> > > > images folder?
> > > >
> > > > B
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > To unsubscribe:
<mailto:[EMAIL PROTECTED]>
> > > > For additional commands:
<mailto:[EMAIL PROTECTED]>
> > > > Troubles with the list:
<mailto:[EMAIL PROTECTED]>
> > > >
> > > > --
> > > > To unsubscribe:
<mailto:[EMAIL PROTECTED]>
> > > > For additional commands:
<mailto:[EMAIL PROTECTED]>
> > > > Troubles with the list:
<mailto:[EMAIL PROTECTED]>
> > > >
> > > > --
> > > > To unsubscribe:
<mailto:[EMAIL PROTECTED]>
> > > > For additional commands:
<mailto:[EMAIL PROTECTED]>
> > > > Troubles with the list:
<mailto:[EMAIL PROTECTED]>
> > > >
> > >
> > >
> > > --
> > > To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> > > For additional commands: <mailto:[EMAIL PROTECTED]>
> > > Troubles with the list: <mailto:[EMAIL PROTECTED]>
> > >
> > > --
> > > To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> > > For additional commands: <mailto:[EMAIL PROTECTED]>
> > > Troubles with the list: <mailto:[EMAIL PROTECTED]>
> > >
> >
> >
> > --
> > To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> > For additional commands: <mailto:[EMAIL PROTECTED]>
> > Troubles with the list: <mailto:[EMAIL PROTECTED]>
> >
> > --
> > To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> > For additional commands: <mailto:[EMAIL PROTECTED]>
> > Troubles with the list: <mailto:[EMAIL PROTECTED]>
> >
>
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>



----------------------------
Aus Rechts- und Sicherheitsgruenden ist die in dieser E-Mail gegebene
Information nicht rechtsverbindlich. Eine rechtsverbindliche Bestaetigung
reichen wir Ihnen gerne auf Anforderung in schriftlicher Form nach. Beachten
Sie bitte, dass jede Form der unautorisierten Nutzung, Veroeffentlichung,
Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail nicht gestattet
ist.Diese Nachricht  ist ausschliesslich fuer den bezeichneten Adressaten
oder dessen Vertreter bestimmt. Sollten Sie nicht der vorgesehene Adressat
dieser E-Mail oder dessen Vertreter sein, so bitten wir Sie, sich mit dem
Absender der E-Mail in Verbindung zu setzen.
----------------------------
For legal and security reasons the information provided in this e-mail is
not legally binding. Upon request we would be pleased to provide you with a
legally binding confirmation in written form. Any form of unauthorised use,
publication, reproduction, copying or disclosure of the content of this
e-mail is not permitted. This message is exclusively for the person
addressed or their representative. If you are not the intended recipient of
this message and its contents, please notify the sender immediately.
---------------------------


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to