Bug report #598 has just been filed.

You can view the report at the following URL:

   <http://znutar.cortexity.com/BugRatViewer/ShowReport/598>

REPORT #598 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: docbug
State: received
Priority: medium
Severity: serious
Confidence: public
Environment: 
   Release: 3.2
   JVM Release: 1.3
   Operating System: Linux
   OS Release: 2.2.12-20
   Platform: intel

Synopsis: 
mod_jk JkLogLevel (also tomcat.sh)

Description:
In jk_logger.h (mod_jk, tomcat version 3.2), the log
levels are defined as:

#define JK_LOG_DEBUG_VERB   "debug"
#define JK_LOG_INFO_VERB    "info"
#define JK_LOG_ERROR_VERB   "error"
#define JK_LOG_EMERG_VERB   "emerg"

The documentation and sample config files show a
level of "warn" for JkLogLevel. jk_util.c does not
find "warn" as a log level and sets the level to "debug".


Another minor quibble.  Add some "shifts" in bin/tomcat.sh
when the user specifies "-security". Otherwise
the script fails.

*** tomcat.sh.orig      Fri Dec 15 10:18:15 2000
--- tomcat.sh   Fri Dec 15 10:17:12 2000
***************
*** 122,127 ****
--- 122,128 ----
    shift 
    echo Using classpath: ${CLASSPATH}
    if [ "$1" = "-security" ] ; then
+     shift
      echo Starting with a SecurityManager
      $JAVACMD $TOMCAT_OPTS -Djava.security.manager 
-Djava.security.policy==${TOMCAT_HOME}/conf/tomcat.policy -Dtomcat.home=${TOMCAT_HOME} 
 org.apache.tomcat.startup.Tomcat "$@" &
    else
***************
*** 139,144 ****
--- 140,146 ----
    shift 
    echo Using classpath: ${CLASSPATH}
    if [ "$1" = "-security" ] ; then
+     shift
      echo Starting with a SecurityManager
      $JAVACMD $TOMCAT_OPTS -Djava.security.manager 
-Djava.security.policy==${TOMCAT_HOME}/conf/tomcat.policy -Dtomcat.home=${TOMCAT_HOME} 
org.apache.tomcat.startup.Tomcat "$@"
    else





Title: BugRat Report # 598

BugRat Report # 598

Project: Tomcat Release: 3.2
Category: Bug Report SubCategory: New Bug Report
Class: docbug State: received
Priority: medium Severity: serious
Confidence: public

Submitter: Conor MacNeill ( [EMAIL PROTECTED] )
Date Submitted: Dec 15 2000, 11:18:24 CST
Responsible: Z_Tomcat Alias ( [EMAIL PROTECTED] )

Synopsis:
mod_jk JkLogLevel (also tomcat.sh)
Environment: (jvm, os, osrel, platform)
1.3, Linux, 2.2.12-20, intel

Additional Environment Description:

Report Description:
In jk_logger.h (mod_jk, tomcat version 3.2), the log levels are defined as: #define JK_LOG_DEBUG_VERB "debug" #define JK_LOG_INFO_VERB "info" #define JK_LOG_ERROR_VERB "error" #define JK_LOG_EMERG_VERB "emerg" The documentation and sample config files show a level of "warn" for JkLogLevel. jk_util.c does not find "warn" as a log level and sets the level to "debug". Another minor quibble. Add some "shifts" in bin/tomcat.sh when the user specifies "-security". Otherwise the script fails. *** tomcat.sh.orig Fri Dec 15 10:18:15 2000 --- tomcat.sh Fri Dec 15 10:17:12 2000 *************** *** 122,127 **** --- 122,128 ---- shift echo Using classpath: ${CLASSPATH} if [ "$1" = "-security" ] ; then + shift echo Starting with a SecurityManager $JAVACMD $TOMCAT_OPTS -Djava.security.manager -Djava.security.policy==${TOMCAT_HOME}/conf/tomcat.policy -Dtomcat.home=${TOMCAT_HOME} org.apache.tomcat.startup.Tomcat "$@" & else *************** *** 139,144 **** --- 140,146 ---- shift echo Using classpath: ${CLASSPATH} if [ "$1" = "-security" ] ; then + shift echo Starting with a SecurityManager $JAVACMD $TOMCAT_OPTS -Djava.security.manager -Djava.security.policy==${TOMCAT_HOME}/conf/tomcat.policy -Dtomcat.home=${TOMCAT_HOME} org.apache.tomcat.startup.Tomcat "$@" else

Workaround:
null

View this report online...

Reply via email to