Question
Two instances in a cluster with the same docroot
I'm setting up a cluster with two instances running on the
same machine under IIS 6. I've followed the official documentation
for doing so, and it seems to be running fine. However, each
instance has its own document root, under c:\jrun4\servers\... etc.
However, the IIS site I have the cluster connected to has its own
document root, which I assumed would be used once I connected the
cluster to IIS and accessed the website at the default port.
When I access pages on the IIS site, IIS is indeed serving them up, but then it seems to pass control onto each instance, using the page in the instance's docroot, if it exists. When I created an EAR archive, the only page I had in the docroot was index.cfm. If I add other pages to IIS's docroot, they show up fine, but the instance's pages always take precedence, even if I attempt to delete them (at which point the server returns a 404, though the page still exists in IIS's docroot).
Any ideas? I'm going to try using an empty docroot to create the initial EAR from, but I wonder if this is a symptom of incorrectly setting up the instances.
When I access pages on the IIS site, IIS is indeed serving them up, but then it seems to pass control onto each instance, using the page in the instance's docroot, if it exists. When I created an EAR archive, the only page I had in the docroot was index.cfm. If I add other pages to IIS's docroot, they show up fine, but the instance's pages always take precedence, even if I attempt to delete them (at which point the server returns a 404, though the page still exists in IIS's docroot).
Any ideas? I'm going to try using an empty docroot to create the initial EAR from, but I wonder if this is a symptom of incorrectly setting up the instances.
AdChoices