Bug 1102733
| Summary: | WSRP clustering - ConnectException after failover | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 6 | Reporter: | vramik | ||||||
| Component: | Portal | Assignee: | Nobody <nobody> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | vramik | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.2.0 | CC: | epp-bugs, ppalaga, tkyjovsk, vramik | ||||||
| Target Milestone: | ER04 | ||||||||
| Target Release: | 6.2.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2025-02-10 03:35:57 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 900347 [details]
server.log of the consumer
Created attachment 900348 [details]
simple distributable, remotable test portlet
Is this a regression? If so, which would be the last known version that this worked? With this information, I'll be able to pin-point when/where the problem was introduced. Hi Juca, Last known working wersion was JPP6.0.0.GA. Status: I was able to reproduce the behavior described by Vlasta. While debugging it, I found out that it seems to be a problem with the integration or with an updated component (CXF being my first guess), as I was able to get the correct behavior by just dropping the latest WSRP jars into the older JPP (meaning, the code for the latest ER2 looks correct). Status: it seems this is the same situation as https://bugzilla.redhat.com/show_bug.cgi?id=880729 . For Portal 6.0.0.GA, we had this: ./standalone/configuration/standalone-ha.xml: <wsdl-host>jbossws.undefined.host</wsdl-host> For 6.1.1.ER2, we have this: ./standalone/configuration/standalone-ha.xml: <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host> So, it seems some XSL transformation is missing, but would be interesting to get feedback from QA to see if just by changing this property would fix the issue. PR https://github.com/gatein/gatein-portal/pull/870 , pending confirmation from QA (see previous comment). I've tried failover with <wsdl-host>jbossws.undefined.host</wsdl-host> set in standalone-ha.xml and failover works. https://github.com/gatein/gatein-portal/pull/870 was merged in upstream. Setting back to modified, as this is targeted at JBoss Portal 6.2.0.ER3 Fixup: ...this is targeted at JBoss Portal 6.2.0.ER4 Verified in ER04 This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
Description of problem: Producer on loadbalancer is not handled properly, it always keep some URL of the node instead of LB - active node. Version-Release number of selected component (if applicable): RHPJ6.2.0.ER02 How reproducible: always Steps to Reproduce: 1. setup producer as 2 node cluster + loadbalancer - my setup: - perf13.mw.lab.eng.bos.redhat.com:8080 - loadbalancer - perf13.mw.lab.eng.bos.redhat.com:8180 - node1 - perf13.mw.lab.eng.bos.redhat.com:8280 - node2 2. setup another instance as consumer 3. on consumer: register producer with loadbalancer WSDL 4. deploy and add remote portlet (e.g. attached simpleloggingportlet) 5. The portlet writes messages to log (after clicking on submit button) -> find out which node is active 6. kill the node 7. click on submit button again 8. see consumer's log Actual results: - java.net.ConnectException: ConnectException invoking http://perf13.mw.lab.eng.bos.redhat.com:8180/wsrp-producer/v2/MarkupService: Connection refused - which was active producer wich was stopped - Portlet is not displayed Additional info: - The same behaviour is present on JPP6.1.1.GA