[JDG-1521] Management Console will not work if there are multiple cache-containers and or endpoints

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: JDG 7.2 ER3
Affects Version/s: JDG 7.2 ER2, JDG 7.1.1 GA
Component/s: API and Configuration, Management and Monitoring
Labels:
None

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Fix Build:
ER3
Target Release:

JDG 7.2 GA
Git Pull Request:
https://github.com/infinispan/jdg-management-console/pull/112
Steps to Reproduce:

Hide

Used a standard clustered.xml (7.1.1)
Step 1 - add container:
<cache-container name="clustered2" default-cache="mycache" statistics="true">
<transport lock-timeout="60000"/>
<global-state/>
<distributed-cache name="mycache"/>
</cache-container>
Step 2 - add connector and binding:
<hotrod-connector socket-binding="hotrod" cache-container="clustered">
<topology-state-transfer lazy-retrieval="false" lock-timeout="1000" replication-timeout="5000"/>
</hotrod-connector>
<hotrod-connector name="hr2" socket-binding="hotrod2" cache-container="clustered2">
<topology-state-transfer lazy-retrieval="false" lock-timeout="1000" replication-timeout="5000"/>
</hotrod-connector>

<socket-binding name="hotrod2" port="11333"/>

Step 3 - add a name for the hotrod connector:
<hotrod-connector name="hr1" socket-binding="hotrod" ....

Show
Used a standard clustered.xml (7.1.1) Step 1 - add container: <cache-container name="clustered2" default-cache="mycache" statistics="true"> <transport lock-timeout="60000"/> <global-state/> <distributed-cache name="mycache"/> </cache-container> Step 2 - add connector and binding: <hotrod-connector socket-binding="hotrod" cache-container="clustered"> <topology-state-transfer lazy-retrieval="false" lock-timeout="1000" replication-timeout="5000"/> </hotrod-connector> <hotrod-connector name="hr2" socket-binding="hotrod2" cache-container="clustered2"> <topology-state-transfer lazy-retrieval="false" lock-timeout="1000" replication-timeout="5000"/> </hotrod-connector> <socket-binding name="hotrod2" port="11333"/> Step 3 - add a name for the hotrod connector: <hotrod-connector name="hr1" socket-binding="hotrod" ....

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

If a second cache contiainer is configured with the necesarry endpoint the management console shows

1.) wrong information
If the endpoint is not configured or the (1. default) enpoint does not use the name attribute
-> both containers shows the same enpoint configuration which is wrong

2.) blank page
If both endpoints use a name attribute the console is not longer working

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

Screen Shot 2018-02-02 at 11.27.02 AM.png
36 kB
2018/02/02 11:30 AM
Step1 - hotrod2 endpoint configured - hotrod1 enpoint does not have a name.png
20 kB
2018/02/02 8:52 AM

is caused by

ISPN-7477 Endpoints with non-default names are not parsed

Closed

Ryan Emerson added a comment - 2018/02/05 5:35 AM

rhn-support-wfink vblagoje Do we also want this on the 7.1.x branch if it's affecting a customer? It's currently only backported to 7.2.x.

Ryan Emerson added a comment - 2018/02/05 5:35 AM rhn-support-wfink vblagoje Do we also want this on the 7.1.x branch if it's affecting a customer? It's currently only backported to 7.2.x.

Vladimir Blagojevic (Inactive) added a comment - 2018/02/02 11:30 AM

rhn-support-wfink I am hoping that this fix is what you/we wanted. I tried it with and without naming the connectors. But I am sure when it lands in your hands you'll thoroughly verify it once again to make sure it is exactly what we wanted. Attaching the screenshot of the fixed cache container page.

Vladimir Blagojevic (Inactive) added a comment - 2018/02/02 11:30 AM rhn-support-wfink I am hoping that this fix is what you/we wanted. I tried it with and without naming the connectors. But I am sure when it lands in your hands you'll thoroughly verify it once again to make sure it is exactly what we wanted. Attaching the screenshot of the fixed cache container page.

Vladimir Blagojevic (Inactive) added a comment - 2018/02/02 9:37 AM - edited

I think you are right remerson@redhat.com, looking into this one now.

Vladimir Blagojevic (Inactive) added a comment - 2018/02/02 9:37 AM - edited I think you are right remerson@redhat.com , looking into this one now.

Ryan Emerson added a comment - 2018/02/02 9:09 AM

vblagoje I think backporting ~~ISPN-7477~~ should fix this issue. We will also need to backport 7.2.x to prevent a regression.

Ryan Emerson added a comment - 2018/02/02 9:09 AM vblagoje I think backporting ISPN-7477 should fix this issue. We will also need to backport 7.2.x to prevent a regression.

Details

Description

Attachments

Attachments

Issue Links

Easy Agile Planning Poker

Activity

Collapse comment: Ryan Emerson added a comment - 2018/02/05 5:35 AM

Expand comment: Ryan Emerson added a comment - 2018/02/05 5:35 AM

Collapse comment: Vladimir Blagojevic (Inactive) added a comment - 2018/02/02 11:30 AM

Expand comment: Vladimir Blagojevic (Inactive) added a comment - 2018/02/02 11:30 AM

Collapse comment: Vladimir Blagojevic (Inactive) added a comment - 2018/02/02 9:37 AM, Edited by Vladimir Blagojevic - 2018/02/02 11:11 AM

Expand comment: Vladimir Blagojevic (Inactive) added a comment - 2018/02/02 9:37 AM, Edited by Vladimir Blagojevic - 2018/02/02 11:11 AM

Collapse comment: Ryan Emerson added a comment - 2018/02/02 9:09 AM

Expand comment: Ryan Emerson added a comment - 2018/02/02 9:09 AM

People

Dates