[ https://issues.jboss.org/browse/JBIDE-24560?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24560: ------------------------------------- After looking into this, the delay is universally determined by updateDebugConfig, and, specifically, waitFor(rcListenerJob, monitor); This job waits around for a matching pod to be non-null. It receives updates from the client whenever the client event framework throws a change event. I can't see anything in the code at all that is hindering or slowing down the process, or delaying unnecessarily. In fact the code looks very efficient at handling these events, and the delay seems 100% on the runtime side while waiting for a proper event to be received that indicates everything is ok to proceed. =/ partial log: https://paste.fedoraproject.org/paste/PjykYz7uIxnSa8jUR~L3qA -- This message was sent by Atlassian JIRA (v7.2.3#72005)