Skip to main content
Anonymous
April 23, 2006
Answered

CF 7 Clustering Problem

  • April 23, 2006
  • 1 reply
  • 256 views
I'm trying to get clustering going on two Windows 2003 server with CF7.01. I was able to create the cluster with no problem. Both instances are using J2EE sessions. I was also able to the connect a third Windows 2003 (IIS6) server to the cluster with the wsconfig. However, the cluster won't failover.

I noticed that the jrun connector's jrunserver.store proxyserver is not being set. So I added in the appropriate info

Example:
Proxyservers=0.0.0.0:54001;0.0.0.1:54001

However when I restart IIS it clears it out back to Proxyservers=

I'm guessing that when he ISAPI filter starts up it contacts the server to which it is bootstraped and then recieves a list of the current available jrun proxyservers and then writes that list to the jrunservers.store. That would be fine if it would leave my manually entered proxyservers. But now it seems that I'm a little stuck.

Does anybody know if that is indeed how it works and why that would be happening. Is this a bug? Or I'm I just really missing something.

Any help would be much appreciated!

Thanks,
Matt
    This topic is closed to new replies. Start a new post to keep the conversation going.
    Correct answer
    Ok, I finally got the CF 7.01 clustering work. Both the local and remote instances in the cluster had the same name "clusterTest". So I deleted them both and created "clusterTest1" and "clusterTest2" and then added them into a newly created cluster. Next I manually made sure to set the jrun.xml proxyservice deactivated attribute to false and applied the jrun connecter update 5 hotfix, and it finally worked.

    1 reply

    Anonymous
    Correct answer
    April 23, 2006
    Ok, I finally got the CF 7.01 clustering work. Both the local and remote instances in the cluster had the same name "clusterTest". So I deleted them both and created "clusterTest1" and "clusterTest2" and then added them into a newly created cluster. Next I manually made sure to set the jrun.xml proxyservice deactivated attribute to false and applied the jrun connecter update 5 hotfix, and it finally worked.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices