[JBoss JIRA] (JBWS-3569) WSDL produced for a multi-port service contains invalid port addresses in clustered configuration
noon
Chris Laprun created JBWS-3569:
----------------------------------
Summary: WSDL produced for a multi-port service contains invalid port
addresses in clustered configuration
Key: JBWS-3569
URL: https://issues.jboss.org/browse/JBWS-3569
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Reporter: Chris Laprun
Priority: Critical
Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in
ports containing the node URLs instead of the loadbalancer's.
I've tried using the dynamic WSDL rewriting as described in
https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid
URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster
node port) that haven't been used to access the WSDL, the port used to access the WSDL
has the proper address though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
noon
[
https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin....
]
Chris Laprun updated JBWS-3569:
-------------------------------
Bugzilla Update: Perform
WSDL produced for a multi-port service contains invalid port
addresses in clustered configuration
-------------------------------------------------------------------------------------------------
Key: JBWS-3569
URL: https://issues.jboss.org/browse/JBWS-3569
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Reporter: Chris Laprun
Priority: Critical
Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in
ports containing the node URLs instead of the loadbalancer's.
I've tried using the dynamic WSDL rewriting as described in
https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid
URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster
node port) that haven't been used to access the WSDL, the port used to access the WSDL
has the proper address though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
noon
[
https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration updated JBWS-3569:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=880729
WSDL produced for a multi-port service contains invalid port
addresses in clustered configuration
-------------------------------------------------------------------------------------------------
Key: JBWS-3569
URL: https://issues.jboss.org/browse/JBWS-3569
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Reporter: Chris Laprun
Priority: Critical
Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in
ports containing the node URLs instead of the loadbalancer's.
I've tried using the dynamic WSDL rewriting as described in
https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid
URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster
node port) that haven't been used to access the WSDL, the port used to access the WSDL
has the proper address though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:02 p.m.
[
https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin....
]
Alessio Soldano updated JBWS-3569:
----------------------------------
Fix Version/s: jbossws-cxf-4.1.1
WSDL produced for a multi-port service contains invalid port
addresses in clustered configuration
-------------------------------------------------------------------------------------------------
Key: JBWS-3569
URL: https://issues.jboss.org/browse/JBWS-3569
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Reporter: Chris Laprun
Assignee: Alessio Soldano
Priority: Critical
Fix For: jbossws-cxf-4.1.1
Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in
ports containing the node URLs instead of the loadbalancer's.
I've tried using the dynamic WSDL rewriting as described in
https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid
URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster
node port) that haven't been used to access the WSDL, the port used to access the WSDL
has the proper address though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:17 a.m.
[
https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3569:
---------------------------------------
This is basically fixed by the changes I just applied for
https://issues.apache.org/jira/browse/CXF-4677 . The
'autoRewriteSoapAddressForAllServices' option introduced there has to be activated
in RequestHandlerImpl, as per the patch snippet below:
{noformat}
Index: modules/server/src/main/java/org/jboss/wsf/stack/cxf/RequestHandlerImpl.java
===================================================================
--- modules/server/src/main/java/org/jboss/wsf/stack/cxf/RequestHandlerImpl.java (revision
17049)
+++ modules/server/src/main/java/org/jboss/wsf/stack/cxf/RequestHandlerImpl.java (working
copy)
@@ -197,8 +197,10 @@
String ctxUri = req.getRequestURI();
String baseUri = req.getRequestURL().toString() + "?" +
req.getQueryString();
EndpointInfo endpointInfo = dest.getEndpointInfo();
- endpointInfo.setProperty(WSDLGetUtils.AUTO_REWRITE_ADDRESS,
-
ServerConfig.UNDEFINED_HOSTNAME.equals(serverConfig.getWebServiceHost()));
+ if (serverConfig.isModifySOAPAddress()) {
+ endpointInfo.setProperty(WSDLGetUtils.AUTO_REWRITE_ADDRESS_ALL,
+
ServerConfig.UNDEFINED_HOSTNAME.equals(serverConfig.getWebServiceHost()));
+ }
for (QueryHandler queryHandler :
bus.getExtension(QueryHandlerRegistry.class).getHandlers())
{
{noformat}
WSDL produced for a multi-port service contains invalid port
addresses in clustered configuration
-------------------------------------------------------------------------------------------------
Key: JBWS-3569
URL: https://issues.jboss.org/browse/JBWS-3569
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Reporter: Chris Laprun
Assignee: Alessio Soldano
Priority: Critical
Fix For: jbossws-cxf-4.1.1
Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in
ports containing the node URLs instead of the loadbalancer's.
I've tried using the dynamic WSDL rewriting as described in
https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid
URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster
node port) that haven't been used to access the WSDL, the port used to access the WSDL
has the proper address though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4376
days inactive
4381
days old
jbossws-issues@lists.jboss.org
4 comments
3 participants
participants (3)
-
Alessio Soldano (JIRA) -
Chris Laprun (JIRA)
-
RH Bugzilla Integration (JIRA)