The following failure was seen in the most recent ER4 build
[0m[31m23:33:19,053 SEVERE [org.overlord.rtgov.active.collection.ActiveCollectionManagerAccessor] (ServerService Thread Pool -- 55) ActiveCollectionManager is not available
[0m[31m23:33:19,054 SEVERE [org.overlord.rtgov.internal.acs.loader.jee.JEEACSLoader] (ServerService Thread Pool -- 55) Failed to obtain reference to ActiveCollectionManager
This is the result of code within the following classes:
ActiveCollectionManagerAccessor, ReportManagerAccessor, ActivityCollectorAccessor, InformationProcessorManagerAccessor, ActivityValidatorManagerAccessor, EPNManagerAccessor
Which has a hard coded timeout of 10s.
This should be replaced with code that is configurable with a larger default.
Other potential error messages are
20:14:02,803 SEVERE [org.overlord.rtgov.active.collection.ActiveCollectionManagerAccessor] (ServerService Thread Pool -- 92) ActiveCollectionManager is not available
20:14:02,809 SEVERE [org.overlord.rtgov.activity.validator.ActivityValidatorManagerAccessor] (ServerService Thread Pool -- 64) ActivityValidatorManager is not available
20:14:02,813 SEVERE [org.overlord.rtgov.activity.processor.InformationProcessorManagerAccessor] (ServerService Thread Pool -- 63) InformationProcessorManager is not available
20:14:02,814 SEVERE [org.overlord.rtgov.reports.ReportManagerAccessor] (ServerService Thread Pool -- 94) ReportManager is not available
20:14:02,806 SEVERE [org.overlord.rtgov.epn.EPNManagerAccessor] (ServerService Thread Pool -- 95) EPNManager is not available
Created attachment 807523 [details]
Kev's quick fix
This is Kev's quick fix that should get around the problem for beta. However I will investigate further to find a better solution that hopefully should avoid blocking the deployment of the artifacts.
Will open a separate bz for the longer term solution.
Verified in ER6 - configurable via proptery and default 30 secs
Gary Brown <firstname.lastname@example.org> updated the status of jira RTGOV-287 to Closed