Community
Participate
Working Groups
The current implementation uses the Executors.newSingleThreadExecutor() call in order to create the background thread responsible for the asynchronous write(s). This call creates non-daemon threads which prevent the application from exiting -> the thread(s) should be daemon(s) since we do not want the weaving to affect the application start/stop. In order to prevent the danger that the thread will be stopped while it is updating something, a derived Thread class should be used (via a special ThreadFactory) that attempts to complete any ongoing I/O operation before (gracefully) terminating.
Are you in a position to give me a patch or pull request for that change?
Created attachment 247703 [details] Suggested patch
Added patch (not compiled or tests, but I am sure you can manage any minor errors that may be reported...)