org
Subject: Re: Servlets mod_jk Context path problems
MMM, I've just probed to access
http://192.168.1.2:8080/ecommerce/ecommerce/Controller and I've accessed to
the servlet. What must I change to access as
http://192.168.1.2/ecommerce/Controller?
jeusdi wrote:
>
> So, the probl
MMM, I've just probed to access
http://192.168.1.2:8080/ecommerce/ecommerce/Controller and I've accessed to
the servlet. What must I change to access as
http://192.168.1.2/ecommerce/Controller?
jeusdi wrote:
>
> So, the problem surges out form tomcat because I can't access it.
>
> If I try a
So, the problem surges out form tomcat because I can't access it.
If I try access throught 192.168.1.2/ecommerce/Controller the message is the
same, so it comes form Tomcat.
I've seen jk log messages and i works correctly.
So, What's wrong is tomcat?
Yassine ELassad (YEL) wrote:
>
> hi
>
>
hi
try to access the context directly via port 8080, so you know it's a
mod_jk related issue
if you can access
http://yourHostMachine:8080/ecommerce/Controller
so the problem is coming from your JK configuration otherwise it from tomcat
Greeting Yassine
Cologne, Germany
On 8/16/06, jeusdi
Mmm, I've changed httpd.conf file and web.xml file to this -->
In httpd.conf I've added JkMount /ecommerce/Controller treb
and in web.xml file I've changed mapping -->
Controller
/ecommerce/Controller
And the result is The requested resource (/ecommerce/Controller) is not
av
Hi jeusdi,
in your Apache configuration you juts Jkmount JSP files that are
inside your Application as the statement say:
JkMount /ecommerce/*.jsp treb
and you are trying to get this :
/ecommerce/servlets/ControllerServlet
which does not match the directive above either you need to change
th
