JB, [resending - ignore the duplicate message if it turns up]
I set the logging levels you identified and repeated the exercise of deleting a kar from the deploy folder and then later adding the same kar back to the deploy folder. The associated section of the karaf log with trace entries is here - https://www.dropbox.com/s/t2odu2k7w5e6rwy/deploy%20delay%20karaf.log?dl=0 I notice lots of repeated logging like this: 2019-04-17T09:12:30,458 | DEBUG | downloader-6-thread-6 | AetherBasedResolver | 2 - org.ops4j.pax.url.mvn - 2.6.1 | Adding repo from inside multi dir: file:/C:/data/ksr-1.0.0/data/kar/FeedStorage-1.0.0-SNAPSHOT/@id=FeedStorage-1.0.0-SNAPSHOT The relevant times to look at in the log are: 1/ undeploy kar @ 2019-04-17T09:12:30,337 - downloader thread tracing stops @ 2019-04-17T09:12:59,043 (30 second delay) - dependency analysis complete @ 019-04-17T09:14:00,074 (60 second delay) - for some reason lots of other unrelated features are stopped/restarted at this time including activemq? - restarted features are all active again @ 2019-04-17T09:14:17,636 (17 second delay) 2/ deploy kar @ 2019-04-17T09:23:43,585 - downloader thread tracing stops @ 2019-04-17T09:23:45,925 (2 second delay) - dependency analysis complete @ 2019-04-17T09:24:39,063 (55 second delay) - dependent bundles installed and started @ 2019-04-17T09:24:39,306 (no delay) - downloader thread tracing stops @ 2019-04-17T09:24:39,311 (no delay) - feature install analysis complete @ 2019-04-17T09:26:37,875 (120 second delay) - new feature active @ 2019-04-17T09:26:39,893 (2 second delay) Thanks Steve -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
