[ 
http://jira.amdatu.org/jira/browse/AMDATU-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10271#comment-10271
 ] 

Ivo Ladage - van Doorn commented on AMDATU-174:
-----------------------------------------------

What I noticed was this:

Suddenly you get an error and stacktrace in the console when opening the 
dashboard since it tries to retrieve the gadgetspec for the login gadget with 
the wrong URL; http://null:null/... So this means hostname and portnr are null, 
which are initialized in the updated() method of this managed service. The 
first time I noticed this error, I attached the debugger and stopped/started 
the login gadget bundle, causing a restart of the managed service 
(LoginGadgetImpl). I noticed that upon starting the service, it did hit the 
init() method, but it never entered the updated() method. And so m_hostname and 
m_portnr remained null. The problem remained after several restarts of the 
bundle, it vanished after restarting Amdatu and removing the work directory.
The second time I noticed this issue, I could reproduce the issue only once: 
the http://null:null... error appeared, but when restarting the service the 
gadget was properly registered.

> Investigate the ManagedService.updated() method call not always being invoked 
> for required configuration dependencies.
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMDATU-174
>                 URL: http://jira.amdatu.org/jira/browse/AMDATU-174
>             Project: Amdatu
>          Issue Type: Bug
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>
> Several reports have indicated that sometimes the updated() method is not 
> invoked before a component with a required configuration dependency is 
> initialized. This does not yet seem reproducable, but is worth investigating 
> because it can lead to all kinds of problems. If it is indeed a bug, it needs 
> to be resolved in the Dependency Manager.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to