Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Bug 1378498
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh81 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 1378498
-
[GSS] ClientListener stops working after connection failure
Summary:
[GSS] ClientListener stops working after connection failure
Keywords
:
Status
:
VERIFIED
Alias:
None
Product:
JBoss Data Grid 6
Classification:
JBoss
Component:
Infinispan
Sub Component:
---
Version:
6.5.1,6.6.2
Hardware:
Unspecified
OS:
Unspecified
Priority:
unspecified
Severity:
unspecified
Target Milestone:
CR1
Target Release
:
6.6.2
Assignee:
Tristan Tarrant
QA Contact:
Martin Gencur
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
1374440
1380236
TreeView+
depends on
/
blocked
Reported:
2016-09-22 14:54 UTC by
Shay Matasaro
Modified:
2022-01-27 04:15 UTC (
History
)
CC List:
5 users
(
show
)
jdg-bugs
jsenko
onagano
vjuranek
wfink
Fixed In Version:
Doc Type:
If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type:
Bug
Attachments
(Terms of Use)
Add an attachment
(proposed patch, testcase, etc.)
Links
System
ID
Private
Priority
Status
Summary
Last Updated
Red Hat Issue Tracker
JDG-517
0
Major
Verified
ClientListener stops working after connection failure
2019-05-14 20:33:19 UTC
Red Hat Knowledge Base (Solution)
2697831
0
None
None
None
2016-10-13 07:06:13 UTC
Description
Shay Matasaro
2016-09-22 14:54:37 UTC
https://issues.jboss.org/browse/JDG-517
Comment 5
Gustavo Fernandes
2017-05-09 14:40:17 UTC
PR for 6.6.x
Note
You need to
log in
before you can comment on or make changes to this bug.