Douglas Knudsen wrote:
yes, this is a common PITA I run into. You didn't mention the type of
cluster you have setup, J2EE software cluster or a HW cluster. In
either case you have to make sure you can update/init your application
scoped stuff on EACH member of the cluster. I use J2EE clusters here
and I had to enable the internal JRun server so that I can access each
instance indiviually.
DK
I believe, we have a hardware cluster with a load balancer. I also know
vmware is involved from time to time. It's totally out of my control and
by my account the configuration seems to be a bit of a moving target. :/
By enabling the internal jrun server do you mean for example:
You have Apache serving handling all the instances on example.com for
the outside world.
then
Jrunserver in instance 1 is on example.com:8500
and
Jrunserver in instance 2 is on example.com:8501
That seems like an easier setup to deal with than just hitting the url
until I hit the instance i want. :)
--jeff
You are subscribed to cfcdev. To unsubscribe, please follow the instructions at
http://www.cfczone.org/listserv.cfm
CFCDev is supported by:
Katapult Media, Inc.
We are cool code geeks looking for fun projects to rock!
www.katapultmedia.com
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
