Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1200360

Summary: Hot Rod client does not full recover after a complete server shutdown
Product: [JBoss] JBoss Data Grid 6 Reporter: wfink
Component: Infinispan, ServerAssignee: Galder ZamarreƱo <galder.zamarreno>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Gencur <mgencur>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.3.0CC: chuffman, dstahl, jdg-bugs, rmarwaha, ttarrant
Target Milestone: ER2   
Target Release: 6.4.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Hot Rod clients should recover from full cluster restarts without the need to restart the RemoteCacheManager instances which control topology and connection establishment. Reason: Having to restart RemoteCacheManager instances manually by clients when cluster is fully restarted meant clients would need to deal with such situations in their code. Result: When Hot Rod clients discover that a cluster might be not be available any more, they will try to restore the initial host configuration and see if the cluster has been restarted. If that fails, Hot Rod clients will fail indicating that the cluster is no longer available.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-02 12:13:46 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1201626    

Description wfink 2015-03-10 12:07:43 UTC
Description of problem:
If the complete cluster is going down for some reason, the client side throws TransportExceptions.
If the client continue in this state without a restart there are the following issues:
- the last node need to be started to continue
- the cluster view will not be updated any more
- client continue only with the 'last' node no matter whether the cluster topology will be changed on the server side

Comment 2 JBoss JIRA Server 2015-03-11 07:41:48 UTC
Galder ZamarreƱo <galder.zamarreno> updated the status of jira ISPN-5283 to Coding In Progress