Bug 1333968 - [GSS](6.4.z) XTS does not work with jbossws.undefined.host in WS config
Summary: [GSS](6.4.z) XTS does not work with jbossws.undefined.host in WS config
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: XTS
Version: 6.4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jiri Ondrusek
QA Contact: Ondrej Chaloupka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-06 20:41 UTC by Chris Dolphy
Modified: 2019-08-19 12:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:45:41 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-6290 0 Major Open XTS does not work with jbossws.undefined.host in WS config 2020-07-28 08:38:41 UTC

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:
Note You need to log in before you can comment on or make changes to this bug.