[
https://issues.jboss.org/browse/JBIDE-21449?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-21449:
---------------------------------------
[~fbricon] First think to verify you dont get multiple callbacks is to allow the
WatchClient to reconnect at least once. Then, you will probable need to do a conditional
break on the 'received' of the listener to validate you are getting a single
event. The code now applies a single listener per kind per project. Also, some actions
will trigger multiple event callbacks but these are actually because the resource is being
changed multiple times by the server.
WatchManager makes multiple callbacks for same event
----------------------------------------------------
Key: JBIDE-21449
URL:
https://issues.jboss.org/browse/JBIDE-21449
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Jeff Cantrill
Assignee: Jeff Cantrill
Priority: Blocker
Fix For: 4.3.1.CR1
There is an issue in either the WatchClient or the the dependent functionality of the the
openshift-rest-client where a new listener is registered when the watch restarts from a
timeout. Listeners should only be able registered once
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)