Friday, 19th April 2024

Comment posted Preserve Session IDs of Tomcat cluster behind Apache reverse proxy / Sticky sessions with mod_proxy and Tomcat by .

Recent comments by

Share this on:

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

No Responses to “…”

  1. admin says:
    Firefox 29.0 Firefox 29.0 Windows 7 x64 Edition Windows 7 x64 Edition
    Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0

    One other note for those new to Tomcat is short explanation on maxThreads and acceptCount.setting in server.xml
     

    maxThreads – defines how many parallel connections Tomcat could serve (to Java VM).

    acceptCount – is the amount of message queue size, requests to Tomcat which are higher than the requests defined by maxThreads will be stored in a queue (those onhold queue could hold a maximum number of requets).

    View CommentView Comment
  2. admin says:
    Firefox 29.0 Firefox 29.0 Windows 7 x64 Edition Windows 7 x64 Edition
    Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0

    If you get some timeouts issues from Tomcat to Apache Reverse Proxy. Try setting to BalancerMember max=64. This timeout issues are common for Apache to work with mod_worker, you should have a configuration like:

    <Proxy balancer://mycluster>
       BalancerMember ajp://10.16.166.48:11010/ route=delivery1 timeout=30 retry=1 max=64
       BalancerMember ajp://10.16.166.70:11010/ route=delivery2 timeout=30 retry=1 max=64
       </Proxy>

    View CommentView Comment