>box. The install went fine however I have a few questions that I hope
>someone can shed some light on:
>
> - after the install script is complete it states that you need to run
>/opt/jrun4/bin/jrun -start coldfusion
> ? does the admin server only need to be running when you want to
>login in to the Jrun Administrator? (I am assuming Yes)
Yes, only if you need the JMC.
>
> - when I start up CFMX, the console never fully completes and it seems
>to hang after "user AdminServlet: init" - CFMX is up and running fine,
>but if I exit this command (crtl-c) or exit the console, CFMX stops
>running.
> ? What could cause the start up process to not run properly
> ? Where can I look for logging, the /opt/jrun4/logs and
>/opt/servers/cfusion/cfusion-war/cfusion-ear/WEB-INF/cfusion/logs
>directories do not show any errors.
That's fine. The reason why that's happening (I'm almost positive) is
because the startup script is writing its startup debug messages to stdout
and not a log file. I like this feature because, in development, it allows
me to test certain MX features in my browser and then toggle over and see
any error messages that result from it. In particular, I've found that if
I'm having trouble connecting to a datasource, the debug out in the console
is more informative that what the MX Administrator is telling me (i.e., bad
username/password, TNS problem, etc.).
All you have to do is hit enter a couple of times and you'll get a command
prompt and you can continue on. Hitting Ctrl-C is the equivalent of killing
the process, which is why your MX instance dies.
Hope this helps?
Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
