Re: Tomcat 9.0.16 Packaging Change (Extras)

[Stephen Hames]

Hi Mark,

-Dcom.sun.management.jmxremote.registry.ssl=false solved the problem.

Thanks for that.

Regards,
Stephen

On Wed, 4 Mar 2020 at 18:09, Mark Thomas  wrote:

> On 04/03/2020 06:45, Stephen Hames wrote:
> > Hi Mark,
> >
> > Apologies for the very late reply here.  I had to set the upgrade aside
> > temporarily...
> >
> > Steps to reproduce:
> >
> > server.xml snippet
> >
> >  > className="org.apache.catalina.mbeans.JmxRemoteLifecycleListener"
> > rmiRegistryPortPlatform="10001"
> > rmiServerPortPlatform="10002"
> > />
> >
> > java options:
> > -Dcom.sun.management.jmxremote.ssl=false
> > -Dcom.sun.management.jmxremote.authenticate=true
> > -Dcom.sun.management.jmxremote.password.file=../conf/jmxremote.password
> > -Dcom.sun.management.jmxremote.access.file=../conf/jmxremote.access
> >
> > When I try to connect with valid credentials using Jconsole, the error
> > observed is: non-JRMP server at remote endpoint
> >
> > If I add catalina-jmx-remote.jar from tomcat 9.0.14 to
> $CATALINA_BASE/lib,
> > and restart, I am able to connect without issue.
>
> The refactoring in 9.0.16 introduced an additional configuration
> requirement:
>
> -Dcom.sun.management.jmxremote.registry.ssl=false
>
> I'll get that added to the documentation.
>
> It is worth noting that with current JVMs there is no need for the
> JmxRemoteLifecycleListener at all. All of the configuration options it
> provides are now available via system properties. Details at:
>
>
> https://tomcat.apache.org/tomcat-9.0-doc/monitoring.html#Enabling_JMX_Remote
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

-- 


This message may
contain confidential and privileged information. If it 
has been sent to you in
error, please reply to advise the sender of the 
error and then immediately
delete this message.

Re: Tomcat 9.0.16 Packaging Change (Extras)

[Mark Thomas]

On 04/03/2020 06:45, Stephen Hames wrote:
> Hi Mark,
> 
> Apologies for the very late reply here.  I had to set the upgrade aside
> temporarily...
> 
> Steps to reproduce:
> 
> server.xml snippet
> 
>  className="org.apache.catalina.mbeans.JmxRemoteLifecycleListener"
> rmiRegistryPortPlatform="10001"
> rmiServerPortPlatform="10002"
> />
> 
> java options:
> -Dcom.sun.management.jmxremote.ssl=false
> -Dcom.sun.management.jmxremote.authenticate=true
> -Dcom.sun.management.jmxremote.password.file=../conf/jmxremote.password
> -Dcom.sun.management.jmxremote.access.file=../conf/jmxremote.access
> 
> When I try to connect with valid credentials using Jconsole, the error
> observed is: non-JRMP server at remote endpoint
> 
> If I add catalina-jmx-remote.jar from tomcat 9.0.14 to $CATALINA_BASE/lib,
> and restart, I am able to connect without issue.

The refactoring in 9.0.16 introduced an additional configuration
requirement:

-Dcom.sun.management.jmxremote.registry.ssl=false

I'll get that added to the documentation.

It is worth noting that with current JVMs there is no need for the
JmxRemoteLifecycleListener at all. All of the configuration options it
provides are now available via system properties. Details at:

https://tomcat.apache.org/tomcat-9.0-doc/monitoring.html#Enabling_JMX_Remote

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9.0.16 Packaging Change (Extras)

[Stephen Hames]

Hi Mark,

Apologies for the very late reply here.  I had to set the upgrade aside
temporarily...

Steps to reproduce:

server.xml snippet



java options:
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=../conf/jmxremote.password
-Dcom.sun.management.jmxremote.access.file=../conf/jmxremote.access

When I try to connect with valid credentials using Jconsole, the error
observed is: non-JRMP server at remote endpoint

If I add catalina-jmx-remote.jar from tomcat 9.0.14 to $CATALINA_BASE/lib,
and restart, I am able to connect without issue.

Worth noting: I am using 9.0.31.

Thanks.

Regards,

Stephen

On Tue, 10 Sep 2019 at 18:36, Mark Thomas  wrote:

> On 10/09/2019 09:41, Stephen Hames wrote:
> > Hi All,
> >
> > After Tomcat 9.0.14, the packaging available for download seems to have
> > changed in that the bin/extras directory has been removed.
> >
> > I am finding a bit of confusion on this.   We use catalina-jmx-remote.jar
> > and previously this was included in the extras directory.
> >
> > I saw an entry in the change log about merging the extras back into core.
> > But am unclear on expected the expected bahaviour now.
> >
> > Is this meant to be that it is no longer necessary to add these jars, or
> > that we need to source them via alternative means?
>
> It should be unnecessary to add the JARs as the classes should be in
> catalina.jar.
>
> > Using tomcat 9.0.22, if I add the catalina-jmx-remote.jar from 9.0.14, it
> > seems to work as normal, but if I don't add the jar, it does not.
>
> Can you share the steps you are following and the test you are using so
> we can see if we can reproduce this. I've checked the build and the
> classes are present in catalina.jar
>
> Thanks,
>
> Mark
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

-- 
_
Stephen Hames, Systems Architect & Release Manager
Singapore | +65 6403 5900
CloudPay 

-- 


This message may
contain confidential and privileged information. If it 
has been sent to you in
error, please reply to advise the sender of the 
error and then immediately
delete this message.

Re: Tomcat 9.0.16 Packaging Change (Extras)

[Mark Thomas]

On 10/09/2019 09:41, Stephen Hames wrote:
> Hi All,
> 
> After Tomcat 9.0.14, the packaging available for download seems to have
> changed in that the bin/extras directory has been removed.
> 
> I am finding a bit of confusion on this.   We use catalina-jmx-remote.jar
> and previously this was included in the extras directory.
> 
> I saw an entry in the change log about merging the extras back into core.
> But am unclear on expected the expected bahaviour now.
> 
> Is this meant to be that it is no longer necessary to add these jars, or
> that we need to source them via alternative means?

It should be unnecessary to add the JARs as the classes should be in
catalina.jar.

> Using tomcat 9.0.22, if I add the catalina-jmx-remote.jar from 9.0.14, it
> seems to work as normal, but if I don't add the jar, it does not.

Can you share the steps you are following and the test you are using so
we can see if we can reproduce this. I've checked the build and the
classes are present in catalina.jar

Thanks,

Mark


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 9.0.16 Packaging Change (Extras)

[Stephen Hames]

Hi All,

After Tomcat 9.0.14, the packaging available for download seems to have
changed in that the bin/extras directory has been removed.

I am finding a bit of confusion on this.   We use catalina-jmx-remote.jar
and previously this was included in the extras directory.

I saw an entry in the change log about merging the extras back into core.
But am unclear on expected the expected bahaviour now.

Is this meant to be that it is no longer necessary to add these jars, or
that we need to source them via alternative means?

Using tomcat 9.0.22, if I add the catalina-jmx-remote.jar from 9.0.14, it
seems to work as normal, but if I don't add the jar, it does not.

Thanks.
Regards,

Stephen

-- 


This message may
contain confidential and privileged information. If it 
has been sent to you in
error, please reply to advise the sender of the 
error and then immediately
delete this message.