up vote 0 down vote favorite
share [g+] share [fb]

We have instances of Tomcat 5 (JDK1.5) and Tomcat 6 (JDK1.6) running quite happily on a RHEL 4 machine. They are fronted by Apache 2.2.8 with mod_jk.

The Tomcat 5 instances are configured in the following way:

worker.x.type=lb
worker.x.balance_workers=node1
worker.x.sticky_session=True
worker.x.sticky_session_force=True

We tried configuring Tomcat 6 in the same way, but we received an error message:

Error in reading worker properties from '/applications/apache2/conf/workers.properties' Configuration Failed

The only way we could get it to work was by removing the last two lines from each configuration 'block' for the Tomcat 6 instances. The Tomcat 5 blocks remained as above, while the Tomcat 6 blocks became:

worker.x.type=lb
worker.x.balance_workers=node1

Can anyone explain why this is? Has something changed between the AJP in Tomcats 5 and 6?

link|improve this question
68% accept rate
What version of mod_jk? Also, are those last two lines necessary if there's just the one node defined? If you can enable debug logging on mod_jk, you should get a better idea on why mod_jk doesn't like these configuration directives. – mahnsc Aug 5 '11 at 20:43
Do you means you want to configure load balancing for 2 Tomcat instances with Apache as a frontend? If so, why did you specific only one node for balance_workers. If not, why did you set type=lb? – quanta Aug 23 '11 at 7:35
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.