Skip to main content
Sep 18, 2006 6:20 PM UTC
Question

JNDIContextManager discovered ClusterManager


Hello All,

I'm running CFMX 7 Enterprise (multi-inst opt) on a 64bit Windows 2003 Server
with IIS enabled to run 32bit apps.

I have two of these and have specifed them as cluster members using
JRun Admin. Also, Sticky Sessions OFF (un-checked) and Session Replication
ON (checked).

We're in production and everything works well and as expected.

However, I have noticed that it takes about 5-10 minutes for each cluster
member to discover each other.

Here's a snippet of the log entry...

...
09/18 08:18:34 info Deploying EJB "JRunSQLInvoker" from: file:/D:/JRun4/lib/jrun-comp.ear
09/18 08:25:05 info Clusterable service JNDIContextManager discovered ClusterManager on ...
...

This is the log entry for each cluster member.

Does anyone know how to get the disovery to happen sooner? Like immediately or
within one minute (provided the other cluster member is up and ready).

I have already tried the updater (CFMX 7,0,2,142559) and using CF Admin to
define the cluster and I find that it still takes between 5-10 minutes.

Any suggestions (reasonable or un-reasonable) are welcome.

Perhaps there's a .xml file indicating how often to look for new members?


thanks,
-newbie
    This topic is closed to new replies. Start a new post to keep the conversation going.

    1 reply

    Sep 18, 2006 7:00 PM UTC

    I guess it's always good to re-read the documentation.

    The answer is to specify the cluster member as a unicast peer.


    thanks,
    -newbie
    Translate