OK, a couple of things:
You are using the JRun Launcher to start things:
---Launch the Launcher (Terminal)
------Start Admin server (Launcher)
---------- JMC (Browser)
------Start Default Server (Launcher)
I prefer to skip the launcher and start the admin server directly from the CLI (Terminal) with:
---Start Admin and Default Servers in Background (Terminal)
From a Terminal window, enter:
Then you get output similar to the following:
/Applications/JRun4/bin/jrun -start admin &
Once the Admin server has started up, the JMC is available through a browser by entering:
[TiBook:~] cfmx% /Applications/JRun4/bin/jrun -start admin default &
[TiBook:~] cfmx% Starting Macromedia JRun 4 (Build 54102), admin server
Server admin ready (startup time: 7 seconds)
Starting Macromedia JRun 4 (Build 54102), default server
Server default ready (startup time: 9 seconds)
into a browser.
If you display the Terminal window in the background, you can see the effect of any JMC activities.
This way of starting Jrun & servers eliminates some steps, and approximates what you would put in a startup script.