This bug was fixed in the package tomcat6 - 6.0.20-8ubuntu1
---
tomcat6 (6.0.20-8ubuntu1) lucid; urgency=low
* Merge from Debian unstable. Remaining changes:
- debian/control, debian/rules: Do not use 3.0 (quilt) source format yet
* debian/tomcat6.default: Fix typos in JSVC
** Changed in: tomcat6 (Ubuntu)
Status: Triaged = In Progress
** Changed in: tomcat6 (Ubuntu)
Assignee: (unassigned) = Thierry Carrez (ttx)
--
tomcat6 needs debug start mode with jpda
https://bugs.launchpad.net/bugs/375493
You received this bug notification because you are a member
I'm adding the comment from Thag to /etc/default/tomcat6 in the Debian
packaging for Tomcat version 6.0.20-5
--
tomcat6 needs debug start mode with jpda
https://bugs.launchpad.net/bugs/375493
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
While I agree that it is possible to get the same behavior with the
addition of:
JAVA_OPTS=-Xdebug
-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n
-Djava.awt.headless=true -Xmx128M
to default/tomcat6, it is finding this information that is non-trivial.
A simple -d switch, or
Passing arbitrary Java options is supported through setting JAVA_OPTS in
/etc/default/tomcat6...
So if you set:
JAVA_OPTS=-Xdebug
-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n
-Djava.awt.headless=true -Xmx128M
You should get desired behavior.
We could modify the init script so
** Attachment added: Adds jpda debug option to tomcat6 init.d
http://launchpadlibrarian.net/26639186/tomcatinit.patch
--
tomcat6 needs debug start mode with jpda
https://bugs.launchpad.net/bugs/375493
You received this bug notification because you are a member of Ubuntu
Server Team, which is
