Bug 1316132 - [GSS](patch 6.6.0) Hot Rod client stuck sporadical if a server node is shutting down
Summary: [GSS](patch 6.6.0) Hot Rod client stuck sporadical if a server node is shutti...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Server
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: One-off release
Assignee: wfink
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On: 1315393
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-09 13:44 UTC by wfink
Modified: 2025-02-10 03:48 UTC (History)
4 users (show)

Fixed In Version:
Clone Of: 1315393
Environment:
Last Closed: 2025-02-10 03:48:52 UTC
Type: Support Patch
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-5507 0 Blocker Resolved Transactions committed immediately before cache stop can block shutdown 2017-05-29 11:17:34 UTC
Red Hat Issue Tracker ISPN-6341 0 Major Resolved StateTransferManager should be the first component to stop 2017-05-29 11:17:34 UTC

Comment 6 JBoss JIRA Server 2016-04-04 16:34:01 UTC 
Sebastian Łaskawiec <slaskawi> updated the status of jira ISPN-5507 to Closed
Comment 7 JBoss JIRA Server 2016-04-04 16:34:05 UTC 
Sebastian Łaskawiec <slaskawi> updated the status of jira ISPN-6341 to Closed
Comment 8 JBoss JIRA Server 2016-04-30 05:24:51 UTC 
Tristan Tarrant <ttarrant> updated the status of jira ISPN-5507 to Reopened
Comment 9 JBoss JIRA Server 2016-04-30 05:25:06 UTC 
Tristan Tarrant <ttarrant> updated the status of jira ISPN-5507 to Resolved
Comment 10 JBoss JIRA Server 2016-04-30 05:25:57 UTC 
Tristan Tarrant <ttarrant> updated the status of jira ISPN-6341 to Reopened
Comment 11 JBoss JIRA Server 2016-04-30 05:26:17 UTC 
Tristan Tarrant <ttarrant> updated the status of jira ISPN-6341 to Resolved
Comment 13 Red Hat Bugzilla 2025-02-10 03:48:52 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.