Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange errors with CHMIProxy and CoreObject #75

Closed
snybril opened this issue Jul 11, 2014 · 1 comment
Closed

Strange errors with CHMIProxy and CoreObject #75

snybril opened this issue Jul 11, 2014 · 1 comment
Assignees
Labels
Milestone

Comments

@snybril
Copy link
Collaborator

snybril commented Jul 11, 2014

During startup 👍 13:57:04.323 [pool-8-thread-1] ERROR appsgate.lig.chmi.impl.CHMIProxyImpl -- If getCoreType method error trace appeare below it is because the service or the device doesn't implement all methode inthe CoreObjectSpec interface.
and a stack Trace (corresponding to EnOcean, Upnp or other devices)

ava.lang.NullPointerException
at appsgate.lig.ehmi.impl.EHMIProxyImpl.__M_getCoreObjectPlaceId(EHMIProxyImpl.java:426)
at appsgate.lig.ehmi.impl.EHMIProxyImpl.getCoreObjectPlaceId(EHMIProxyImpl.java)
at appsgate.lig.ehmi.impl.listeners.ObjectUpdateListener.notifyUpdate(ObjectUpdateListener.java:69)
at appsgate.lig.chmi.impl.CHMIProxyImpl.__M_notifyAllUpdatesListeners(CHMIProxyImpl.java:421)
at appsgate.lig.chmi.impl.CHMIProxyImpl.notifyAllUpdatesListeners(CHMIProxyImpl.java)
at appsgate.lig.chmi.impl.CHMIProxyImpl.__M_addAbstractObject(CHMIProxyImpl.java:154)
at appsgate.lig.chmi.impl.CHMIProxyImpl.addAbstractObject(CHMIProxyImpl.java)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.felix.ipojo.util.Callback.call(Callback.java:237)
at fr.imag.adele.apam.apform.impl.RelationCallback.invoke(RelationCallback.java:67)
at fr.imag.adele.apam.apform.impl.ApamInstanceManager$Apform.fireCallbacks(ApamInstanceManager.java:635)
at fr.imag.adele.apam.apform.impl.ApamInstanceManager$Apform.setLink(ApamInstanceManager.java:559)
at fr.imag.adele.apam.impl.ComponentImpl.createLink(ComponentImpl.java:195)
at fr.imag.adele.apam.impl.ApamResolverImpl.resolvePromotion(ApamResolverImpl.java:515)
at fr.imag.adele.apam.impl.ApamResolverImpl.resolveLink(ApamResolverImpl.java:809)
at fr.imag.adele.apam.impl.PendingRequest.resolve(PendingRequest.java:397)
at fr.imag.adele.apam.impl.DynaMan.resolveDynamicRequests(DynaMan.java:297)
at fr.imag.adele.apam.impl.DynaMan.addedComponent(DynaMan.java:130)
at fr.imag.adele.apam.ApamManagers.notifyAddedInApam(ApamManagers.java:244)
at fr.imag.adele.apam.impl.InstanceImpl.register(InstanceImpl.java:215)
at fr.imag.adele.apam.impl.ImplementationImpl.createInstance(ImplementationImpl.java:198)
at appsgate.lig.enocean.ubikit.adapter.UbikitAdapter.__M_instanciateItem(UbikitAdapter.java:470)
at appsgate.lig.enocean.ubikit.adapter.UbikitAdapter.instanciateItem(UbikitAdapter.java)
at appsgate.lig.enocean.ubikit.adapter.UbikitAdapter.access$000(UbikitAdapter.java:71)
at appsgate.lig.enocean.ubikit.adapter.UbikitAdapter$ItemInstanciation.__M_run(UbikitAdapter.java:592)
at appsgate.lig.enocean.ubikit.adapter.UbikitAdapter$ItemInstanciation.run(UbikitAdapter.java)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
13

Behavior seems normal after !

@snybril
Copy link
Collaborator Author

snybril commented Jul 11, 2014

Those error appeared because of exception during mongoDB link (error message is wrong)

@snybril snybril closed this as completed Jul 11, 2014
@jrcourtois jrcourtois added this to the v1.6 milestone Oct 16, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants