JRun 4 clusters and the jrunserver.store file

Here I'm reposting a recent reply to the CFGURU mailing list regarding usage of jrunserver.store when clustering JRun servers.

> You should note that the jrunserver.store file
> in the directories for the servers in a
> cluster (these directories I speak of are the ones beneath the
> "wsconfig" directory) contain a list of the proxy port
> numbers for all of the servers in a cluster.


The jrunserver.store file is more of a bootstrap to get the connector started. It doesn't necessarily have to contain a list of all cluster members and their proxy port. The webserver will connect to the first available server listed in the .store file and begin a dialog with it to get a complete list of cluster members and their proxy ports. Connector logging will show this. There is a misconception that the jrunserver.store must contain a list clustered servers and that adding a server's ip and proxy port to it is sufficient to cluster, but neither are true. Any manual modifications you make to it will be overwritten at runtime.

Below is a snippet from a recent connector log when using CFMX 6.1 U1 on JRun4 U4 with Apache 2 on Linux (the connector logging defaults to Apache error_log)

[More]

CFMX 6.1 Standard, multiple CPUs, and licensing

I'm reposting a CFTalk thread that I just responded to regarding a comment that CFMX 6.1 Standard (Professional) will not use more than one processor on a multi-proc machine. From what I have observed CFMX Standard will utilize multiple processors, and from my reading of the license agreement it is legal to use one licensed copy on a server having up to 8 CPUs.




> 1) Cold Fusion MX Professional (not Enterprise) will only use one CPU.
> If you want to take advantage of both CPU's on that box then you will need to use
> ColdFusion Enterprise.


That's not quite accurate. CFMX Standard (Professional) will use more than one CPU if available.

[More]