You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2013/07/12 09:41:54 UTC

[Bug 55253] New: catalina.sh: Move CATALINA_BASE to show path in 'ps -ef'

https://issues.apache.org/bugzilla/show_bug.cgi?id=55253

            Bug ID: 55253
           Summary: catalina.sh: Move CATALINA_BASE to show path in 'ps
                    -ef'
           Product: Tomcat 7
           Version: unspecified
          Hardware: Sun
                OS: SunOS
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: michael.renz@kordoba.de

Created attachment 30587
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=30587&action=edit
Patch

For monitoring reasons I always have to patch the catalina.sh to show up
CATALINA_BASE as first argument. 
Running Tomcat under SunOS, the process information with 'ps -ef' only shows
the first 79 characters of the process command. Per default, the
java.util.logging.config.file argument is shown first, but it gives no clue
about which instance of Tomcat the process is.
>From the path specified with CATALINA_BASE the process can be directly
identified for each instance. 
Example:

unpatched catalina.sh shows the following commandlines:
/softwarenet/tools/java7_17/bin/java -Djava.util.logging.config.file=/software/
/softwarenet/tools/java7_17/bin/java -Djava.util.logging.config.file=/software/
/softwarenet/tools/java7_17/bin/java -Djava.util.logging.config.file=/software/

Moving the CATALINA_BASE as first argument will show the path of the instance:
/softwarenet/tools/java7_17/bin/java -Dcatalina.base=/software/korweb/E0/ -Djav
/softwarenet/tools/java7_17/bin/java -Dcatalina.base=/software/korweb/E1/ -Djav
/softwarenet/tools/java7_17/bin/java -Dcatalina.base=/software/korweb/E2/ -Djav

I'm fully aware of that I could grab the PID of Tomcat to monitor it, but
unfortunately this is no option in my case. 
I'm pretty sure other users will also benefit from this change, not every OS
does show the full command line of each process.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 55253] catalina.sh: Move CATALINA_BASE to show path in 'ps -ef'

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55253

Michael Renz <mi...@kordoba.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|unspecified                 |7.0.37

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 55253] catalina.sh: Move CATALINA_BASE to show path in 'ps -ef'

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55253

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
While I have some sympathy with this problem, I am concerned that different
users are going to want different information in those 79 characters and that
will lead to conflicting requirements.

I don't recall that there is a good reason for LOGGING_CONFIG to be first. I'll
note that it does contain $CATALINA_BASE even though it is not fully visible
due to the length of the path to the java executable.

I think your best option is a workaround. Create a file called setenv.sh (or
edit the one you already have if you have one) and add the following:

LOGGING_CONFIG="-Dfoo.your.marker.here $LOGGING_CONFIG"

That will allow you to insert any text you like into the command line as early
as possible (i.e. just after the path to the java executable).

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org