On 08/12/17 19:29, Jesse Schulman wrote:
> Got it, that works and I was able to accomplish exactly what I needed,
> thank you!
>
> One side note, the name ended up being:
> "Tomcat:name=\"https-jsse-nio-8443\",type=ThreadPool"
>
> Which is a different order than your example so I am using the
>
Got it, that works and I was able to accomplish exactly what I needed,
thank you!
One side note, the name ended up being:
"Tomcat:name=\"https-jsse-nio-8443\",type=ThreadPool"
Which is a different order than your example so I am using the
ObjectName(String domain, Hashtable table)
On 06/12/17 18:32, Jesse Schulman wrote:
> For some reason there are no Catalina names from that MBean server:
>
> Registry.getRegistry(null, null).getMBeanServer().getDomains()
>
> yields
>
> JMImplementation, java.util.logging, java.lang, Tomcat, com.sun.management,
> null, java.nio
>
> and
For some reason there are no Catalina names from that MBean server:
Registry.getRegistry(null, null).getMBeanServer().getDomains()
yields
JMImplementation, java.util.logging, java.lang, Tomcat, com.sun.management,
null, java.nio
and
Registry.getRegistry(null,
On 06/12/17 00:17, Jesse Schulman wrote:
> Now that 8.5.24 is released with new support for runtime SNI/SSLHostConfig
> changes (thank you Mark!) I am trying to access the AbstractEndpoint from
> our application to call these 2 new methods:
>
> public void addSslHostConfig(SSLHostConfig
Now that 8.5.24 is released with new support for runtime SNI/SSLHostConfig
changes (thank you Mark!) I am trying to access the AbstractEndpoint from
our application to call these 2 new methods:
public void addSslHostConfig(SSLHostConfig sslHostConfig, boolean
replace)
public