[ https://issues.jboss.org/browse/GTNWSRP-340?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on GTNWSRP-340: ------------------------------------------------- Michal Vanco <mvanco(a)redhat.com&gt; 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/ServiceDesc...: 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!!! -- 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