Whenever we try to bring up a second JRun server instance, the first one
starts experiencing jikesw compiler errors:
"Could not invoke Java compiler, please make sure jikesw is in
/tools/jrun4/bin or put a JDK bin directory in your path"
Pages that were already compiled when the second instance was started
continue to load, but any newly (non-compiled) accessed pages will fail
with the above.
This doesn't seem to be a PATH problem, since things work GREAT until
the second server is brought up. I put /tools/jrun4/bin in jrun user's
PATH anyway, with no help.
We are using the following ksh syntax (in a wrapper script) to start our
servers:
...
cd /tools/jrun4/servers/${SERVER}
su jrun -c "/tools/jrun4/bin/jrun -config ./${SERVER}.config -nohup
-start ${SERVER} 1>>${STANDARD_OUT_LOG} 2>>${STANDARD_ERR_LOG}"
...
PS. It appears that ANY additional server instance will cause this,
including the admin server! Is it a file contention problem? Why would
jikesw suddenly become unavailable? I can even see some compilation
occurring (in the jsp dir) before it croaks, so it seems to be making it
part-way through before dying.
We are in the middle of a large-scale installation, so any help is
greatly appreciated.
thanks
--
Chris Boyce
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
