tomcat6 needs debug start mode with jpda
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Invalid
|
Undecided
|
Unassigned | ||
tomcat6 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Bits and pieces here from different sources but it all describes the prob.
tomcat 6:
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/
exec "$PRGDIR"
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/
DAEMON=
.
.
.
$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 fix is to apply the enclosed patch, or something like it.
Changed in rosetta: | |
status: | New → Invalid |
affects: | ubuntu → tomcat6 (Ubuntu) |
Why is this invalid?
Is it not desirable to be able to run tomcat with a debugger?
-Bruce
On Mon, May 11, 2009 at 11:31 PM, Данило Шеган <email address hidden> wrote:
> ** Changed in: rosetta /bugs.launchpad .net/bugs/ 375149
> Status: New => Invalid
>
> ** Also affects: ubuntu
> Importance: Undecided
> Status: New
>
> --
> tomcat6 needs debug start mode with jpda
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>