Bug 1015363 - ActiveCollectionManager is not available
Summary: ActiveCollectionManager is not available
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: RT Governance
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER4
: 6.0.0
Assignee: Gary Brown
QA Contact: Jiri Sedlacek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-04 03:21 UTC by kconner
Modified: 2015-08-02 23:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-06 15:26:12 UTC
Type: Bug


Attachments (Terms of Use)
Kev's quick fix (12.32 KB, patch)
2013-10-04 09:28 UTC, Gary Brown
no flags Details | Diff


Links
System ID Priority Status Summary Last Updated
Red Hat One Jira Issue Tracker RTGOV-287 Major Closed Accessor wait interval needs to be configurable 2018-01-11 05:39:29 UTC

Description kconner 2013-10-04 03:21:01 UTC
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.

Comment 2 kconner 2013-10-04 06:18:12 UTC
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

Comment 3 Gary Brown 2013-10-04 09:28:44 UTC
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.

Comment 4 Gary Brown 2013-10-04 12:59:01 UTC
Will open a separate bz for the longer term solution.

Comment 8 Jiri Pechanec 2013-10-18 14:24:11 UTC
Verified in ER6 - configurable via proptery and default 30 secs

Comment 9 JBoss JIRA Server 2014-07-02 09:18:47 UTC
Gary Brown <gary@brownuk.com> updated the status of jira RTGOV-287 to Closed


Note You need to log in before you can comment on or make changes to this bug.