https://bz.apache.org/bugzilla/show_bug.cgi?id=64493
Bug ID: 64493
Summary: Regression: JMX beans for HTTPS connector changed
protocol with 9.0.35
Product: Tomcat 9
Version: 9.0.35
Hardware: PC
OS: Mac OS X 10.1
Status: NEW
Severity: normal
Priority: P2
Component: Connectors
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: -----
Using the following pseudo code:
{
try
{
MBeanServer server = MBeanServerFactory.createMBeanServer();
Set<ObjectName> protocolHandlers = server.queryNames(new
ObjectName("Catalina:type=Connector,*"), null);
for (ObjectName x: protocolHandlers)
{
String protocol = (String) server.getAttribute(x, "protocol");
System.out.println(x + " - " + protocol);
}
}
catch (Exception e)
{
}
}
Then under 9.0.30 we get:
Catalina:type=Connector,port=10180 - HTTP/1.1
Catalina:type=Connector,port=10443 - HTTP/1.1
Under 0.0.35 we get:
[15:02] Anton Goselink
Catalina:type=Connector,port=10180 - HTTP/1.1
Catalina:type=Connector,port=10443 - org.apache.coyote.http11.Http11NioProtocol
I believe that this is related to
https://github.com/apache/tomcat/commit/5e0dd5d91ca3b9eb85d79fca2b9ce9313d90083c
, since in the old situation, whenever the connector was Http11NioProtocol, it
would return "HTTP/1.1". in the new situation, when a ProtocolHandler is passed
in, we use the class name instead of "HTTP/1.1" for configuredProtocol. This
should probably get the name of the protocol being handled from the
ProtocolHandler.
In any case, this causes a breakage in our environment, as we rely on the
protocol being set to "HTTP*" for the JMX bean.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
