With Tomcat 5.5.12, individual RequestProcessors do not show up when I attempt to access them via JMX. Is this by design, or a new bug? If by design, documentation will need to be updated since the query below is used as an example in the javadocs and the remote administration documentation. The example below uses the Manager app's jmxproxy. Under Tomcat 5.5.12, when I access this URL: /manager/jmxproxy/?qry=*%3Atype%3DRequestProcessor%2C* I get the following result: ----------------- OK - Number of results: 0 ----------------- Under Tomcat 5.5.11, accessing the same URL: I get this result: ----------------- OK - Number of results: 2 Name: Catalina:type=RequestProcessor,worker=http-8680,name=HttpRequest0 modelerType: org.apache.coyote.RequestInfo virtualHost: xxxxxxxxxxxx bytesSent: 0 method: GET remoteAddr: xxxxxxxxxxxx requestBytesSent: 0 contentLength: -1 bytesReceived: 0 requestProcessingTime: 104 globalProcessor: org.apache.coyote.RequestGroupInfo@5660d6 protocol: HTTP/1.1 currentQueryString: qry=*%3Atype%3DRequestProcessor%2C* requestBytesReceived: 0 serverPort: 8680 stage: 3 requestCount: 0 maxTime: 0 processingTime: 0 currentUri: /manager/jmxproxy/ errorCount: 0 ------snip-------
It's a feature.
Then, as noted, the documentation will need to be updated to not suggest that one can see RequestProcessors using the method shown. These are two places I've seen the outdated docs: http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/catalina/ant/JMXQueryTask.html
(In reply to comment #2) > Then, as noted, the documentation will need to be updated to not suggest that > one can see RequestProcessors using the method shown. These are two places I've > seen the outdated docs: I was evidently sarcastic: this works perfectly fine, and the JMX objects are properly registered.
Sorry about not recognizing the sarcasm Remy, I'm new here. But I do believe this problem exists. It appears to only happen when NOT using APR. Can you verify that this problem does not exist on a fresh, no-APR Tomcat install before closing again? Not trying to be a pest - this is happening consistently on all of my Tomcat 5.5.12 instances that are non-APR. I just now realized that it still works fine on instances that use APR.
As I said, it works for me. Please do not reopen the report.
I have fixed this issue for 5.5.13. Thanks for reporting this.