Bug 1039090 - Handle cache shutdown during ongoing hotrod operation silently with retry
Summary: Handle cache shutdown during ongoing hotrod operation silently with retry
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan, Server
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: CR1
: 6.4.0
Assignee: Tristan Tarrant
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-06 15:08 UTC by Michal Linhard
Modified: 2015-05-25 20:38 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-01-28 13:28:02 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-3743 0 Major Resolved Silence "IllegalStateException: Default cache is in 'STOPPING' state" exceptions 2018-04-25 15:15:47 UTC
Red Hat Issue Tracker ISPN-4717 0 Major Resolved Hot Rod 2.0 should add error codes for suspected nodes and stopping/stopped caches 2018-04-25 15:15:47 UTC

Description Michal Linhard 2013-12-06 15:08:00 UTC 
With 6.2.0.ER5 the call to a hotrod operation will throw a HotRodClientException if the cache is shutdown during the operation. 

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/RESILIENCE/job/jdg-func-resilience-dist-4-3/99/artifact/report/loganalysis/client/categories/cat19_entry10.txt


This however might be only happening on one node while rest of the cluster is operating normally and can be retried inside hotrod client.
Comment 4 JBoss JIRA Server 2015-05-25 20:38:58 UTC 
Dan Berindei <dberinde> updated the status of jira ISPN-3743 to Resolved
Note You need to log in before you can comment on or make changes to this bug.