[jira] [Commented] (CASSANDRA-9902) Windows dtest: invalid jolokia agent path
[
https://issues.apache.org/jira/browse/CASSANDRA-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649675#comment-14649675
]
Carl Yeksigian commented on CASSANDRA-9902:
---
I'm not actually sure what that last test is supposed to be for; [~mambocab] do
you remember what that part of the test is for? I think we probably want to
write to the table, check that the size is the same, then write again and
ensure that the commitlog increases in size.
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)
[jira] [Commented] (CASSANDRA-9902) Windows dtest: invalid jolokia agent path
[
https://issues.apache.org/jira/browse/CASSANDRA-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649694#comment-14649694
]
Jim Witschey commented on CASSANDRA-9902:
-
[~carlyeks] Sorry, which test?
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)
[jira] [Commented] (CASSANDRA-9902) Windows dtest: invalid jolokia agent path
[
https://issues.apache.org/jira/browse/CASSANDRA-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649702#comment-14649702
]
Carl Yeksigian commented on CASSANDRA-9902:
---
This
[dtest|https://github.com/riptano/cassandra-dtest/commit/ce417ff9f74305260ca1fd75b8f4e2296a865135],
which was related to CASSANDRA-9560.
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)
[jira] [Commented] (CASSANDRA-9902) Windows dtest: invalid jolokia agent path
[
https://issues.apache.org/jira/browse/CASSANDRA-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649779#comment-14649779
]
Joshua McKenzie commented on CASSANDRA-9902:
Well, this is officially strike 1 against ConEmu for me.
Tests look good w/v3 when I run it locally via command-prompt and code looks
good to me. You'll want to open a PR to the github [dtest
repo|https://github.com/riptano/cassandra-dtest] and get a review from the
owners over there.
Along with that, could we get confirmation that this re-jiggering of .jar / cp
for jolokia works well on linux as well [~philipthompson]? I don't have my
linux VM handy atm else I'd do so.
Great find on this and excellent detective work!
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)
[jira] [Commented] (CASSANDRA-9902) Windows dtest: invalid jolokia agent path
[
https://issues.apache.org/jira/browse/CASSANDRA-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649796#comment-14649796
]
Joshua McKenzie commented on CASSANDRA-9902:
On a side note, it looks like it's
[ConEmuHk|https://code.google.com/p/conemu-maximus5/wiki/ConEmuFAQ#Q._What_is_the_purpose_of_ConEmuHk_.dll_(_ConEmuHk64_.dll)?]
that's the culprit. If you uncheck the Inject ConEmuHk option in ConEmu the
tests pass in ConEmu.
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)
[jira] [Commented] (CASSANDRA-9902) Windows dtest: invalid jolokia agent path
[
https://issues.apache.org/jira/browse/CASSANDRA-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649719#comment-14649719
]
Paulo Motta commented on CASSANDRA-9902:
to make the context clearer, the
{{TestConfiguration.change_durable_writes_test}} was failing because of the
following assertion near the end of the test:
{noformat}
self.assertGreater(commitlog_size(node), init_size, msg='ALTER KEYSPACE was not
respected')
{noformat}
because the highlighted part from the test description was actually missing
from the test:
{noformat}
- using ALTER KEYSPACE to set its DURABLE_WRITES option to true,
***writing a dataset to this keyspace that is known to trigger a
commitlog fsync***
- asserting that the commitlog has grown in size since the data was
written.
{noformat}
So I basically add the following missing line before the assertion to make the
test pass (in this
[commit|https://github.com/pauloricardomg/cassandra-dtest/commit/dfca2e8918b89bc9b88a2ac4a950699d7a99baaa]):
{noformat}
write_to_trigger_fsync(session, 'ks', 'tab')
{noformat}
Does this seems OK?
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)
[jira] [Commented] (CASSANDRA-9902) Windows dtest: invalid jolokia agent path
[
https://issues.apache.org/jira/browse/CASSANDRA-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649766#comment-14649766
]
Jim Witschey commented on CASSANDRA-9902:
-
Oh, wow, I see now; thanks to both of you for finding and explaining this.
Yes, I believe your changes are correct; I'm not sure why this test failed
before CASSANDRA-9560 and succeeded after. I'd appreciate a pull request on the
dtest repo.
Great find, thank you.
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)
[jira] [Commented] (CASSANDRA-9902) Windows dtest: invalid jolokia agent path
[
https://issues.apache.org/jira/browse/CASSANDRA-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (CASSANDRA-9902) Windows dtest: invalid jolokia agent path
[
https://issues.apache.org/jira/browse/CASSANDRA-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (CASSANDRA-9902) Windows dtest: invalid jolokia agent path
[
https://issues.apache.org/jira/browse/CASSANDRA-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646961#comment-14646961
]
Paulo Motta commented on CASSANDRA-9902:
The original error is caused by conflicting JDKs (namely 7 and 8) installed in
the same system, which are normally switched by changing the {{$JAVA_HOME}} and
adding {{$JAVA_HOME\bin}} to the {{$PATH}} environment variable. It may also
necessary to update the registry when switching JDKs by running the following
command on PowerShell:
{noformat}
Set-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java
Runtime Environment\' CurrentVersion 1.7
{noformat}
When java without the parent directory is called via python's
{{subprocess.check_output}} on
[cassandra-dtest/jmxutils.py|https://github.com/riptano/cassandra-dtest/blob/master/jmxutils.py#L80],
the {{$PATH}} env var is not considered due to this
[bug|http://bugs.python.org/issue8557], so instead, the java executable from
{{c:\windows\system32\}} is picked, which can be pointing to another version.
The simple fix is to use the {{$JAVA_HOME}} variable, if present, as done in
this [v1|https://github.com/pauloricardomg/cassandra-dtest/tree/9902-v1] patch.
However, this is not all the fun, after this fix, the following error appears:
{noformat}
Failed to start jolokia agent (command was: C:\Program
Files\Java\jdk1.7.0_76\bin\java -jar lib\jolokia-jvm-1.2.3-agent.jar --host
127.0.0.1 start 1992 --debug --verbose): Command '('C:\\Program
Files\\Java\\jdk1.7.0_76\\bin\\java', '-jar',
'lib\\jolokia-jvm-1.2.3-agent.jar', '--host', '127.0.0.1', 'start', '1992',
'--debug', '--verbose')' returned non-zero exit status 1
Exit status was: 1
Output was: java.util.ServiceConfigurationError:
com.sun.tools.attach.spi.AttachProvider: Provider
sun.tools.attach.WindowsAttachProvider could not be instantiated
InvocationTarget class com.sun.tools.attach.VirtualMachine (command: start) :
null
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.jolokia.jvmagent.client.util.VirtualMachineHandler.attachVirtualMachine(VirtualMachineHandler.java:66)
at org.jolokia.jvmagent.client.AgentLauncher.main(AgentLauncher.java:57)
Caused by: com.sun.tools.attach.AttachNotSupportedException: no providers
installed
at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:208)
... 6 more
{noformat}
According to this [blog
post|http://wayne-adams.blogspot.com.br/2011/10/jdi-three-ways-to-attach-to-java.html],
this issue happens when the tools.jar is not loaded by the JRE. After
inspecting the jolokia [vm instatiation
code|https://github.com/rhuss/jolokia/blob/aadf5c19c2052bdfa2bad470c55f4c15c1005d26/agent/jvm/src/main/java/org/jolokia/jvmagent/client/util/VirtualMachineHandler.java],
I found that the {{com.sun.tools.attach.VirtualMachine}} class is [dynamically
loaded|https://github.com/rhuss/jolokia/blob/aadf5c19c2052bdfa2bad470c55f4c15c1005d26/agent/jvm/src/main/java/org/jolokia/jvmagent/client/util/ToolsClassFinder.java]
from the tools.jar, however when {{VirtualMachine.attach}} is called, the JVM
is not able to load the {{sun.tools.attach.WindowsAttachProvider}} class
because the tools.jar is not on the classpath (so that's probably a bug with
jolokia, or Java on Windows).
The simple fix is to explicitly add the tools.jar to the jolokia classpath, as
suggested
[here|https://github.com/rhuss/jolokia/blob/aadf5c19c2052bdfa2bad470c55f4c15c1005d26/agent/jvm/src/main/java/org/jolokia/jvmagent/client/util/VirtualMachineHandler.java#L206].
This was done in
[v2|https://github.com/pauloricardomg/cassandra-dtest/tree/9902-v2] patch.
Apparently this seems to make jolokia connect with the testing JVM, however,
this makes the Cassandra JVM crash without java crash logs or heap dumps. The
only thing we have is a windows crash log ([attached
here|https://issues.apache.org/jira/secure/attachment/12747879/win-crashlogs.zip]),
which indicates the JVM crashes because of a [Data Execution
Prevention|https://technet.microsoft.com/en-us/library/cc738483%28v=ws.10%29.aspx]
exception. There is a feature to [whitelist a program from
DEP|http://windows.microsoft.com/en-us/windows7/Change-Data-Execution-Prevention-settings],
but apparently it's not possible to disable DEP for 64-bit programs o_O.
I don't know what might be causing this, if a JVM option that is set by
Cassandra or an actual Windows JVM bug. In order to simplify reproduction, I
made a simple class to reproduce the issue
