[ https://issues.jboss.org/browse/WFLY-12167?page=com.atlassian.jira.plugin... ] Paul Ferraro edited comment on WFLY-12167 at 6/6/19 2:45 PM: ------------------------------------------------------------- The code in ServiceSupplier is correct. Using the new MSC API, the only way to obtain a value provided by an ON_DEMAND service is install a service that depends on the target service. Once the value is retrieved, the mode of the temporary service is set to REMOVE. However, this removal happens asynchronously. Even if there was no memory leak in MSC this would still cause a heap spike until an available MSC thread is able to perform the removal. To resolve that, ServiceSupplier.get() can block until the temporary service removal is complete which would prevent any spike in heap due to a pile-up of to-be-removed services. was (Author: pferraro): The code in ServiceSupplier is correct. Using the new MSC API, the only way to obtain a value provided by an ON_DEMAND service is install a service that depends on the target service. Once the value is retrieved, the mode of the temporary service is set to REMOVE. However, this removal happens asynchronously. Even if there were a memory leak in MSC this would still cause a heap spike until some MSC thread is able to perform the removal. To resolve that, ServiceSupplier.get() can block until the temporary service removal is complete which would prevent any spike in heap due to a pile-up of to-be-removed services. -- This message was sent by Atlassian Jira (v7.12.1#712002)