Thanks for the reply Simon. It was behaving illogically when running through various tests which is why it wasn't making much sense to me. For example, if I stopped one particular instance, it would not end-up back in the cluster for quite a long time, but would eventually at random find it's way back in, however the other instances would behave as you said below.
I ended-up reinstalling the web server connectors and now it seems to be behaving as one would expect it to. Thanks, - Brandon On Apr 12, 2005 12:19 PM, Simon Horwith <[EMAIL PROTECTED]> wrote: > JRun has a cluster manager service. When a server is offline or stops > responding to requests, it's dropped from the cluster. If you attempt > to access something in the session scope and the server is unable to > access the session, it fails over to the other cluster member... but > only if you have fail over turned on (which you should). For the most > part, nothing much short of a crash, stop, or restart will remove an > instance from the cluster as far as I know. This is one of the reasons > you balance the instances. When it is restarted or started for the > first time, the cluster manager adds it to the cluster for you. > > ~Simon > -- ---------------------------------- http://devnulled.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:202493 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
