----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files.  Don't make us guess your problem!!!
----------------------------------------------------------------


   Date: Thu, 3 Feb 2000 08:46:57 -0600 
   From: "Fisk, Thomas B." <[EMAIL PROTECTED]>

   Do you have a command line example of starting it
   manually?

   Thanks!

   Tom.

Here's the jserv startup script we use.  It's somewhat specific to our
deployment/development environment, but it can give you some ideas.

The script lets you switch between simulating production and
development modes with a "-p" flag, and uses the DEBUG environment
variable for getting informative backtraces in the logs.

Notes: oem.jar and platform.jar contain the classes specific to our
applications.  The $hier stuff is figuring out where the installed 
instance of the application lives. 

-billo

------------
#!/bin/sh
# $Id: jserv.start,v 1.8 2000/01/31 21:43:46 billo Exp $
# Start the jserv server for application for the $0 hierarchy.

JAVA=/usr/java1.2/bin/java

cd `dirname $0` || exit 1
hier=`cd .. && pwd`

base_hier=`basename $hier`

CLASSPATH=$hier/lib/ApacheJServ.jar:$hier/lib/jsdk.jar

# referenced by per-hierarchy jserv.properties
logfile=$hier/logs/jserv.log
touch $logfile
chmod a+rw $logfile

# referenced by common /l/jserv/jserv.conf
logfile2=/l/apache/logs/jserv.log
touch $logfile2
chmod a+rw $logfile2

outfile=/var/tmp/jserv.$base_hier.nohup

test=/bin/test

if $test "$1" = "-p"; then
  echo "Running production mode (no auto-reload of classes)."
  CLASSPATH=${CLASSPATH}:$hier/lib/oem.jar:$hier/lib/platform.jar
else
  # Make developer mode the default, since JServ crash is now fixed.
  echo "Running developer mode."
fi


if $test "$DEBUG" = "1"; then
  debug_flag=-Djava.compiler=NONE
else
  debug_flag=
fi

echo "$0: starting jserv; debug_flag=$debug_flag outfile=$outfile logfiles=$logfile 
$logfile2"
# note the java.compiler=NON flag is needed to get meaningful stack traces.
nohup $JAVA $debug_flag -classpath $CLASSPATH org.apache.jserv.JServ \
  $hier/conf/jserv.properties >$outfile 2>&1 &


--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to