Skip to main content
Participating Frequently
October 12, 2009
Question

Starting ColdFusion Multi-Server Instances - Correct Method

  • October 12, 2009
  • 2 replies
  • 1920 views

Can someone please provide me with the correct method of starting multi-server instances of ColdFusion from the command line?

I have been using:

/<jrun4 home>/bin/jrun -nohup -start cfusion  (for the cfusion instance)

/<jrun4 home>/bin/jrun -nohup -start <coldfusion instance 2>  (for a second instance of coldfusion)

etc.

I see however that when the second instance of coldfusion (<coldfusion instance 2>) is started from the ColdFusion Administrator (Enterprise Manager - Instance Manager), it appears as the following:

/<jrun4 home>/bin/jrun -nohup -start -childVM <coldfusion instance 2>

What is the purpose of the -childVM switch that appears to be used when starting the instance from the ColdFusion Administrator (Enterprise Manager - Instance Manager)?  Should it be used when manually starting the instance from the command line?

Is there an online reference for the jrun swithces to be used when starting ColdFusion instances?  I have not been able to find any.

Thank you in advance for your assistance.

    This topic has been closed for replies.

    2 replies

    November 9, 2009

    This is one are were you won't find too many good docs on.

    I have two servers running CentOS in a cluster, with each server running two CF 8.1 servers in a cluster on each server. So I have 4 CF prod servers.

    The problem you will find is that the admin server interface can stop/start a service, but it uses the same jvm.config file as with thich the admin server was started. I have searched a lot, but couldn't find a solution to start the servers from the admin console. So I start them vir the "service" option on the OS level.

    So I build a script were I can start each server with its own jvm.config file. Madness to allocate 1Gig of mem for the admin server just so that the other servers can get 1Gig as well.

    Here is my startup script:

    [root@clu1 logs]# cat /etc/init.d/coldfusion8multi

    #!/bin/sh

    # chkconfig: 345 90 14
    # description: starts the MultiServer cfusion instance


    if [ -f /etc/rc.common ]; then
    . /etc/rc.common
    fi

    #
    # Start ColdFusion 8 Multiserver
    #
    # Because this is a start up script, and will be run by root, we use a specific
    # user (the user who installed) to run ColdFusion

    CF_DIR="/opt/cfusion/clu1_man"
    RUNTIME_USER=""cfusion""

    su $RUNTIME_USER -c "$CF_DIR/bin/jrun -start cfusion >& $CF_DIR/logs/cfusion-event.log &"
    su $RUNTIME_USER -c "$CF_DIR/bin/jrun -config $CF_DIR/bin/jvm.config_clu1 -start clu1_01 >& $CF_DIR/logs/cfusion-event.log &"
    su $RUNTIME_USER -c "$CF_DIR/bin/jrun -config $CF_DIR/bin/jvm.config_clu2 -start clu1_02 >& $CF_DIR/logs/cfusion-event.log &"

    Hope it helps a bit.

    Inspiring
    October 12, 2009

    I'll start by saying I don't know for sure, but I would guess that it makes the CF instance start with its own JVM instance, rather than running in an existing JVM?

    Info on this is a bit thin on the ground... Google doesn't turn up much.

    --

    Adam