AW: Unable to integrate Apache 2.0.24, mod_jk2 with Tomcat 5.

2004-09-03 Thread Gunnar Pörschke
Change settings of your workers file... Maybe tomcat does not use it???
 

-Ursprüngliche Nachricht-
Von: João Gil ACE-SC [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 3. September 2004 13:18
An: Tomcat Users List
Betreff: RE: Unable to integrate Apache 2.0.24, mod_jk2 with Tomcat 5.


Hello,

Thank's to Andy Eastham solution I managed to get Apache to forward *.jsp
requests to Tomcat. In adition I also discovered that I had to define
localhost(127.0.0.1) in JK2.properties file as without this config
Tomcat(JK2) was listening on the wrong IP(0.0.0.0.).

Servlets are still not being forwarded - Apache reports - 404 file not
found when I click on, for example, - http://localhost/MyServlet.
MyServlet exists on my root_path as MyServlet.class . Can anyone tell me how
to prevent this error and forward the request to Tomcat5?

Warmest Regards
Joao Gil



 

  Andy Eastham

  [EMAIL PROTECTED]To:   'Tomcat Users
List' [EMAIL PROTECTED]
  om  cc:

   Subject:  RE: Unable to
integrate Apache 2.0.24 with Tomcat 5.  
  02-09-2004 16:41

  Please respond to

  Tomcat Users

  List

 

 





Joao,

I looked at that url and the way redirections are configured is different to
mine.

I do NOT have things like
Location /*.jsp
JkUriSet worker ajp13:localhost:8009
/Location

Location /mywebapp
JkUriSet worker ajp13:localhost:8009
/Location

(in fact these look like mod_jk configuration to me)

Instead, my workers2.properties is as follows:
[logger.apache2]
#level=DEBUG

[shm]
file=/usr/local/apache2/logs/shm.file
size=1048576

# Example socket channel, override port and host.
[channel.socket:localhost:8009]
port=8009
host=127.0.0.1

# define the worker
[ajp13:localhost:8009]
channel=channel.socket:localhost:8009

# Uri mapping
[uri:192.168.0.103/wisadmin/*]
worker=ajp13:localhost:8009

[uri:localhost/wisadmin/*]
worker=ajp13:localhost:8009

[uri:wis/wisadmin/]
worker=ajp13:localhost:8009

[uri:127.0.0.1/wisadmin/*]
worker=ajp13:localhost:8009

Note that the URIs are mapped in this file.

Give this a try,

Andy

 -Original Message-
 From: João Gil ACE-SC [mailto:[EMAIL PROTECTED]
 Sent: 02 September 2004 16:25
 To: [EMAIL PROTECTED]
 Subject: Unable to integrate Apache 2.0.24 with Tomcat 5.


 Greatings,

 I am trying to integrate Apache 2.0.24 with Tomcat 5 with no success.

 The best solution I have found on the net is at 
 http://www.dynamicobjects.com/d2r/archives/002574.html

 After configuring Apache and Tomcat as instructed, both execute with 
 no problem. But Apache is still not forwarding JSP pages/Servlets to 
 Tomcat. Can anyone help me?

 Warmest Regards
 Joao Gil



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



AW: Unable to integrate Apache 2.0.24, mod_jk2 with Tomcat 5.

2004-09-03 Thread SH Solutions
Hi

 Servlets are still not being forwarded - Apache reports - 404 file 
 not
found when I click on, for example, - http://localhost/MyServlet.
MyServlet exists on my root_path as MyServlet.class . Can anyone tell me how
to prevent this error and forward the request to Tomcat5?

First, simply copying Java Classes to root_path does not work.
Servlets need to be
1. inside WEB-INF
2. NOT packageless
3. mapped in web.xml

Try to get tomcat with it's own html-connector to work first.
It is much easier than with apache / mod_jk.

THEN think about using tomcat without apache.
And only LAST, put mod_jk inbetween.
In that case, think about updateing your fairly old version of Apache2.
2.0.50 is current stable. 2.0.24 is old and has much more bugs. There should
be no problems, since the apache2 api is stable since 2.0.22.

Regards,
  Steffen


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]