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/12/25 04:01:28 UTC

svn commit: r490104 - in /tomcat/container/tc5.5.x/webapps/docs: changelog.xml monitoring.xml

Author: yoavs
Date: Sun Dec 24 19:01:27 2006
New Revision: 490104

URL: http://svn.apache.org/viewvc?view=rev&rev=490104
Log:
Bugzilla 39055; documentation for JSR160 JMX monitoring with firewall

Modified:
    tomcat/container/tc5.5.x/webapps/docs/changelog.xml
    tomcat/container/tc5.5.x/webapps/docs/monitoring.xml

Modified: tomcat/container/tc5.5.x/webapps/docs/changelog.xml
URL: http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/changelog.xml?view=diff&rev=490104&r1=490103&r2=490104
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/changelog.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/changelog.xml Sun Dec 24 19:01:27 2006
@@ -160,6 +160,10 @@
         <bug>37977</bug>: adapt BUILDING.txt and net build.xml for SVN.  Patch by
         Christopher Sahnwaldt. (yoavs)
       </fix>
+      <update>
+        <bug>39055</bug>: Link to sample workaround code for using JSR160 JMX monitoring
+        with a local firewall.  Thanks to George Lindholm for the patch. (yoavs)
+      </update>
     </changelog>
   </subsection> 
   <subsection name="Coyote">

Modified: tomcat/container/tc5.5.x/webapps/docs/monitoring.xml
URL: http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/monitoring.xml?view=diff&rev=490104&r1=490103&r2=490104
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/monitoring.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/monitoring.xml Sun Dec 24 19:01:27 2006
@@ -62,7 +62,9 @@
     </li>
     </ol>
     <b>Note:</b>The JSR 160 JMX-Adaptor opens a second data protocol port. That is a problem
-    when you have installed a local firewall.<br/>
+    when you have installed a local firewall.  However, there is at least one possible
+    workaround: using a custom JMXConnectorServer.  The code for this is available
+    at <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=39055" title="Bugzila 39055">Bugzilla 39055</a>.
     </p>
     <p>Activate JMX MX4J Http Adaptor with Java 1.4:
     <ol>



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