Re: mod_proxy or mod_jk?

2007-11-19 Thread Jim Jagielski

It almost sounds like it's more a config issue than
a module one... Using mod_proxy_ajp is nice because
you use normal httpd directives (ProxyPass. etc..)
to handle the stuff that TC needs to handle.

On Nov 17, 2007, at 8:20 PM, Rocco Scappatura wrote:



Hello.

I would like to publish a Web application running under Tomcat.

I'm using Apache 2 as Web server.

Basically, I have two opportunities:

1) mod_jk
2) mod_proxy

I've tried the first. So I discover that I ve:

- Create an alias in httpd.conf so that al static pages are processed
directly by Apache2.
- Use JkMount directive so that path is mapped to worker (and so to  
Tomcat)


I don't know I have well understod the concept, but I have noted that
application doesn't work correcltly. For example, assuming that the  
path
of the application is '/path'. When I accesst to http://hostname/ 
path
all works fine. But if I access to http://hostname/path/subpath I  
get

Visualizzation errors (It seems tome that it misses CSS.. and so on).

I read that it is possible to use mod proxy.

Now, I would like to know from mailing list if mod_proxy is the best
choice or otherwise if I have to solve problem similiar to the one  
I ve

pointed out above, and to use mod_jk.

Thanks,

rocsca




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: mod_proxy or mod_jk?

2007-11-19 Thread Rainer Jung

Rocco Scappatura wrote:

Hello.

I would like to publish a Web application running under Tomcat.

I'm using Apache 2 as Web server.

Basically, I have two opportunities:

1) mod_jk
2) mod_proxy

I've tried the first. So I discover that I ve:

- Create an alias in httpd.conf so that al static pages are processed
directly by Apache2.
- Use JkMount directive so that path is mapped to worker (and so to Tomcat)

I don't know I have well understod the concept, but I have noted that
application doesn't work correcltly. For example, assuming that the path
of the application is '/path'. When I accesst to http://hostname/path
all works fine. But if I access to http://hostname/path/subpath I get
Visualizzation errors (It seems tome that it misses CSS.. and so on).

I read that it is possible to use mod proxy.

Now, I would like to know from mailing list if mod_proxy is the best
choice or otherwise if I have to solve problem similiar to the one I ve
pointed out above, and to use mod_jk.


Your problem sounds like a simple config issue, but since you didn't 
show us your config, who knows ...


mod_proxy_* vs. mod_jk: mod_proxy_* comes automatically with httpd and 
is more tightly integrated into it, mod_jk is still more powerful 
especially concerning complex instance topologies. So your decision 
might depend on how complex you expect your final setup to be.



Thanks,

rocsca


Regards,

Rainer

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: mod_proxy or mod_jk?

2007-11-19 Thread Rocco Scappatura

 put this in your servlet.xml file

 Host name=localhost appBase=webapps unpackWARs=true
 autoDeploy=true
 xmlValidation=false xmlNamespaceAware=false
 !--  Added this for JK THIS--
   Listener className=org.apache.jk.config.ApacheConfig append=true
 forwardAll=false modJk=Path/To/mod_jk.so /
 /Host
OK.

 Start Tomcat it will generate the mod_jk.conf file under
 Tomcat/conf/auto
OK

 In the apache httpd.cong file... somewhere near the bottom...
 add
 # I added this for connector ==
 Include Path/To/Tomcat 5.5/conf/auto/mod_jk.conf
Done.

 That will make apache front end tomcat...I
It was already?

 Then just study those files...
 It generates all the core stuff... all the JKMounts folder protection etc
 for all your webapps.

??  What files do you refer?

 Then you can edit as required... add aliases etc.

 Load sharing is different again... but the generated file comes in handy
 there as well.
 Remember that everytime you start tomcat this is generated... so remove
 the
 listener if you dont want it to change, or copy it and point apache at
 that.

???

I don't unserstandvery well..

Thanks, rocsca


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: mod_proxy or mod_jk?

2007-11-18 Thread Johnny Kewl


---
HARBOR: http://coolharbor.100free.com/index.htm
Now Tomcat is also a cool pojo application server
---
- Original Message - 
From: Rocco Scappatura [EMAIL PROTECTED]

To: users@tomcat.apache.org
Sent: Sunday, November 18, 2007 3:20 AM
Subject: mod_proxy or mod_jk?

You need to post your config files for real help...
I think everyone is tired of arguing the differences... just google for 
that.
I like mod_jk just because its worked on by Tomcat developers and thus the 
focus is very much on Tomcat.


Here a tip to get you going...
This works on TC 5.5

put this in your servlet.xml file

Host name=localhost appBase=webapps unpackWARs=true autoDeploy=true 
xmlValidation=false xmlNamespaceAware=false

!--  Added this for JK THIS--
 Listener className=org.apache.jk.config.ApacheConfig append=true 
forwardAll=false modJk=Path/To/mod_jk.so /

   /Host

Start Tomcat it will generate the mod_jk.conf file under 
Tomcat/conf/auto

In the apache httpd.cong file... somewhere near the bottom...
add
# I added this for connector ==
Include Path/To/Tomcat 5.5/conf/auto/mod_jk.conf

That will make apache front end tomcat...

Then just study those files...
It generates all the core stuff... all the JKMounts folder protection etc 
for all your webapps.


Then you can edit as required... add aliases etc.

Load sharing is different again... but the generated file comes in handy 
there as well.
Remember that everytime you start tomcat this is generated... so remove the 
listener if you dont want it to change, or copy it and point apache at that.


Have fun...



Hello.

I would like to publish a Web application running under Tomcat.

I'm using Apache 2 as Web server.

Basically, I have two opportunities:

1) mod_jk
2) mod_proxy

I've tried the first. So I discover that I ve:

- Create an alias in httpd.conf so that al static pages are processed
directly by Apache2.
- Use JkMount directive so that path is mapped to worker (and so to 
Tomcat)


I don't know I have well understod the concept, but I have noted that
application doesn't work correcltly. For example, assuming that the path
of the application is '/path'. When I accesst to http://hostname/path
all works fine. But if I access to http://hostname/path/subpath I get
Visualizzation errors (It seems tome that it misses CSS.. and so on).

I read that it is possible to use mod proxy.

Now, I would like to know from mailing list if mod_proxy is the best
choice or otherwise if I have to solve problem similiar to the one I ve
pointed out above, and to use mod_jk.

Thanks,

rocsca




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]