Bug 967082 - Request for WFLY-1369 (Admin console displays incorrect port for WSDL url)
Summary: Request for WFLY-1369 (Admin console displays incorrect port for WSDL url)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: EAP 6.4.0
Assignee: Heiko Braun
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On:
Blocks: 1013716
TreeView+ depends on / blocked
 
Reported: 2013-05-24 16:04 UTC by Andrew Matusevich
Modified: 2018-12-05 16:01 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
: 1013716 (view as bug list)
Environment:
Last Closed: 2016-09-16 21:22:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1369 0 Major Resolved Admin console displays incorrect port for WSDL url 2016-09-16 21:20:15 UTC

Internal Links: 1013716

Description Andrew Matusevich 2013-05-24 16:04:45 UTC
Community JIRA: https://issues.jboss.org/browse/WFLY-1369
Associated case: 00822365

When multiple HTTP connectors are defined, the Admin Console's Runtime->Server Status->Webservices->Web Service Endpoints may display the incorrect port number in a selection's WSDL Url text box. The WSDL is published to the correct URL which leads to confusion when the wrong port is displayed in the WSDL Url text box.

Comment 1 Andrew Matusevich 2013-05-24 16:10:23 UTC
Patch is required for 6.1 only

Comment 9 Heiko Braun 2015-06-30 07:42:56 UTC
The view "Runtime / Webservices" uses the selected server when whowing the WSDL URL. Since the server "ct-server" was selected tha port of that server is used in the URLs. If you want to use another port for the web service you have to deploy that web service to another server.

Comment 10 Brad Maxwell 2016-09-16 21:22:27 UTC
Closing as it was nacked and it out of date


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