Chris,

Don't know if this helps, but here goes.  We're using the same basic setup:
JRun4, Solaris 8, Apache 2.  We put our .config files into our
$JRUN_HOME/bin directory and start our JRun's up that way.  You might
consider starting jrun from $JRUN_HOME/bin:

ie:

JRUN_HOME is /opt/java/jrun4 (in our case)
$SERVER_NAME is jsm-messaging (here)

cd $JRUN_HOME/bin
sudo jrun -config jsm.messaging.config -nohup -start jsm-messaging >
../logs/jsm-messaging.out 2>&1

I know this works as we have a few servers we bring up at the same time in
development.  I think the key is to have the config file in the bin
directory and start things off from bin.

Hope that helps.

Erik
[EMAIL PROTECTED]/[EMAIL PROTECTED]

  -----Original Message-----
  From: Chris Boyce [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, July 28, 2004 2:10 PM
  To: JRun-Talk
  Subject: Could not invoke Java compiler

  We are using JRun4 on Solaris 8.

  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]

Reply via email to