Until now, I’ve only ever been running QaaWS on a single server, the same server that TomCat was running on. Working great.
I’m now looking at a cluster of XI 3.1 machines, and trying to get QaaWS working on them. there are 2 machines in the cluster
Server IHSERV0001, this is where the qaaws are published. Tomcat installed but not running.
Server IHSERV0006, Tomcat installed and running.
Both machines have a full BO 3.1 SP6 stack installed.
NLB sits in front with both servers listed, it currently only ‘sees’ IHSERV0006, as that is the only machine with Tomcat running. All web traffic is being directed to this machine.
I have a crossdomain.xml file, placed in the ROOT directory of TomCat on both servers. The contents are identical
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-http-request-headers-from domain="*" headers="*" secure="false" />
<allow-access-from domain="*" secure="false" />
</cross-domain-policy>
When I try and run an xcelsius file, when it gets to a QaaWS, I get the following error:
If I turn on TomCat on IHSERV0001, and go directly against this server for Infoview, everything is good. If I use the cluster name, I now have a 50/50 chance of it working (if the traffic is directed to IHSERV0001) and failing (if traffic is directed to IHSERV0006).
I’m sure I’ve screwed up on the configuration somewhere, but does anyone have any idea on how I can get this working? We’re looking at only running one web server, and the BO stack will not be installed on this machine. There will be 6 servers in the cluster eventually, and one IHSERV0001 will be dedicated to running QaaWS, though this may be spread out over a few more servers eventually.
adrian.procter 
(BOB member since 2006-09-26)
(BOB member since 2003-11-27)