Bug 1102733 - WSRP clustering - ConnectException after failover
Summary: WSRP clustering - ConnectException after failover
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER04
: 6.2.0
Assignee: Nobody
QA Contact: vramik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-29 13:03 UTC by vramik
Modified: 2025-02-10 03:35 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:35:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
server.log of the consumer (217.67 KB, text/x-log)
2014-05-29 13:04 UTC, vramik
no flags Details
simple distributable, remotable test portlet (7.31 KB, application/java-archive)
2014-05-29 13:05 UTC, vramik
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GTNPORTAL-3505 0 Major Resolved WSRP Producers behind Load Balancers get wrong endpoint URL 2014-08-13 18:13:48 UTC

Description vramik 2014-05-29 13:03:39 UTC
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

Comment 1 vramik 2014-05-29 13:04:30 UTC
Created attachment 900347 [details]
server.log of the consumer

Comment 2 vramik 2014-05-29 13:05:50 UTC
Created attachment 900348 [details]
simple distributable, remotable test portlet

Comment 4 Juraci Paixão Kröhling 2014-05-30 08:30:10 UTC
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.

Comment 5 vramik 2014-06-01 14:55:56 UTC
Hi Juca,

Last known working wersion was JPP6.0.0.GA.

Comment 6 Juraci Paixão Kröhling 2014-06-03 16:09:32 UTC
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).

Comment 7 Juraci Paixão Kröhling 2014-06-04 14:24:28 UTC
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.

Comment 8 Juraci Paixão Kröhling 2014-06-04 14:38:51 UTC
PR https://github.com/gatein/gatein-portal/pull/870 , pending confirmation from QA (see previous comment).

Comment 9 vramik 2014-06-04 20:41:12 UTC
I've tried failover with <wsdl-host>jbossws.undefined.host</wsdl-host> set in standalone-ha.xml and failover works.

Comment 10 Peter Palaga 2014-06-17 13:22:01 UTC
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

Comment 11 Peter Palaga 2014-06-17 13:22:56 UTC
Fixup: ...this is targeted at JBoss Portal 6.2.0.ER4

Comment 12 vramik 2014-07-02 14:11:05 UTC
Verified in ER04

Comment 15 Red Hat Bugzilla 2025-02-10 03:35:57 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.