Bug 1049796

Summary:	[TEST] (6.2.x?) Intermittent 'AssertionError: expected:<200> but was:<500>' in org.jboss.as.test.manualmode.ws.ReloadWSDLPublisherTestCase.testHelloStringAfterReload
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Emmanuel Hugonnet (ehsavoie) <ehugonne>
Component:	Web Services	Assignee:	Emmanuel Hugonnet (ehsavoie) <ehugonne>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Jelinek <pjelinek>
Severity:	medium	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.0	CC:	cdewolf, ehugonne, jmartisk, kkhan, myarboro, pjelinek, smumford, vtunka
Target Milestone:	CR3
Target Release:	EAP 6.2.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1034229	Environment:
Last Closed:	2014-06-09 12:48:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1034229, 1067348
Bug Blocks:	1067532

Description Emmanuel Hugonnet (ehsavoie) 2014-01-08 09:08:26 UTC

+++ This bug was initially created as a clone of Bug #1034229 +++

See e.g.:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-RHEL-matrix-OracleJDK7/98/jdk=java17_default,label_exp=RHEL6%26%26x86_64/testReport/org.jboss.as.test.manualmode.ws/ReloadWSDLPublisherTestCase/testHelloStringAfterReload/

--- Additional comment from Emmanuel Hugonnet (ehsavoie) on 2013-11-27 07:07:16 EST ---

The issue is due to the fact that the jvm is reusing the same connection.
Setting keep-alive to false fixes it.

--- Additional comment from Jan Martiska on 2013-12-05 07:01:35 EST ---

Emmanuel is right, but keep-alive cannot be used with WS invocations (you don't have access to the underlying connection), so that would only resolve half of the problem. I think the best solution will be to add a 5 second wait until the pooled connections time out.

--- Additional comment from Emmanuel Hugonnet (ehsavoie) on 2013-12-05 07:49:44 EST ---

It is working by setting the keep-alive to false in the set up and resetting it to the previous value in the tear down.
I have a patch for this.
This avoid long( 5s) test.

--- Additional comment from Emmanuel Hugonnet (ehsavoie) on 2013-12-05 07:51:16 EST ---

https://github.com/ehsavoie/jboss-eap/tree/BZ-1034229 : the patch but I need to make one for upstream.

--- Additional comment from Jan Martiska on 2013-12-05 08:07:18 EST ---

Ok, I didn't think of this solution. We'll go with yours then.

--- Additional comment from Emmanuel Hugonnet (ehsavoie) on 2013-12-06 10:25:25 EST ---

PR : https://github.com/jbossas/jboss-eap/pull/720
Upstream : https://github.com/wildfly/wildfly/pull/5576

Comment 1 Emmanuel Hugonnet (ehsavoie) 2014-01-08 10:31:38 UTC

PS for 6.2.x : https://github.com/jbossas/jboss-eap/pull/759

Comment 3 Scott Mumford 2014-01-21 03:41:29 UTC

Marking for inclusion in 6.2.1 release notes as this bug appears in the master tracking BZ 1027004

Comment 5 Pavel Jelinek 2014-01-27 11:27:54 UTC

Woriking for ipv4 but not for ipv6. 
See eg: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP-6.2.x-CP/job/eap-62x-patched-as-testsuite-Windows-OracleJDK7-pureIPV6/15/jdk=java17_default,label_exp=w2k8r2-ipv6%26%26x86_64%26%26pure-ipv6/testReport/org.jboss.as.test.manualmode.ws/ReloadWSDLPublisherTestCase/testHelloStringAfterReload/

Comment 6 Pavel Jelinek 2014-01-27 14:55:11 UTC

I meen now I don't see this issue on IPV4 but it still appears intermittently on IPV6.

Comment 8 Emmanuel Hugonnet (ehsavoie) 2014-01-27 16:39:32 UTC

Does it appear on Windows only or on Windows and Linux ?

Comment 10 Emmanuel Hugonnet (ehsavoie) 2014-02-06 11:43:39 UTC

This is due to the proxy configuration when running the ipv6 test.
By removing all proxy configuration in the test code when running the test in the same ipv6 environment it was green 100 times in a row.

Comment 12 Emmanuel Hugonnet (ehsavoie) 2014-02-12 22:15:51 UTC

This issue is due to a misconfiguration on the IPV6 QA Jenkins : currently the connection to the server during test is using the proxy which seems to defeat the fact that we don't want a keep-alive connection.
If we reset the proxy configuration programmatically in the test then it goes green.
I think the proxy matcher in the JVM doesn't work well with IPv6 addresses.

Comment 14 Carlo de Wolf 2014-04-14 10:24:49 UTC

See https://bugzilla.redhat.com/show_bug.cgi?id=1067348#c4

Comment 15 Emmanuel Hugonnet (ehsavoie) 2014-05-05 12:33:51 UTC

PR for 6.2.x : https://github.com/jbossas/jboss-eap/pull/1296

Comment 16 Pavel Jelinek 2014-05-06 12:43:56 UTC

Unfortunatelly there seems to be same fail again for EAP 6.2.3.CP.CR2 despite I'm using  -DnonProxyHosts="localhost|127.*|[::0]|[::1]|[$MYTESTIPV6_2]|[$MYTESTIPV6_1]" -Dhttp.nonProxyHosts="localhost|127.*|[::0]|[::1]|[$MYTESTIPV6_2]|[$MYTESTIPV6_1]"  maven arguments. 

See: 
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP-6.2.x-CP/view/EAP-6.2.x-CP-jobs/job/eap-62x-patched-as-testsuite-RHEL-OpenJDK7-pureIPV6/jdk=openjdk-1.7.0-local,label_exp=RHEL6-ipv6%26%26x86_64%26%26pure-ipv6/18/testReport/org.jboss.as.test.manualmode.ws/ReloadWSDLPublisherTestCase/testHelloStringAfterReload/

Comment 17 Pavel Jelinek 2014-05-19 12:05:38 UTC

Fixed in EAP 6.2.3.CR3.