I'm attempting to set up a Tomcat cluster on Windows. It is mostly working, but I'm struggling with failover.
I'm using the 64-bit versions of:
- Apache 2.4
- JRE 7
- Tomcat 7.0.23
I set up Apache using this guide, and configured Tomcat clustering using info from here and here. I used wdeploy to split the static and dynamic content between Apache and Tomcat, then copied the Tomcat directory and made the required port changes.
I added the <distributable/> tag to BOE/WEB-INF/web.xml
Load Balancing is working perfectly. When I go to http://server/BOE/BI, the connection is assigned to one of the two Tomcats.
Using Tomcat manager, I can see that the sessions are properly replicated. So when the connection is assigned to TomcatB, the manager on TomcatC will show the session as a Backup.
When one Tomcat is killed, I know that the survivor is aware of it. I see this is the log:
INFO: Received member disappeared:org.apache.catalina.tribes.membership.MemberImpl[tcp://{10, 219, 24, 208}:5000,{10, 219, 24, 208},5000, alive=818797, securePort=-1, UDP Port=-1, id={-19 66 86 -88 68 -20 74 -79 -123 126 9 -51 69 111 -128 -74 }, payload={}, command={66 65 66 89 45 65 76 69 88 ...(9)}, domain={}, ]
However, BI Launchpad isn't handling it so well. If I log in to http://server/BOE/BI while both Tomcats are up, then kill the Tomcat that the connection was assigned to, the next action in Launchpad produces an HTTP 500. These are the first few lines of the exception:
SEVERE: Servlet.service() for servlet [equinoxbridgeservlet] in context with path [/BOE] threw exception
java.lang.RuntimeException: org.apache.jasper.JasperException: java.lang.NullPointerException
at com.businessobjects.http.servlet.internal.BundlePathAwareServiceHandler.serviceHelper(BundlePathAwareServiceHandler.java:254)
at com.businessobjects.http.servlet.internal.BundlePathAwareServiceHandler.service(BundlePathAwareServiceHandler.java:197)
at com.businessobjects.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:248)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:220)
I wrote a very simple page that just prints out current session info. This page does fail over properly.
I found an SAP Note that is similar to my problem, although not identical. I don't believe it is the same problem, since there are no firewall rules on my server that would be interfering, all of the traffic is local, and it is working with my test page.
Has anyone been successful with failover using a similar configuration as mine?