Bug 1034097 - Failures in RespawnTestCase on IBM JDK
Summary: Failures in RespawnTestCase on IBM JDK
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Testsuite
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER5
: EAP 6.3.0
Assignee: Pavel Jelinek
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On:
Blocks: 1097585
TreeView+ depends on / blocked
 
Reported: 2013-11-25 09:17 UTC by Ondrej Chaloupka
Modified: 2016-10-18 10:21 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
: 1097585 (view as bug list)
Environment:
Last Closed: 2014-08-06 14:37:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBQA-9028 0 Major Closed org.jboss.as.test.integration.respawn.RespawnTestCase fails on IBMJDK due to 'JPS executable not found' 2016-10-18 10:21:19 UTC

Description Ondrej Chaloupka 2013-11-25 09:17:12 UTC 
Tested with EAP 6.2.0.CR3.
The RespawnTestCase fails as the IBM JDK does not contain 'jps' tool.

I suppose that it will be needed to rework the test to use 'ps' or some other way of finding running java processes.

The failure is:
Failed tests:   org.jboss.as.test.integration.respawn.RespawnTestCase: JPS executable not found. File: /qa/tools/opt/ibm-java-i386-70/jre/../bin/jps
Comment 1 Ondrej Chaloupka 2014-01-30 13:06:17 UTC 
We were hitting the same problem in Narayana testsuite. There is the way here how Hayk fixed it:
https://github.com/hhovsepy/narayana/blob/JBQA-8699/XTS/localjunit/crash-recovery-tests/src/main/java/com/arjuna/qa/extension/JBossAS7ServerKillProcessor.java
Comment 2 Pavel Jelinek 2014-05-14 06:38:15 UTC 
PR: https://github.com/jbossas/jboss-eap/pull/1322
Comment 3 Pavel Jelinek 2014-07-03 08:06:54 UTC 
Verified for EAP 6.3.0.ER8.
Comment 4 JBoss JIRA Server 2016-10-18 10:21:19 UTC 
Radim Hatlapatka <rhatlapa> updated the status of jira JBQA-9028 to Closed
Note You need to log in before you can comment on or make changes to this bug.