https://bz.apache.org/bugzilla/show_bug.cgi?id=66617
Bug ID: 66617
Summary: Developing wiki page: "How do I configure Tomcat to
support remote debugging?" does not cover distributed
shell scripts
Product: Tomcat 10
Version: 10.1.9
Hardware: All
OS: All
Status: NEW
Severity: trivial
Priority: P2
Component: Documentation
Assignee: dev@tomcat.apache.org
Reporter: chea...@gmail.com
Target Milestone: ------
The "How do I configure Tomcat to support remote debugging?" section of the
Tomcat Developing FAQ at
https://cwiki.apache.org/confluence/display/TOMCAT/Developing?show-miniview#Developing-Debugging
contains the following item:
> If you are using shell scripts to start Tomcat, start it with the following
> command:
> catalina jpda start
> [...]
This case visibly refers to *custom* shell scripts. Unfortunately, employees in
my organization appear to have (pretty much) followed that advice even though
we are using vendor-provided shell scripts (those shipped by Tomcat), which
means we effectively modified code that doesn't belong to us (a Bad Idea™).
Colleagues modified the last line of startup.sh adding "jpda", meaning our
changes are lost at least every time the Tomcat package is upgraded:
https://github.com/apache/tomcat/blob/483c3d0adde00a5c6569bd75b2901dc6786d1663/bin/startup.sh#L60
Considering that our case is surely far from rare, it would be important to:
1. at least indicate in the existing item that it treats *custom* shell scripts
only
2. ideally, add an item covering the case of official (distributed) shell
scripts
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
