[WG: Sakai QA] Trunk nightly is not usable

[Aaron Zeckoski]

There is not currently a JIRA for that. It is sort of the "state of the
union" (as it were) and even though it is probably an architectural
weakness, there are some good(ish) reasons for it. In an ideal world, we
would have no circular dependencies in kernel and no use of CM lazy loads
but that's not as serious an issue as the use of covers in kernel was (that
was fixed though).

I think it is probably better (but more painful) to deal with them as
needed, like this case.
-AZ



On Mon, Apr 14, 2014 at 7:41 AM, Neal Caidin <neal.caidin at apereo.org> wrote:

> Thanks Aaron!  All three scenarios work this morning.
>
> Is there a Jira for the circular dependencies?
>
> -- Neal
>
>
>
>   Aaron Zeckoski <azeckoski at unicon.net>
>  April 13, 2014 at 10:25 AM
> It's a service start failure (as any widespread system failure tends
> to be). I updated the ticket with some details from the logs.
>
> Here is the kicker:
> This is tricky because it is a startup order issue caused by these
> services depending on each other. Basically:
>
> MemoryService uses SecurityService, EventTrackingService,
> ServerConfigurationService
> SecurityService uses MemoryService, EventTrackingService,
> ServerConfigurationService (and others)
> EventTrackingService uses SecurityService (and others)
>
> This could be tolerable as long as none of these services are used in
> the init. Unfortunately, SecurityService inits it's caches. Nothing
> uses SecurityService in the init EXCEPT the new MemoryService because
> it needs to insert it into the selected implementation (this is the
> new change).
>
> In essence, these circular dependencies between the various services
> make it impossible for Spring to establish a viable startup order and
> this results in the NPE.
>
> The real fix for this is quite complex because the service dependency
> graph is cyclical and basically needs to be untangled and have the
> cycles removed (of which there are... many). The quick-ish fix for
> this is to change the MemoryService to lazy load the SecurityService
> and EventTrackingService.
>
> -AZ
>
>
>
>   Neal Caidin <neal.caidin at apereo.org>
>  April 13, 2014 at 9:44 AM
> Hi,
>
> One cannot create an account [1], one cannot log in as admin [2], one
> cannot log in with an existing account (did not open a ticket for this
> one).
>
> [1] https://jira.sakaiproject.org/browse/SAK-26087
>
> [2] https://jira.sakaiproject.org/browse/SAK-26088
>
> Cheers,
> Neal
>
>
> --
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org
> Skype me! (but let me know in advance for the first interaction) - nealkdin
>
>


-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20140414/393d0c6c/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1247 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20140414/393d0c6c/attachment-0002.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20140414/393d0c6c/attachment-0003.jpg