Community
Participate
Working Groups
StartupTracker has a default timeout of 3600 seconds for every bundle that is not started. This makes the startup of Virgo in exceptional situations extremely slow.
Created attachment 186731 [details] Configurable wait limit for bundle&kernel start
Comment on attachment 186731 [details] Configurable wait limit for bundle&kernel start Hristo agrees that the new property should be for the whole kernel startup and not per bundle.
Created attachment 186804 [details] Wait limit is configurable and for the whole kernel
Comment on attachment 186804 [details] Wait limit is configurable and for the whole kernel The bundle error message is wrong. It can report "Bundle X did not start within 0 seconds". The fix Hristo and I have agreed is to remove the error message.
Created attachment 186816 [details] Configurable start limit, removed "bundle did not start" message
Added configurable startup wait limit with commit 28f7df1e1cb214c46fd277964665477cba7e092e The property that can be used to configure the commit is org.eclipse.virgo.kernel.startup.wait.limit
Please remember to do the doc change too.
Commit 0ac3b040a394d9924553ecb101dcfff9d8b00a39 adds documentation about kernel properties