[jbossws-issues] [JBoss JIRA] (JBWS-3569) WSDL produced for a multi-port service contains invalid port addresses in clustered configuration
[
https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JBWS-3569:
-----------------------------------------------
Boleslaw Dawidowicz <bdawidow(a)redhat.com> made a comment on [bug
880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729]
I don't think we can do anything on our side - patch need to be provided and it is
beyond JPP Dev team to provide proper EAP one.
I'm reassigning to Honza as there is nothing more that Chris can help with.
Honza let us know if you need any more assistance from us. I'm not sure who should be
exactly in charge to arrange the patch.
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