[jira] [Commented] (CASSANDRA-9608) Support Java 9

2017-05-30 Thread Paul Sandoz (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030429#comment-16030429
 ] 

Paul Sandoz commented on CASSANDRA-9608:


The JMX RMI connector was moved into it's own module, java.management.rmi. See:

  https://bugs.openjdk.java.net/browse/JDK-8173607

As a result the class com.sun.jmx.remote.internal.RMIExporter was moved to the 
package com.sun.jmx.remote.internal.rmi.

The Cassandra class org.apache.cassandra.utils.JMXServerUtils depends on 
RMIExporter.

In total JMXServerUtils depends on the following internal classes:

  com.sun.jmx.remote.internal.RMIExporter
  com.sun.jmx.remote.security.JMXPluggableAuthenticator
  sun.rmi.registry.RegistryImpl
  sun.rmi.server.UnicastServerRef2


> Support Java 9
> --
>
> Key: CASSANDRA-9608
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9608
> Project: Cassandra
>  Issue Type: Task
>Reporter: Robert Stupp
>Priority: Minor
>
> This ticket is intended to group all issues found to support Java 9 in the 
> future.
> From what I've found out so far:
> * Maven dependency {{com.sun:tools:jar:0}} via cobertura cannot be resolved. 
> It can be easily solved using this patch:
> {code}
> - artifactId="cobertura"/>
> + artifactId="cobertura">
> +  
> +
> {code}
> * Another issue is that {{sun.misc.Unsafe}} no longer contains the methods 
> {{monitorEnter}} + {{monitorExit}}. These methods are used by 
> {{o.a.c.utils.concurrent.Locks}} which is only used by 
> {{o.a.c.db.AtomicBTreeColumns}}.
> I don't mind to start working on this yet since Java 9 is in a too early 
> development phase.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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



[jira] [Commented] (CASSANDRA-9608) Support Java 9

2016-08-10 Thread Paul Sandoz (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415962#comment-15415962
 ] 

Paul Sandoz commented on CASSANDRA-9608:


-Xloggc is deprecated, as a workaround use -Xlog:gc instead, that should not 
result in a SEGV, but it will not create the file and you may observe:

$java -Xlog:gc:a/log.txt A
[0.004s][error][logging] Error opening log file 'a/log.txt': No such file or 
directory
...

> Support Java 9
> --
>
> Key: CASSANDRA-9608
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9608
> Project: Cassandra
>  Issue Type: Task
>Reporter: Robert Stupp
>Priority: Minor
>
> This ticket is intended to group all issues found to support Java 9 in the 
> future.
> From what I've found out so far:
> * Maven dependency {{com.sun:tools:jar:0}} via cobertura cannot be resolved. 
> It can be easily solved using this patch:
> {code}
> - artifactId="cobertura"/>
> + artifactId="cobertura">
> +  
> +
> {code}
> * Another issue is that {{sun.misc.Unsafe}} no longer contains the methods 
> {{monitorEnter}} + {{monitorExit}}. These methods are used by 
> {{o.a.c.utils.concurrent.Locks}} which is only used by 
> {{o.a.c.db.AtomicBTreeColumns}}.
> I don't mind to start working on this yet since Java 9 is in a too early 
> development phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CASSANDRA-9608) Support Java 9

2016-06-10 Thread Paul Sandoz (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325049#comment-15325049
 ] 

Paul Sandoz commented on CASSANDRA-9608:


Paul Sandoz here from the Oracle Java team.

The sooner the better in terms of feedback/evaluation if at all possible since 
the Java 9 release schedule has a long soak time and the closer we get to GA 
the harder it is to make changes.

If there is any evaluation that can be performed sooner that would be very 
helpful and gratefully received, otherwise if feedback arrives in 8 or 9 months 
it may be too late if it is determined Cassandra cannot function effectively 
e.g. without such Unsafe methods.

In general we have been releasing regular Java 9 EA builds and reaching out and 
engaging with communities to test Java 9 (e.g. Apache Lucene is a good 
example). This helps us (the Java team) improve the release and find issues 
earlier so we can fix them or provide guidance ahead of time so there is a 
smoother upgrade path for the many Java developers.

> Support Java 9
> --
>
> Key: CASSANDRA-9608
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9608
> Project: Cassandra
>  Issue Type: Task
>Reporter: Robert Stupp
>Priority: Minor
>
> This ticket is intended to group all issues found to support Java 9 in the 
> future.
> From what I've found out so far:
> * Maven dependency {{com.sun:tools:jar:0}} via cobertura cannot be resolved. 
> It can be easily solved using this patch:
> {code}
> - artifactId="cobertura"/>
> + artifactId="cobertura">
> +  
> +
> {code}
> * Another issue is that {{sun.misc.Unsafe}} no longer contains the methods 
> {{monitorEnter}} + {{monitorExit}}. These methods are used by 
> {{o.a.c.utils.concurrent.Locks}} which is only used by 
> {{o.a.c.db.AtomicBTreeColumns}}.
> I don't mind to start working on this yet since Java 9 is in a too early 
> development phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)