[
https://issues.apache.org/jira/browse/CASSANDRA-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647967#comment-14647967
]
Paulo Motta commented on CASSANDRA-9902:
----------------------------------------
This morning I tried a few more approaches, without success:
- Upgrading jolokia to latest version 1.3.1
- Disabled DEP via bcdedit
- Zulu OpenJDK
- Tried with 32bit and 64 bit JVMs
- jdks 7u76, 7u79, 7u80
I wonder why VMAttach.java didn't crash the C* JVM on your system and you had
to add the System.loadlibrary("attach")... Did you add tools.jar to the
classpath during compilation and execution? Did it print only "success!"
without any errors, successfully attaching to the JVM and exiting?
You also need to run C* process and VMAttach both on an administrator shell,
otherwise the process is not able to write the PID to
$TEMP\hsperfdata_$USERNAME due to some [crazy permission
issue|https://blogs.oracle.com/lmalventosa/entry/jconsole_local_process_list_on].
This directory is used by the attaching tools to check if a pid is valid. If
even with those details you're able to attach successfully with VMAttach, we
may be able to tweak jolokia to load that "attach" library and see if it works.
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|http://sourceforge.net/projects/javara/], but maybe JDK8 leaves some
uncleaned garbage. Would be nice to try reproducing on a clean system with only
JDK7 ever installed.
Will try a few more sane alternatives before diving into JVM debugging, but
we're surely running out of them.
> 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)
