New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QueuedThreadPool not exposed on JMX #1718
Comments
We need more evidence.
is too vague, as Start with a barebone server and enable the JMX module. Can you see the |
After more thorough investigation it was determined that jetty wasn't the cause of the issue so I'm closing it. |
After further investigation, I've managed to pinpoint the issue with @wilkinsona. public static void main(String[] args) throws Exception {
Server server = new Server();
server.addBean(new MBeanContainer(ManagementFactory.getPlatformMBeanServer()));
ServerConnector connector = new ServerConnector(server);
connector.setPort(8080);
server.addConnector(connector);
server.start();
checkThreadPoolMBean();
Connector[] connectors = server.getConnectors();
server.setConnectors(null);
checkThreadPoolMBean();
server.setConnectors(connectors);
checkThreadPoolMBean();
}
private static void checkThreadPoolMBean() throws MalformedObjectNameException {
ObjectName queuedthreadpool = new ObjectName("org.eclipse.jetty.util.thread:type=queuedthreadpool,id=0");
try {
ManagementFactory.getPlatformMBeanServer().getMBeanInfo(queuedthreadpool);
System.out.println(queuedthreadpool + " was available");
}
catch(Exception ex) {
System.out.println(queuedthreadpool + " was not available");
}
} |
After upgrading from 9.4.5.v20170502 to 9.4.6.v20170531
MBean "org.eclipse.jetty.util.thread.queuedthreadpool" is no longer exposed on JMX althrough
other jetty JMX MBeans are. QueuedThreadPool is still being constructed.
Any thought about what it might be?
The text was updated successfully, but these errors were encountered: