DO NOT REPLY [Bug 33027] - catalina.sh - give shutdown some time before killing with -force option
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33027. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33027 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2005-02-01 21:35 --- -1, this is too specific a feature for you, have fun with your own custom scripts. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 33027] - catalina.sh - give shutdown some time before killing with -force option
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33027. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33027 --- Additional Comments From [EMAIL PROTECTED] 2005-01-12 18:56 --- The brackets for kill -0 are wrong, it's supposed to be if kill -0 `cat $CATALINA_PID` 2/dev/null; then ... fi Sorry - Christian -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 33027] - catalina.sh - give shutdown some time before killing with -force option
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33027. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33027 [EMAIL PROTECTED] changed: What|Removed |Added Severity|normal |enhancement -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29133] - catalina.sh stop -force doesn't work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29133. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29133 catalina.sh stop -force doesn't work [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-05-26 19:47 --- Fixed as suggested. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27380] - catalina.sh and startup.sh are not executable upon install
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27380. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27380 catalina.sh and startup.sh are not executable upon install [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-03-02 22:53 --- This is ok if you get the .tar.gz distribution. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20029] - catalina.sh - command stop -force not working
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20029. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20029 catalina.sh - command stop -force not working [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Component|Unknown |Native:Integration Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-09-02 12:26 --- Since I don't see how this can work well in all situations (except if we add a new command which would just kill Tomcat - not that good an idea IMO), I'm willing to make the change. We'll see how it works in practice ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20029] - catalina.sh - command stop -force not working
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20029. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20029 catalina.sh - command stop -force not working --- Additional Comments From [EMAIL PROTECTED] 2003-06-27 22:39 --- But removing the exec will make shutdown.sh wait until shutdown is complete, not return right away like now. For a large system, this can easily be several seconds (or more, depending on custom shutdown code in user webapps). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13965] - Catalina.sh correction request for Tru64 Unix
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13965.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13965
Catalina.sh correction request for Tru64 Unix
[EMAIL PROTECTED] changed:
What|Removed |Added
Component|Jasper 2|Catalina
Keywords||PatchAvailable
Summary|Need a way to globally |Catalina.sh correction
|configure Jasper options|request for Tru64 Unix
--- Additional Comments From [EMAIL PROTECTED] 2002-10-25 04:51 ---
Dear All,
I have extract jakarta-tomcat-4.1.12 on my Tru64 Unix v 5.1 (DEC Alpha).
The
problem is catalina.sh couldn't work.
./catalina.sh start
Using CATALINA_BASE:
/var/jakarta-tomcat-4.1.12
Using CATALINA_HOME: /var/jakarta-tomcat-4.1.12
Using
CATALINA_TMPDIR: /var/jakarta-tomcat-4.1.12/temp
Using JAVA_HOME:
/usr/opt/java140
catalina.out:
usage: java
org.apache.catalina.startup.Catalina [ -config {pathname} ] [ -debug ] [ -nonaming ] {
start | stop
}
But Tomcat can start if i run directly using the following
command:
/usr/opt/java140/bin/java -Djava.endorsed.dirs=/var/jakarta-tomcat-
4.1.12/bin:/var/jakarta-tomcat-4.1.12/common/endorsed -classpath
/usr/opt/java140/lib/tools.jar:/var/jakarta-tomcat-4.1.12/bin/bootstrap.jar -
Dcatalina.base=/var/jakarta-tomcat-4.1.12 -Dcatalina.home=/var/jakarta-tomcat-4.1.12 -
Djava.io.tmpdir=/var/jakarta-tomcat-4.1.12/temp org.apache.catalina.startup.Bootstrap
start
My Questions:
How to fix the catalina.sh?
This problem occur when i run on my
DEC Tru64 Unix.
TIA,
Yon
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 7827] - catalina.sh can't work in Cygwin environment
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7827. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7827 catalina.sh can't work in Cygwin environment [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX | --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 18:40 --- I understand the above tons of hacks argument, however, if that is the case then everything in the scripts referencing cygwin should be removed so it does not appear to support cygwin. I just spent an hour searching the web because I thought There must be something wrong with my environment because catalina.sh obviously should work under cygwin because it does cygwin checks in several places. It makes no sense to have cygwin checks in this script if it's broken in cygwin. It would actually be easier to just apply the two line change noted in the original entry of this bug report than to remove all cygwin references. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8719] - catalina.sh bug
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8719. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8719 catalina.sh bug [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WONTFIX -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 8719] - catalina.sh bug
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8719. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8719 catalina.sh bug [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX | --- Additional Comments From [EMAIL PROTECTED] 2002-05-03 16:21 --- Look, if you don't want to support Cygwin, remove the code entirely and note it as officially no longer supported. I have no problem with that. But I don't think it's terribly cool to put partial support in, cause people to waste hours of time wondering why something won't work when it isn't even supposed to work, then complain about how tired you are of Cygwin when you get a bug report. Just remove it instead. You'll have less code to maintain. Alternatively, you could spend 5 seconds doing a simple cut paste of the fix I already provided. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7827] - catalina.sh can't work in Cygwin environment
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7827. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7827 catalina.sh can't work in Cygwin environment [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2002-04-08 09:56 --- I find it counter productive to put tons of hacks in the Unix scripts just to support Cygwin. The .bat works perfectly well when run from Cygwin, so please use it to run Tomcat. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
bug in catalina.sh
Hello,
I noticed a bug in catalina.sh that make some of us have problem starting
tomcat. The common error is that a message
usage: java org.apache.catalina.startup.Catalina [ -config {pathname} ] [
-debug ] [ -nonaming ] { start | stop }
is printed in $CATALINA_HOME/logs/catalina.out
I began to look at this problem and I finally found the bug:
The problem is that at every line where catalina is started ($_RUNJAVA
...), command line arguments that are passed to the catalina.sh script are
passed using $_RUNJAVA javaargs catalinaClass $@ command (quotes
included) ... The problem : When only one argument is passed to the VM , in
Catalina.main(String args[]), args are { , command } and not {
command } ... ( starting catalina.sh start means starting java
javaargs class start, not java javaargs class start) ...
big problem in Catalina.arguments(String[] args) where the argument
(empty string) is not recognised and issues an error on stdout...
I think the problem could be corrected by replacing all $@ (with quotes)
occurence by $@ (without quotes) in catalina.sh
Are you ok with this or am I missing something??
Fabien Nisol
java Developer/Analyst consultant
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: bug in catalina.sh
Fabien,
Since the $@ is necessary to preserve quoting of arguments with spaces in
them, changing it to $@ is not a really good solution. First off, which Unix
platform are you using? I know that the $@ works on Solaris and Linux and Mac
OS X.
Also, have you tried using ${@}? Most platfroms don't require the curly braces
to preserve quoting, but maybe yours does.
Patrick
Fabien Nisol wrote:
Hello,
I noticed a bug in catalina.sh that make some of us have problem starting
tomcat. The common error is that a message
usage: java org.apache.catalina.startup.Catalina [ -config {pathname} ] [
-debug ] [ -nonaming ] { start | stop }
is printed in $CATALINA_HOME/logs/catalina.out
I began to look at this problem and I finally found the bug:
The problem is that at every line where catalina is started ($_RUNJAVA
...), command line arguments that are passed to the catalina.sh script are
passed using $_RUNJAVA javaargs catalinaClass $@ command (quotes
included) ... The problem : When only one argument is passed to the VM , in
Catalina.main(String args[]), args are { , command } and not {
command } ... ( starting catalina.sh start means starting java
javaargs class start, not java javaargs class start) ...
big problem in Catalina.arguments(String[] args) where the argument
(empty string) is not recognised and issues an error on stdout...
I think the problem could be corrected by replacing all $@ (with quotes)
occurence by $@ (without quotes) in catalina.sh
Are you ok with this or am I missing something??
Fabien Nisol
java Developer/Analyst consultant
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
_
Patrick Luby Email: [EMAIL PROTECTED]
Sun Microsystems Phone: 408-276-7471
901 San Antonio Road, USCA14-303
Palo Alto, CA 94303-4900
_
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5104] - catalina.sh fails to start tomcat on Tru64
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5104. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5104 catalina.sh fails to start tomcat on Tru64 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2002-01-24 15:34 --- Michael, thanks for the explanation (and workaround). I don't think it would be a good idea to put a workaround in the script itself for what is a bug in Tru64. You may want to try the updated scripts from the HEAD branch (they're also in the recent nightly builds) to see if you have more success with them. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5104] - catalina.sh fails to start tomcat on Tru64
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5104. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5104 catalina.sh fails to start tomcat on Tru64 --- Additional Comments From [EMAIL PROTECTED] 2002-01-13 05:03 --- The reason for this is the incorrect interpretation of the $@ construct by the Tru-64 Bourne Shell. If you change the first line of each .sh file in the tomcat bin directory to be #!/bin/ksh i.e. use the Korn shell for the file instead of the /bin/sh that is there now, it works correctly. Experimenting with $@ on different OS (Solaris, AIX etc) shows Tru-64 to be incorrect. Regards Mike Doyle Ubiquity Software Corporation -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
