Bug 1231215 - Tight loop on ClientListenerNotifier
Summary: Tight loop on ClientListenerNotifier
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: 6.5.1
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-12 12:20 UTC by Jakub Markos
Modified: 2025-02-10 03:47 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:47:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
EAP and JDG logs (2.52 MB, application/zip)
2015-06-12 12:20 UTC, Jakub Markos 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-5315 0 Minor Resolved Tight loop on ClientListenerNotifier 2018-11-26 13:34:05 UTC

Description Jakub Markos 2015-06-12 12:20:56 UTC 
Created attachment 1038033 [details]
EAP and JDG logs

Seeing the linked JIRA in the remote hotrod client tests, i.e. client running in an EAP container, contacting a JDG server.
I missed this because the issue does not appear with Java 8, only with 7. The tests pass, but there are tens of megabytes of warnings.
Attached are EAP and JDG logs.
Comment 3 Vitalii Chepeliuk 2015-08-21 19:17:43 UTC 
You can still see few WARNs from server output. Find ClientListenerNotifier here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-func-remote-client-in-different-containers/jdk=java17_default,label=RHEL6&&x86_64&&mem4G/77/consoleFull
Comment 4 Vitalii Chepeliuk 2015-08-24 15:36:59 UTC 
After discussion with Gustavo I close this bug as VERIFIED. Because it is not now tight loop as before and time interval between WARNs is 10 seconds.
Comment 7 Red Hat Bugzilla 2025-02-10 03:47:43 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.