- Original Message -
From: Jacob Kjome [EMAIL PROTECTED]
Subject: Re: Tomcat application redeploy behind Apache server
I would suggest that you quit using mod_webapp. It is not actively
developed any longer. Use mod_jk or jk2. mod_webapp is probably doing
some funky cacheing. I
will
be hard pressed to find any support out there for it. Make the switch and
see if mod_jk or jk2 solves your problem.
Jake
At 03:49 PM 3/8/2003 -0500, you wrote:
- Original Message -
From: Ben Ricker [EMAIL PROTECTED]
Subject: Re: Tomcat application redeploy behind Apache server
So you
- Original Message -
From: Ben Ricker [EMAIL PROTECTED]
Subject: Re: Tomcat application redeploy behind Apache server
So you are saying that you cannot go to /manager/reload?path/to/webapp?
No. The manager application works perfectly. The application is redeployed
and I can see
- Original Message -
From: Ben Ricker [EMAIL PROTECTED]
Subject: Re: Tomcat application redeploy behind Apache server
On Tue, 2003-03-04 at 09:43, Jim Cobban wrote:
I am sorry to keep harping on this, but I still am no closer to solving
my
problem. I don't even know where to look
On Fri, 2003-03-07 at 15:59, Jim Cobban wrote:
The problem I was having with the connector was NOT that updated pages were
not visible after the redeploy with the manager app. It was only that
updated classes were not visible. Indeed I did not even have to redeploy to
see the updated
] Tomcat application redeploy behind Apache
server
I have a problem that when I redeploy my JSP/servlet application on a
Tomcat
server, the new behavior is not visible to users who access the
applications
through an Apache HTTP server which is the front-end. The new behavior is
seen if I go
Subject: Re: [EMAIL PROTECTED] Tomcat application redeploy behind Apache
server
I have a problem that when I redeploy my JSP/servlet application on a
Tomcat
server, the new behavior is not visible to users who access the
applications
through an Apache HTTP server which is the front-end
