appsgate2015 / appsgate

Appsgate
0 stars 5 forks source link

Dependancies stay stuck #410

Closed jrcourtois closed 9 years ago

jrcourtois commented 9 years ago

Pas de messages explicites dans la console :

11:44:09.793 [WebSocketWorker-87] DEBUG a.l.m.c.communication.WebSockeServer - msg --> {"method":"getGraph","args":[],"callId":"loadGraph","TARGET":"EHMI"} 11:44:09.793 [WebSocketWorker-87] DEBUG a.l.m.c.communication.WebSockeServer - notify listeners for new command event 11:44:09.794 [WebSocketWorker-87] DEBUG a.l.m.c.communication.WebSockeServer - retrieving command listener for EHMI target. 11:44:09.794 [WebSocketWorker-87] DEBUG a.l.m.c.communication.WebSockeServer - Command listener appsgate.lig.ehmi.impl.listeners.EHMICommandListener@afb3f98 found, invoking onReceivedCommand 11:44:09.795 [WebSocketWorker-87] DEBUG a.l.m.c.communication.WebSockeServer - Finished invoking listener appsgate.lig.ehmi.impl.listeners.EHMICommandListener@afb3f98 for command {"TARGET":"EHMI","args":[],"method":"getGraph","callId":"loadGraph","clientId":561544239}. 11:44:09.799 [pool-7-thread-1] INFO f.i.adele.apam.impl.ApamResolverImpl - Resolving relation schedulerService towards INSTANCE providing interface appsgate.lig.scheduler.SchedulerSpec from INSTANCE EHMIProxyImplInst (creation = LAZY, resolve = EXIST, missing policy = null) 11:44:09.800 [pool-7-thread-1] DEBUG f.i.adele.apam.impl.ApamResolverImpl - Calling manager UPDATEMAN 11:44:09.800 [pool-7-thread-1] DEBUG f.i.adele.apam.impl.ApamResolverImpl - resolveOneManager(...), manager resolve returns null 11:44:09.800 [pool-7-thread-1] DEBUG f.i.adele.apam.impl.ApamResolverImpl - Calling manager APAMMAN 11:44:09.801 [pool-7-thread-1] DEBUG f.i.adele.apam.impl.ApamResolverImpl - resolveOneManager(...), manager resolve returns fr.imag.adele.apam.Resolved@1783389b 11:44:09.801 [pool-7-thread-1] INFO f.i.adele.apam.impl.ApamResolverImpl - UPDATEMAN APAMMAN Selected : INSTANCE GoogleSchedulerInst 11:44:09.802 [pool-7-thread-1] ERROR a.lig.google.impl.GoogleAdapterImpl - Cannot get an access token for the calendar

Possiblement en configurant correctement mail et calendrier et en rebootant, le problème a disparu, pas sûr que ce soit la cause profonde. Mais sur le getGraph, on n'a aucun retour

BidoisMorgan commented 9 years ago

Normalement réglé avec un timer sur la demande des planifications