Bug 1302038 – JBossWS test failures on RHEL6 x86 with IBM Java 8

Bug 1302038 - JBossWS test failures on RHEL6 x86 with IBM Java 8

Summary:	JBossWS test failures on RHEL6 x86 with IBM Java 8

Status:	ASSIGNED

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Web Services (Show other bugs)
Sub Component:
Version:	6.4.6
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	Jan Blizňák
QA Contact:	Jan Blizňák
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-01-26 10:41 EST by Jan Blizňák
Modified:	2017-01-16 10:41 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:	RHEL 6.7 (32bit), IBM SDK 8 SR2 (dev8*-rhel6-x86 nodes in jenkins)
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jan Blizňák 2016-01-26 10:41:06 EST

Description of problem:
Running JBossWS testsuite against EAP 6.4.6.CP.CR2, there is a constant set of tests failing on some RHEL6 x86 nodes with IBM Java 8

Version-Release number of selected component (if applicable):
JBossWS TS 4.3.6.Final-redhat-1

How reproducible:
on almost all nodes in QA jenkins, never locally on Fedora

Steps to Reproduce:
1. run http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-6x-jbossws-testsuite-smoke/ with proper parameters

Actual results:
79 failed tests http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-6x-jbossws-testsuite-smoke/389/testReport/
Most of them failed with cause "Caused by: java.net.ConnectException: Connection refused" either on client or server side.


Expected results:
all tests pass

Additional info:
I will try to investigate more, especially to determine if it is environment issue, testsuite issue or issue with JDK.

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