Loading...

XML

Word

Printable

Details

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

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 Links:

Description

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