On Thu, Feb 4, 2021 at 2:26 PM Mark Thomas wrote:
>
> On 04/02/2021 08:08, Luis Rodríguez Fernández wrote:
> > Hello Suvendu,
> >
> > I've never used the
> > "org.apache.catalina.mbeans.JmxRemoteLifecycleListener", I would advise you
> > to continue using the JVM startup options for JMX [1]
>
>
On 04/02/2021 08:08, Luis Rodríguez Fernández wrote:
> Hello Suvendu,
>
> I've never used the
> "org.apache.catalina.mbeans.JmxRemoteLifecycleListener", I would advise you
> to continue using the JVM startup options for JMX [1]
+1. Ignore the JmxRemoteLifecycleListener and use the settings
Hello Suvendu,
I've never used the
"org.apache.catalina.mbeans.JmxRemoteLifecycleListener", I would advise you
to continue using the JVM startup options for JMX [1]
Martynas: the JPDA port is using to enable debugging in your java process
and be able to connect to it, e.g. via your favourite
Hi Martynas,
On Tue, Feb 2, 2021 at 5:04 PM Martynas Jusevičius
wrote:
>
> Not sure if related, but JPDA address config changed from -
> JPDA_ADDRESS=8000 on Tomcat 8 to - JPDA_ADDRESS=*:8000 on Tomcat 9
> (i.e. host needs to be included, or a wildcard).
>
Thanks for pointing that out but I
Not sure if related, but JPDA address config changed from -
JPDA_ADDRESS=8000 on Tomcat 8 to - JPDA_ADDRESS=*:8000 on Tomcat 9
(i.e. host needs to be included, or a wildcard).
On Tue, Feb 2, 2021 at 12:22 PM Suvendu Sekhar Mondal wrote:
>
> Hello Everyone,
>
> We recently migrated Tomcat from
Hello Everyone,
We recently migrated Tomcat from 7.0.55 to 9.0.39. Everything is
working as expected except accessing exposed MBeans via JMX clients
like jconsole/jvisualvm. While troubleshooting the issue, I enabled
debug logging for both of those tools and it is throwing following
error:
