[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22243: --------------------------------------- I looked at this and we are specifically ignoring some refresh requests. Our caching strategy is purposely ignoring calls where it already knows about the version of the resource. Ideally, we would have a single cache for a connection and we could possibly evict the refreshed member. During investigation, I also discovered our refresh job is ignoring a parameter that it should be passing on (isAdded?). I think the short term fix might be to figure out how we might pass a 'context' to the cache so it knows it should evict the member in question and continue on refreshing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)