workers2.properties # only at beginning. In production uncomment it out [logger.apache2] level=DEBUG
[shm] file=z:/tomcat/logs/jk2.shm size=1048576 # Example socket channel, override port and host. [channel.socket:localhost:8109] port=8109 host=127.0.0.1 [channel.socket:localhost:8110] port=8110 host=127.0.0.1 [channel.socket:localhost:8111] port=8111 host=127.0.0.1 #[channel.jni:jni] #info=The jni channel, used if tomcat is started inprocess [status:] info=Status worker, displays runtime informations # Define the worker # First Web Application Worker [ajp13:localhost:8109] channel=channel.socket:localhost:8109 # Second Web Application Worker [ajp13:localhost:8110] channel=channel.socket:localhost:8110 # Third Web Application Worker [ajp13:localhost:8111] channel=channel.socket:localhost:8111 Uri mapping [uri:127.0.0.1/*.jsp] worker=ajp13:localhost:8109 [uri:/jkstatus/*] info=Display status information and checks the config file for changes. worker=status:status [uri:www.session1.com/*.jsp] worker=ajp13:localhost:8109 [uri:www.session2.com/*.jsp] worker=ajp13:localhost:8110 [uri:www.session3.com/*.jsp] worker=ajp13:localhost:8111 Here is my properties file. I hope that this helps you out. I am currently running with three seperate instances from one binary install of tomcat. This allows me the flexibility to start and stop each instance without afecting the the other two. Dean -----Original Message----- From: Tatu Vanhanen [mailto:[EMAIL PROTECTED] Sent: Fri 11/7/2003 02:17 To: User Tomcat Cc: Subject: Tomcat + jk2 connector configuration Hello, We have a development environment where each developer has a separate Tomcat instance to play with. Each Tomcat should listen in it's port for requests coming from the Apache front-end. The mappings for each user's Tomcat should be based on the request uri, i.e. http://www.somehost.com/user1/xxxx means that Apache should forward the requests having 'user1' to user1's running Tomcat instance. We have this working with the "ancient" Warp- connector but we should move to jk2 because of some issues with warp. Could someone please include some example of workers2.properties/jk2.properties that would give us some hint of how to make things work. Yes, we have tried to configure things but apparently something has been missing and we are still stuck with warp :( Below is our workers2.properties (with user names replaced with more "publishable" names). Is there something missing there? Thanks a lot! workers2.properties: [logger.apache2] level=DEBUG [shm] file=/www/logs/shm.file size=1048576 # First Tomcat serving a product under tests [channel.socket:localhost:9025] port=9025 maxPort=9025 host=127.0.0.1 [ajp13:localhost:9025] channel=channel.socket:localhost:9025 [uri:/product1/*] worker1=ajp13:localhost:9025 # user1 [channel.socket:localhost:9031] port=9031 maxPort=9031 host=127.0.0.1 [ajp13:localhost:9031] channel=channel.socket:localhost:9031 [uri:/user1/*] worker1=ajp13:localhost:9031 # user2 [channel.socket:localhost:9029] port=9029 maxPort=9029 host=127.0.0.1 [ajp13:localhost:9029] channel=channel.socket:localhost:9029 [uri:/user2/*] worker1=ajp13:localhost:9029 # user3 [channel.socket:localhost:9027] port=9027 maxPort=9027 host=127.0.0.1 [ajp13:localhost:9027] channel=channel.socket:localhost:9027 [uri:/user3/*] worker1=ajp13:localhost:9027 # user4 [channel.socket:localhost:9021] port=9021 maxPort=9021 host=127.0.0.1 [ajp13:localhost:9021] channel=channel.socket:localhost:9021 [uri:/user4/*] worker1=ajp13:localhost:9021 --------------------------------------------------------------------- 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]
