[jbossws-issues] [JBoss JIRA] (JBWS-3569) WSDL produced for a multi-port service contains invalid port addresses in clustered configuration

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750172#comment-12750172 ] 

RH Bugzilla Integration commented on JBWS-3569:
-----------------------------------------------

Michal Vanco <mvanco at redhat.com> made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729]

Hi Chris, 

I was just checking the same scenario which is already described here with JPP 6.0.0 ER05 (which also includes the patch JBPAPP-10497) and it seems like issue is still present.
Again I have 2 producer nodes + loadbalancer + another jpp instance as consumer.
I registered consumer against loadbanacer WSDL, added remote portlet and failover active producer node. Unfortunately portlet isn't displayed and it's not possible to refresh consumer.

I'm getting:
java.net.ConnectException: ConnectException invoking http://perf15.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/ServiceDescriptionService: Connection refused
(perf15 was active producer node which was stopped).

There is a change at loadbalancer, host:port/wsrp-producer/v2/MarkupService?wsdl - before it showed different node for each refresh - right now it points to active node only.
But... the content is:

<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:bind="urn:oasis:names:tc:wsrp:v2:bind" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:oasis:names:tc:wsrp:v2:wsdl">
<import location="http://perf13.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/MarkupService?wsdl=wsrp-2.0-bindings.wsdl" namespace="urn:oasis:names:tc:wsrp:v2:bind"></import>
<service name="WSRPService">
<port binding="bind:WSRP_v2_ServiceDescription_Binding_SOAP" name="WSRPServiceDescriptionService">
<soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/ServiceDescriptionService"/>
</port>
<port binding="bind:WSRP_v2_PortletManagement_Binding_SOAP" name="WSRPPortletManagementService">
<soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/PortletManagementService"/>
</port>
<port binding="bind:WSRP_v2_Markup_Binding_SOAP" name="WSRPMarkupService">
<soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/MarkupService"/>
</port>
<port binding="bind:WSRP_v2_Registration_Binding_SOAP" name="WSRPRegistrationService">
<soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/RegistrationService"/>
</port>
</service>
</definitions>

I expected perf13...(loadbalancer) will be used at all wsdl links (that's what patch was about), but it's not.
This also means that current docs test at BZ doesn't reflect current portal behavior.

Thanks for any updates!!!
                
> 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