[Bug 375493] [NEW] tomcat6 needs debug start mode with jpda

Thag bruce.edge at gmail.com
Tue May 12 16:06:06 BST 2009


Public bug reported:

Binary package hint: tomcat6

I had filed this in the wrong place, but I don't see any links to it
now. Apologies if it's a dup.

Bits and pieces pasted here from different sources but it all describes
the prob.

tomcat 6 in jaunty:
 dpkg -l | grep tomcat6
ii  libtomcat6-java                          6.0.18-0ubuntu6                          Servlet and JSP engine -- core libraries
ii  tomcat6                                  6.0.18-0ubuntu6                          Servlet and JSP engine
ii  tomcat6-admin                            6.0.18-0ubuntu6                          Servlet and JSP engine -- admin web applications
ii  tomcat6-common                           6.0.18-0ubuntu6                          Servlet and JSP engine -- common files
ii  tomcat6-user                             6.0.18-0ubuntu6                          Servlet and JSP engine -- tools to create user instances

I've installed the stock tomcat6 package on Intrepid, and I want to
configure it for remote JPDA debugging (listening on port 8000) for
debugging a webapp from eclipse. The normal way to do this is to edit
/usr/share/tomcat6/bin/startup.sh so it starts in debug mode:

exec "$PRGDIR"/"$EXECUTABLE" jpda start "$@"

However, the Ubuntu system startup script doesn't seem to follow the
normal tomcat6 startup procedure. /etc/init.d/tomcat6 runs /usr/bin/jsvc
instead of executing the normal startup scripts in
/usr/share/tomcat6/bin:

DAEMON=/usr/bin/jsvc
.
.
.
$DAEMON -user "$TOMCAT6_USER" -cp "$JSVC_CLASSPATH" \
-outfile SYSLOG -errfile SYSLOG \
-pidfile "$CATALINA_PID" $JAVA_OPTS "$BOOTSTRAP_CLASS"

How should I configure it to start the debugger?


The attached patch is crude way of accomplishing this. I'm sure there are better ways.

** Affects: tomcat6 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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 to tomcat6 in ubuntu.



More information about the Ubuntu-server-bugs mailing list