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

Joshua McKenzie commented on CASSANDRA-9902:
--------------------------------------------

bq. Did you add tools.jar to the classpath during compilation and execution?
I did - it gave me the following w/out the loadlibrary / java.library.path:
{noformat}
java.util.ServiceConfigurationError: com.sun.tools.attach.spi.AttachProvider: 
Provider sun.tools.attach.WindowsAttachProvider could not be instantiated
This error
com.sun.tools.attach.AttachNotSupportedException: no providers installed
{noformat}

bq. Did it print only "success!" without any errors, successfully attaching to 
the JVM and exiting?
It did. Updated to 8_u51 (to fix the ProgramData hard links) and it's still 
succeeding.

bq. You also need to run C* process and VMAttach both on an administrator shell
Yep - doing so (more from dumb luck from bcdedit / wmic changes and 
confirmation than anything), but confirmed again - and it's definitely working. 
Updated to 8_u51 and it's still succeeding.

bq. I wonder if there could also be some crazy conflict between JDK7 and JDK8, 
even though I purged all JVMs from my system with JavaRa, but maybe JDK8 leaves 
some uncleaned garbage. Would be nice to try reproducing on a clean system with 
only JDK7 ever installed.
I have a version of 7 on here and 8 both, so if it's that it might be a vestige 
of the environment hanging around on your side?

If I come up with anything other than JVM debugging as an idea I'll kick it 
your way.


> Windows dtest: invalid jolokia agent path
> -----------------------------------------
>
>                 Key: CASSANDRA-9902
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9902
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Joshua McKenzie
>            Assignee: Paulo Motta
>            Priority: Minor
>              Labels: Windows
>             Fix For: 2.2.x
>
>         Attachments: Not_Dep.jpg, VMAttach.java, win-crashlogs.zip
>
>
> A variety of tests are failing with similar:
> {noformat}
> 05:39:07 
> ======================================================================
> 05:39:07 ERROR: change_durable_writes_test 
> (configuration_test.TestConfiguration)
> 05:39:07 
> ----------------------------------------------------------------------
> 05:39:07 Traceback (most recent call last):
> 05:39:07   File 
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\configuration_test.py",
>  line 63, in change_durable_writes_test
> 05:39:07     durable_init_size = commitlog_size(durable_node)
> 05:39:07   File 
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\configuration_test.py",
>  line 127, in commitlog_size
> 05:39:07     with JolokiaAgent(node) as jmx:
> 05:39:07   File 
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\jmxutils.py", 
> line 188, in __enter__
> 05:39:07     self.start()
> 05:39:07   File 
> "D:\jenkins\workspace\cassandra-2.2_dtest_win32\cassandra-dtest\jmxutils.py", 
> line 80, in start
> 05:39:07     subprocess.check_output(args, stderr=subprocess.STDOUT)
> 05:39:07   File "D:\Python27\lib\subprocess.py", line 573, in check_output
> 05:39:07     raise CalledProcessError(retcode, cmd, output=output)
> 05:39:07 CalledProcessError: Command '('java', '-jar', 
> 'lib\\jolokia-jvm-1.2.3-agent.jar', '--host', '127.0.0.1', 'start', '3436')' 
> returned non-zero exit status 2
> 05:39:07 -------------------- >> begin captured logging << 
> --------------------
> 05:39:07 dtest: DEBUG: cluster ccm directory: d:\temp\dtest-kjkypw
> 05:39:07 --------------------- >> end captured logging << 
> ---------------------
> {noformat}
> Likely related:
> {noformat}
> 20:54:46 Failed to start jolokia agent (command was: java -jar 
> lib\jolokia-jvm-1.2.3-agent.jar --host 127.0.0.1 start 3436): Command 
> '('java', '-jar', 'lib\\jolokia-jvm-1.2.3-agent.jar', '--host', '127.0.0.1', 
> 'start', '3436')' returned non-zero exit status 2
> 20:54:46 Exit status was: 2
> 20:54:46 Output was: Error: Registry key 'Software\JavaSoft\Java Runtime 
> Environment'\CurrentVersion'
> 20:54:46 has value '1.8', but '1.7' is required.
> 20:54:46 Error: could not find java.dll
> 20:54:46 Error: Could not find Java SE Runtime Environment.
> {noformat}
> And at the top of jmxutils.py we see:
> {code}
> JOLOKIA_JAR = os.path.join('lib', 'jolokia-jvm-1.2.3-agent.jar')
> {code}
> So that's not going to work out too well on Windows.



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

Reply via email to