Re: jk connector problems

2006-11-15 Thread brian bay
did you try setting the default host in the workers.properties file to the actual host you want apache to forward to tomcat? worker.default.host = 10.x.x.x instead of worker.default.host=127.0.0.1 Brian On 11/15/06, Martin Gainty [EMAIL PROTECTED] wrote: The connectors tutorial is

Re: Need setting up Tomcat with Apache web-server

2006-11-15 Thread brian bay
This looks suspiciously not right... Connector port=8009 enableLookups=false redirectPort=8443 protocol=AJP/1.3 / Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Also, your on windows

Re: [REPOST] Can't get apache and Tomcat to talk

2006-09-19 Thread brian bay
sorry I failed to mention that I was running tomcat5.5.17... minor details. On 9/15/06, Rob Tanner [EMAIL PROTECTED] wrote: Mark, Thank you. That took care of the problem. -- Rob On 09/15/2006 05:28 PM, Mark Thomas wrote: Rob Tanner wrote: Brian, Adding the Listener ... / parameter

Re: [REPOST] Can't get apache and Tomcat to talk

2006-09-15 Thread brian bay
Do you have a Listener set up in your tomcat server.xml? Inside of EngineHost Listener className=org.apache.jk.config.ApacheConfig modJk=/usr/lib/apache2/modules/mod_jk.so workersConfig=/etc/apache2/workers.properties/ I placed my workers.properties file in

Tomcat 5.5.17 role-name*/role-name behavior change

2006-09-01 Thread brian bay
I recently upgraded from tomcat 5.0.28 to 5.5.17. I have security set up on all my apps to allow any user that can authenticate against ldap access to the application So in 5.0.28, I defined role-name*/role-name to allow all role names. In 5.5.17 the behavior changes on the role-name

Re: Tomcat 5.5.17 role-name*/role-name behavior change

2006-09-01 Thread brian bay
authenticates all roles. Brian Bay On 9/1/06, brian bay [EMAIL PROTECTED] wrote: I recently upgraded from tomcat 5.0.28 to 5.5.17. I have security set up on all my apps to allow any user that can authenticate against ldap access to the application So in 5.0.28, I defined role-name*/role

Re: Migration from jk2 to jk, problems with uri context

2006-09-01 Thread brian bay
I have this working with tomcat 5.5.17 and apache2, jk1 You need mod_jk.so in apache/modules..for me /usr/lib/apache2/modules/mod_jk.so In apache home ---create workers.properties workers.tomcat.home=/path/to/tomcat ps=/ workers.list=worker1 worker.ajp13.type=ajp13

Re: Tomcat 5.5.17 role-name*/role-name behavior change

2006-09-01 Thread brian bay
-threads.. Brian On 9/1/06, Bill Barker [EMAIL PROTECTED] wrote: It would have been easier to change server.xml, to something like: Realm allRolesMode=strictAuthOnly .. / brian bay [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] SOLVED! Well since no one else seems to care