{"action":"opened","issue":{"url":"https://api.github.com/repos/OpenLiberty/boost/issues/237","repository_url":"https://api.github.com/repos/OpenLiberty/boost","labels_url":"https://api.github.com/repos/OpenLiberty/boost/issues/237/labels{/name}","comments_url":"https://api.github.com/repos/OpenLiberty/boost/issues/237/comments","events_url":"https://api.github.com/repos/OpenLiberty/boost/issues/237/events","html_url":"https://github.com/OpenLiberty/boost/issues/237","id":392431287,"node_id":"MDU6SXNzdWUzOTI0MzEyODc=","number":237,"title":"Refine app monitoring (polling interval or mbean) to avoid double update on `mvn compile`","user":{"login":"scottkurz","id":4081634,"node_id":"MDQ6VXNlcjQwODE2MzQ=","avatar_url":"https://avatars3.githubusercontent.com/u/4081634?v=4","gravatar_id":"","url":"https://api.github.com/users/scottkurz","html_url":"https://github.com/scottkurz","followers_url":"https://api.github.com/users/scottkurz/followers","following_url":"https://api.github.com/users/scottkurz/following{/other_user}","gists_url":"https://api.github.com/users/scottkurz/gists{/gist_id}","starred_url":"https://api.github.com/users/scottkurz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/scottkurz/subscriptions","organizations_url":"https://api.github.com/users/scottkurz/orgs","repos_url":"https://api.github.com/users/scottkurz/repos","events_url":"https://api.github.com/users/scottkurz/events{/privacy}","received_events_url":"https://api.github.com/users/scottkurz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-19T03:57:50Z","updated_at":"2018-12-19T03:57:50Z","closed_at":null,"author_association":"MEMBER","body":"As mentioned in issue #127 , the default monitoring interval of 500 ms isn't necessarily a good fit for the loose application, and this can result in the app being updated twice upon one recompilation.   Perhaps this is partly why WDT uses the mbean-based app monitoring for the loose app it manages.\r\n\r\nThough it might not be a big deal for a typical web app to rapidly stop/start twice... it can be a problem or at least an annoyance for an app with startup logic, particularly if the changes the developer is making intersect startup (or if the startup has side effects).\r\n\r\nIt seems simply using a longer monitoring interval, like 2 seconds\r\n`<applicationMonitor pollingRate=\"2000ms\" />`\r\nworks, or at least I'm unable to recreate the problem with relatively simple apps at 2 seconds.\r\n\r\nIs there a better value?\r\n\r\nShould we be undertaking the extra work of using the mbean notification (if so might be helpful to add to LMP too), or is 2 seconds good enough?    What happens when it's not..can the user override ?  Maybe we deal with that as-needed if it arises?\r\n\r\n\r\nhttps://stackoverflow.com/questions/16963012/maven-compiler-recompile-all-files-instead-modified/49700942#49700942"}}
{"actor":{"display_login":"scottkurz"}}