You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by yo...@apache.org on 2006/01/10 19:41:30 UTC

svn commit: r367722 - in /tomcat/site/trunk: docs/faq/misc.html docs/faq/printer/misc.html xdocs-faq/misc.xml

Author: yoavs
Date: Tue Jan 10 10:41:29 2006
New Revision: 367722

URL: http://svn.apache.org/viewcvs?rev=367722&view=rev
Log:
Question I've gotten offline a few times.

Modified:
    tomcat/site/trunk/docs/faq/misc.html
    tomcat/site/trunk/docs/faq/printer/misc.html
    tomcat/site/trunk/xdocs-faq/misc.xml

Modified: tomcat/site/trunk/docs/faq/misc.html
URL: http://svn.apache.org/viewcvs/tomcat/site/trunk/docs/faq/misc.html?rev=367722&r1=367721&r2=367722&view=diff
==============================================================================
--- tomcat/site/trunk/docs/faq/misc.html (original)
+++ tomcat/site/trunk/docs/faq/misc.html Tue Jan 10 10:41:29 2006
@@ -174,6 +174,11 @@
         Help! Even though I run shutdown.sh (or shutdown.bat), Tomcat does not stop!
       </a>
     </li>
+    <li>
+      <a href="#adminJspErrors">
+        How do I debug JSP errors in the Admin web application?
+      </a>
+    </li>
   </ul>
 </p>
 
@@ -781,6 +786,39 @@
     Most likely, a non-daemon thread is running. JVM's do not shutdown until there are
     0 non-daemon threads. You will need to perform a thread dump [<tt>kill -3 pid</tt> for Unix or
     <tt>CTRL+Break</tt> for Windows] to determine the code which started the thread.
+  </div><br>
+
+  <b style="font-size: larger">
+      <a href="#adminJspErrors">
+        How do I debug JSP errors in the Admin web application?
+      </a>
+  </b>
+  <div style="padding-left : 20px;">
+    The admin web application that ships with Tomcat's binary distribution contains
+    pre-compiled JSPs and mappings for them.  In order to debug these JSPs, you need
+    to get the source versions, place them in the admin webapp directory, and disable
+    the JSPC-generated web.xml servlet mappings.  Here's how to do it from scratch
+    for a clean Tomcat installation:
+
+    <ol>
+      <li>Download Tomcat's base and admin webapp distributions (binaries), unzip to a directory
+          of your choice.  We'll use <code>c:\temp</code> in this example.</li>
+      <li>Edit c:\temp\server\webapps\admin\WEB-INF\web.xml to remove the JSPC-generated servlet mappings.
+          These are marked in the web.xml file with comments indicating the beginning and end of the JSPC
+          section.  You can simply comment out all these <code>servlet-mappping</code> elements.  Be careful not to 
+          comment out other servlet mappings such as the Struts dispatcher servlet.</li>
+      <li>Open c:\temp\server\webapps\admin\WEB-INF\lib\catalina-admin.jar with a zip file program like
+          WinZip.  Remove the files named *_jsp.class, as these are the compiled JSPs.  Do not remove
+          the other class files, the ones under the org/apache/ paths.</li>
+      <li>Download a Tomcat source distribution and unzip it to a directory of your choice, but not
+          the same directory that you used above.  We'll use <code>c:\src</code> in this example.</li>
+      <li>Copy everything <b>except</b> the WEB-INF/lib directory from c:\src\container\webapps\admin
+          to c:\temp\server\webapps\admin.  Now you will have the uncompiled admin webapp JSPs.</li>
+      <li>If you haven't already, define an admin user in <code>%CATALINA_HOME%\conf\tomcat-users.xml</code>.</li>
+      <li>Start Tomcat, navigate to http://localhost:8080 (or your actual server:port if you have modified
+          the default values), and access the admin web application.  It will run slower because Tomcat is
+          now compiling the JSPs on-demand the first time you access them, but should otherwise appear normal.</li>
+    </ol>
   </div><br>
 
 </blockquote></td></tr></table></td></tr><!--FOOTER SEPARATOR--><tr><td colspan="2"><hr size="1" noshade=""></td></tr><tr><td align="center" colspan="2"><!--Google Search Form: see Bugzilla 35788--><form action="http://www.google.com/search" name="searchForm" method="GET"><input value="UTF-8" name="ie" type="hidden"><input value="UTF-8" name="oe" type="hidden"><table bgcolor="#FFFFFF"><tr><td><a href="http://www.google.com/"><img align="absmiddle" alt="Google" border="0" src="http://www.google.com/logos/Logo_40wht.gif"></a></td><td><input value="" maxlength="255" size="25" name="q" type="text"><input value="http://jakarta.apache.org/tomcat/faq" name="domains" type="hidden"><input value="http://jakarta.apache.org/tomcat/faq" name="sitesearch" type="hidden"><input value="Google Search" name="btnG" type="submit"><br>

Modified: tomcat/site/trunk/docs/faq/printer/misc.html
URL: http://svn.apache.org/viewcvs/tomcat/site/trunk/docs/faq/printer/misc.html?rev=367722&r1=367721&r2=367722&view=diff
==============================================================================
--- tomcat/site/trunk/docs/faq/printer/misc.html (original)
+++ tomcat/site/trunk/docs/faq/printer/misc.html Tue Jan 10 10:41:29 2006
@@ -173,6 +173,11 @@
         Help! Even though I run shutdown.sh (or shutdown.bat), Tomcat does not stop!
       </a>
     </li>
+    <li>
+      <a href="#adminJspErrors">
+        How do I debug JSP errors in the Admin web application?
+      </a>
+    </li>
   </ul>
 </p>
 
@@ -780,6 +785,39 @@
     Most likely, a non-daemon thread is running. JVM's do not shutdown until there are
     0 non-daemon threads. You will need to perform a thread dump [<tt>kill -3 pid</tt> for Unix or
     <tt>CTRL+Break</tt> for Windows] to determine the code which started the thread.
+  </div><br>
+
+  <b style="font-size: larger">
+      <a href="#adminJspErrors">
+        How do I debug JSP errors in the Admin web application?
+      </a>
+  </b>
+  <div style="padding-left : 20px;">
+    The admin web application that ships with Tomcat's binary distribution contains
+    pre-compiled JSPs and mappings for them.  In order to debug these JSPs, you need
+    to get the source versions, place them in the admin webapp directory, and disable
+    the JSPC-generated web.xml servlet mappings.  Here's how to do it from scratch
+    for a clean Tomcat installation:
+
+    <ol>
+      <li>Download Tomcat's base and admin webapp distributions (binaries), unzip to a directory
+          of your choice.  We'll use <code>c:\temp</code> in this example.</li>
+      <li>Edit c:\temp\server\webapps\admin\WEB-INF\web.xml to remove the JSPC-generated servlet mappings.
+          These are marked in the web.xml file with comments indicating the beginning and end of the JSPC
+          section.  You can simply comment out all these <code>servlet-mappping</code> elements.  Be careful not to 
+          comment out other servlet mappings such as the Struts dispatcher servlet.</li>
+      <li>Open c:\temp\server\webapps\admin\WEB-INF\lib\catalina-admin.jar with a zip file program like
+          WinZip.  Remove the files named *_jsp.class, as these are the compiled JSPs.  Do not remove
+          the other class files, the ones under the org/apache/ paths.</li>
+      <li>Download a Tomcat source distribution and unzip it to a directory of your choice, but not
+          the same directory that you used above.  We'll use <code>c:\src</code> in this example.</li>
+      <li>Copy everything <b>except</b> the WEB-INF/lib directory from c:\src\container\webapps\admin
+          to c:\temp\server\webapps\admin.  Now you will have the uncompiled admin webapp JSPs.</li>
+      <li>If you haven't already, define an admin user in <code>%CATALINA_HOME%\conf\tomcat-users.xml</code>.</li>
+      <li>Start Tomcat, navigate to http://localhost:8080 (or your actual server:port if you have modified
+          the default values), and access the admin web application.  It will run slower because Tomcat is
+          now compiling the JSPs on-demand the first time you access them, but should otherwise appear normal.</li>
+    </ol>
   </div><br>
 
 </blockquote></td></tr></table></td></tr><!--FOOTER SEPARATOR--><tr><td colspan="2"><hr size="1" noshade=""></td></tr><!--PAGE FOOTER--><tr><td colspan="2"><div align="center"><font size="-1" color="#525D76"><em>

Modified: tomcat/site/trunk/xdocs-faq/misc.xml
URL: http://svn.apache.org/viewcvs/tomcat/site/trunk/xdocs-faq/misc.xml?rev=367722&r1=367721&r2=367722&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs-faq/misc.xml (original)
+++ tomcat/site/trunk/xdocs-faq/misc.xml Tue Jan 10 10:41:29 2006
@@ -187,6 +187,11 @@
         Help! Even though I run shutdown.sh (or shutdown.bat), Tomcat does not stop!
       </a>
     </li>
+    <li>
+      <a href="#adminJspErrors">
+        How do I debug JSP errors in the Admin web application?
+      </a>
+    </li>
   </ul>
 </p>
 
@@ -797,6 +802,39 @@
     Most likely, a non-daemon thread is running. JVM's do not shutdown until there are
     0 non-daemon threads. You will need to perform a thread dump [<tt>kill -3 pid</tt> for Unix or
     <tt>CTRL+Break</tt> for Windows] to determine the code which started the thread.
+  </answer>
+
+  <question>
+      <a href="#adminJspErrors">
+        How do I debug JSP errors in the Admin web application?
+      </a>
+  </question>
+  <answer>
+    The admin web application that ships with Tomcat's binary distribution contains
+    pre-compiled JSPs and mappings for them.  In order to debug these JSPs, you need
+    to get the source versions, place them in the admin webapp directory, and disable
+    the JSPC-generated web.xml servlet mappings.  Here's how to do it from scratch
+    for a clean Tomcat installation:
+
+    <ol>
+      <li>Download Tomcat's base and admin webapp distributions (binaries), unzip to a directory
+          of your choice.  We'll use <code>c:\temp</code> in this example.</li>
+      <li>Edit c:\temp\server\webapps\admin\WEB-INF\web.xml to remove the JSPC-generated servlet mappings.
+          These are marked in the web.xml file with comments indicating the beginning and end of the JSPC
+          section.  You can simply comment out all these <code>servlet-mappping</code> elements.  Be careful not to 
+          comment out other servlet mappings such as the Struts dispatcher servlet.</li>
+      <li>Open c:\temp\server\webapps\admin\WEB-INF\lib\catalina-admin.jar with a zip file program like
+          WinZip.  Remove the files named *_jsp.class, as these are the compiled JSPs.  Do not remove
+          the other class files, the ones under the org/apache/ paths.</li>
+      <li>Download a Tomcat source distribution and unzip it to a directory of your choice, but not
+          the same directory that you used above.  We'll use <code>c:\src</code> in this example.</li>
+      <li>Copy everything <b>except</b> the WEB-INF/lib directory from c:\src\container\webapps\admin
+          to c:\temp\server\webapps\admin.  Now you will have the uncompiled admin webapp JSPs.</li>
+      <li>If you haven't already, define an admin user in <code>%CATALINA_HOME%\conf\tomcat-users.xml</code>.</li>
+      <li>Start Tomcat, navigate to http://localhost:8080 (or your actual server:port if you have modified
+          the default values), and access the admin web application.  It will run slower because Tomcat is
+          now compiling the JSPs on-demand the first time you access them, but should otherwise appear normal.</li>
+    </ol>
   </answer>
 
 </section>



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