Bug 816641 - Torquebox: jmx4r does not work in integration tests
Summary: Torquebox: jmx4r does not work in integration tests
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: TorqueBox
Version: 2.0.0.ER4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ER1
: 2.1.0
Assignee: Bob McWhirter
QA Contact: Oliver Kišš
Depends On:
TreeView+ depends on / blocked
Reported: 2012-04-26 15:12 UTC by Oliver Kišš
Modified: 2015-08-02 23:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-11-30 15:35:03 UTC
Type: Bug

Attachments (Terms of Use)
RSpec report (105.53 KB, text/html)
2012-04-26 15:12 UTC, Oliver Kišš
no flags Details
EAP log (736.33 KB, text/x-log)
2012-05-30 11:00 UTC, Oliver Kišš
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TORQUE-842 0 Major Closed Integration Tests Using jmx4r Fail on RHEL 6 2012-11-05 08:49:19 UTC

Description Oliver Kišš 2012-04-26 15:12:47 UTC
Created attachment 580508 [details]
RSpec report

Description of problem:
jmx4r does not work properly in Torquebox integration tests.

jmx4r relies on com.sun.tools.attach.VirtualMachine.list() method which returns empty list when called during integration tests.

Version-Release number of selected component (if applicable):
Torquebox 2.0.1
Actual results:
Integration tests fail

Additional info:
RSpec html report is attached

Fedora 15 
OpenJDK 1.6.0_22 or Sun JDK 1.6.0_20

Comment 1 Bob McWhirter 2012-05-14 15:07:22 UTC
We need to figure out how to run the integ tests locally with the EAP/WFK build and I'll get back to you on this.  Iniitially I cannot fathom why it's not working, unless JMX is disabled in EAP?

Comment 2 Oliver Kišš 2012-05-30 11:00:00 UTC
Created attachment 587680 [details]
EAP log

Added server log from running integration tests with Torquebox 2.0.3.redhat.1 and EAP6 ER8

Comment 3 Ben Browning 2012-05-31 18:12:11 UTC
I don't have the appropriate permissions to link things, but this is tracked upstream in https://issues.jboss.org/browse/TORQUE-842. I've replicated this in a RHEL 6 virtual machine and am testing a fix now.

Comment 4 Ben Browning 2012-06-01 13:18:25 UTC
Fixed committed to our 2.0.x-dev branch in https://github.com/torquebox/torquebox/commit/73b05d4db66e186690aa7290fd4a446735df100b

Comment 5 Karel Piwko 2012-06-13 14:32:09 UTC
Removed Target Version, this was not productized so far.

Comment 6 JBoss JIRA Server 2012-07-26 21:58:07 UTC
Benjamin Browning <bbrowning@redhat.com> updated the status of jira TORQUE-842 to Closed

Comment 7 Karel Piwko 2012-07-27 06:59:42 UTC
Moving target version to 2.1.0.

Comment 8 Marek Novotny 2012-09-25 06:36:14 UTC
Already in product branch as commit - 

Comment 9 Karel Piwko 2012-11-30 15:35:03 UTC
Distributed as a part of WFK 2.1.0.GA release.

Note You need to log in before you can comment on or make changes to this bug.