Bug 1333968

Summary:	[GSS](6.4.z) XTS does not work with jbossws.undefined.host in WS config
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Chris Dolphy <cdolphy>
Component:	XTS	Assignee:	Jiri Ondrusek <jondruse>
Status:	CLOSED EOL	QA Contact:	Ondrej Chaloupka <ochaloup>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.6	CC:	istudens, jondruse, rstancel
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:45:41 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:

Description Chris Dolphy 2016-05-06 20:41:21 UTC

Description of problem:
Can't use XTS and "jbossws.undefined.host" for wsdl-host, or WSDL rewriting with request URL.

XTS uses ServerConfig to initialise it's configuration. However, we should rely on jboss.bind.address instead, because wsdl-host could take "jbossws.undefined.host" as a value.
"jbossws.undefined.host" will cause UnknownHostException, because address rewriting is not executed in XTS.



Version-Release number of selected component (if applicable):
EAP 6.4.6

How reproducible:
See attached reproducer

Steps to Reproduce:
1. run "mvn test" to execute
2.
3.

Actual results:
Stacktrace with:
Caused by: java.net.UnknownHostException: jbossws.undefined.host
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) [rt.jar:1.7.0_75]
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [rt.jar:1.7.0_75]
	at java.net.Socket.connect(Socket.java:579) [rt.jar:1.7.0_75]

Expected results:
Working

Additional info: