dcsimg
Servlet is found only when port is specified in URL
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Irene_Vermaak
Posted On:   Monday, March 10, 2003 10:48 PM

If I specify the port (Tomcat's 8080) in my URL, my program runs fine and my servlet ../servlet/ReportsProcessSrv is found. But, if I only type in the URL and the servlet is called, I get the following error message: The requested URL /servlet/ReportsProcessSrv was not found on this server. Apache/1.3.26 Server at citrussa.trial.co.za Port 80 The people hosting the site, explained that Apache is running as the primary server and then it delegates the JSP pages to Tomcat, which sends it back to Apache. Tomcat is running on port 8080 and Apache on port 80. ReportsProcessSrv.class is in the folder /public_html/WEB-INF/classes/ From the error message I think that the server is looking f   More>>

If I specify the port (Tomcat's 8080) in my URL, my program runs fine and my servlet ../servlet/ReportsProcessSrv is found.

But, if I only type in the URL and the servlet is called, I get the following error message:

The requested URL /servlet/ReportsProcessSrv was not found on this server.

Apache/1.3.26 Server at citrussa.trial.co.za Port 80


The people hosting the site, explained that Apache is running as the primary server and then it delegates the JSP pages to Tomcat, which sends it back to Apache. Tomcat is running on port 8080 and Apache on port 80.


ReportsProcessSrv.class is in the folder /public_html/WEB-INF/classes/

From the error message I think that the server is looking for the servlet on Apache, while it should be looking on Tomcat??


I was wondering if I should put my servlet in another folder or if a setting on Apache can be changed so the server can look for my servlet on Tomcat?


Thanks,

Irene

   <<Less

Re: Servlet is found only when port is specified in URL

Posted By:   Christopher_Koenigsberg  
Posted On:   Tuesday, March 11, 2003 10:45 AM

As far as I know, someone has to add your servlet to Apache's httpd.conf, telling it to go to Tomcat for that URL. This is one thing that sucks about integrating Apache and Tomcat, that you can't just automatically deploy web apps without editing the Apache httpd.conf.



We have a script ("deploy.sh") which does this, but it still sucks because the Apache httpd has to be stopped and restarted, and then Tomcat has to be stopped and restarted (including waiting for each one to shut down all tcp port listeners), for each deployment or re-deployment of a web app.

About | Sitemap | Contact