cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Ribeiro (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14173) JDK 8u162 breaks JMX integration
Date Sun, 21 Jan 2018 03:18:00 GMT


Edward Ribeiro commented on CASSANDRA-14173:

Yes [~mshuler], the first cut of this patch *requires* >= 1.8u161 :( 

OTOH, I have put together another version (see attachment) that compiles on both 152 and 161.
*_But_* *_I still need to verify if it doesn't break C* at runtime, though!_* (heh, changing
jdk back and forth messed up my IDE so it dragged me down)

AFAIK, 161 build has both the legacy and the new constructor (the one with _ObjectInputFilter_),
so it should work as intended, but I am not sure about 152 yet. _Please_, let me know what
you think, thanks.

> JDK 8u162 breaks JMX integration
> --------------------------------
>                 Key: CASSANDRA-14173
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sam Tunnicliffe
>            Priority: Critical
>             Fix For: 3.11.2
>         Attachments: cassandra-14173.2.patch, cassandra-14173.patch
> {\{org.apache.cassandra.utils.JMXServerUtils}} which is used to programatically configure
the JMX server and RMI registry (CASSANDRA-2967, CASSANDRA-10091) depends on some JDK internal
classes/interfaces. A change to one of these, introduced in Oracle JDK 1.8.0_162 is incompatible,
which means we cannot build using that JDK version. Upgrading the JVM on a node running 3.6+
will result in Cassandra being unable to start.
> {noformat}
> ERROR [main] 2018-01-18 07:33:18,804 - Exception encountered
during startup
> java.lang.AbstractMethodError: org.apache.cassandra.utils.JMXServerUtils$Exporter.exportObject(Ljava/rmi/Remote;ILjava/rmi/server/RMIClientSocketFactory;Ljava/rmi/server/RMIServerSocketFactory;Lsun/misc/ObjectInputFilter;)Ljava/rmi/Remote;
>         at
>         at
>         at
>         at org.apache.cassandra.utils.JMXServerUtils.createJMXServer(
>         at org.apache.cassandra.service.CassandraDaemon.maybeInitJmx(
>         at org.apache.cassandra.service.CassandraDaemon.setup(
>         at org.apache.cassandra.service.CassandraDaemon.activate(
>         at org.apache.cassandra.service.CassandraDaemon.main(
> This is also a problem for CASSANDRA-9608, as the internals are completely re-organised
in JDK9, so a more stable solution that can be applied to both JDK8 & JDK9 is required.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message