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 pages. All I had to do was issue a reload at my browser and > the updated page would appear. So the problem has nothing to do with > cacheing on Apache. > > Still I cannot get the manager application to redeploy. Except now things > are worse, since the ability to update the pages without restarting the > Tomcat server has been lost. > > There must be SOMEONE out there who has gotten this to work. Please tell me > what I have to do to get the manager application to work behind Apache. So you are saying that you cannot go to /manager/reload?path/to/webapp? Do you get an error on the browser? If not, check the access_log of Apache and see if you received an error there. If the access_log shows a "good" return code on the /manager, then check the mod_jk log (wherever you set it up to be logged) and see if there any errors there. You might be dealing with an issue where Apache does not recognize that /managers needs to be redirected to Tomcat. Or, passing that point, it may be that mod_jk is not able to pass the connection to Tomcat. Anyway, more info would be needed. One more thing to add: if you can embed the mod_jk configs you added to httpd.conf and any workers.properties/mod_jk.properties you setup, I can help you better. HTH, Ben Ricker I cannot really answer your question until I know what exactly is not working and where it breaks down. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Ben Ricker <[EMAIL PROTECTED]> Wellinx.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
