You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a critical issue for my development but I have considered it convenient to report it. Basically the services are executed correctly, but the Log Monitor does not treat them in the right way and I'm not sure why. In fact, the operation is adequate when the calls modify a value of the StatusValue type, but not when the value to be modified is an Integer.
I attach the code used and the error log below.
ProvidedService turnOn = new ProvidedService(PROVIDED_SERVICE_NAMESPACE + actuator.getLocalName() + "-TURN_ON");
turnOn.setProperty(Service.PROP_NUMBER_OF_VALUE_RESTRICTIONS, Integer.valueOf(-1));
turnOn.addInstanceLevelRestriction(MergedRestriction.getFixedValueRestriction(DeviceService.PROP_CONTROLS, actuator), PPATH_CONTROLS);
turnOn.getProfile().addChangeEffect(PPATH_VALUE_DEVICE, new Integer(100));
profiles[i++] = turnOn.getProfile();
Error found in LogMonitor:
java.lang.IllegalArgumentException: ERROR in matching log tool: startMatching, id not available.
at org.universAAL.tools.logmonitor.service_bus_matching.LogMonitor.getMatchmaking(LogMonitor.java:204)
at org.universAAL.tools.logmonitor.service_bus_matching.LogMonitor.startMatching(LogMonitor.java:233)
at org.universAAL.tools.logmonitor.service_bus_matching.LogMonitor.handleServiceStrategyMessage(LogMonitor.java:167)
at org.universAAL.tools.logmonitor.service_bus_matching.LogMonitor.log(LogMonitor.java:113)
at org.universAAL.tools.logmonitor.LogMonitor.log(LogMonitor.java:60)
at org.universAAL.middleware.container.utils.LogUtils.log(LogUtils.java:108)
at org.universAAL.middleware.container.utils.LogUtils.logTrace(LogUtils.java:367)
at org.universAAL.middleware.service.impl.ServiceStrategy.logTrace(ServiceStrategy.java:998)
at org.universAAL.middleware.service.impl.ServiceStrategy.handle(ServiceStrategy.java:1229)
at org.universAAL.middleware.bus.model.BusStrategy$HandlerThread.run(BusStrategy.java:63)
Error found in LogMonitor:
java.lang.IllegalArgumentException: ERROR in matching log tool: handleServiceRealizationMessage, id not available.
at org.universAAL.tools.logmonitor.service_bus_matching.LogMonitor.getMatchmaking(LogMonitor.java:204)
at org.universAAL.tools.logmonitor.service_bus_matching.LogMonitor.handleServiceRealizationMessage(LogMonitor.java:145)
at org.universAAL.tools.logmonitor.service_bus_matching.LogMonitor.log(LogMonitor.java:115)
at org.universAAL.tools.logmonitor.LogMonitor.log(LogMonitor.java:60)
at org.universAAL.middleware.container.utils.LogUtils.log(LogUtils.java:108)
at org.universAAL.middleware.container.utils.LogUtils.logTrace(LogUtils.java:367)
at org.universAAL.middleware.service.impl.ServiceMatcher.matchRestrictions(ServiceMatcher.java:247)
at org.universAAL.middleware.service.impl.ServiceMatcher.matches(ServiceMatcher.java:54)
at org.universAAL.middleware.service.impl.ServiceRealization.matches(ServiceRealization.java:331)
at org.universAAL.middleware.service.impl.ServiceStrategy.matches(ServiceStrategy.java:1790)
at org.universAAL.middleware.service.impl.ServiceStrategy.handle(ServiceStrategy.java:1231)
at org.universAAL.middleware.bus.model.BusStrategy$HandlerThread.run(BusStrategy.java:63)
Error found in LogMonitor:
java.lang.IllegalArgumentException: ERROR in matching log tool: endMatching, success: false, id not available.
at org.universAAL.tools.logmonitor.service_bus_matching.LogMonitor.getMatchmaking(LogMonitor.java:204)
at org.universAAL.tools.logmonitor.service_bus_matching.LogMonitor.endMatching(LogMonitor.java:260)
at org.universAAL.tools.logmonitor.service_bus_matching.LogMonitor.handleServiceStrategyMessage(LogMonitor.java:173)
at org.universAAL.tools.logmonitor.service_bus_matching.LogMonitor.log(LogMonitor.java:113)
at org.universAAL.tools.logmonitor.LogMonitor.log(LogMonitor.java:60)
at org.universAAL.middleware.container.utils.LogUtils.log(LogUtils.java:108)
at org.universAAL.middleware.container.utils.LogUtils.logTrace(LogUtils.java:367)
at org.universAAL.middleware.service.impl.ServiceStrategy.logTrace(ServiceStrategy.java:998)
at org.universAAL.middleware.service.impl.ServiceStrategy.handle(ServiceStrategy.java:1236)
at org.universAAL.middleware.bus.model.BusStrategy$HandlerThread.run(BusStrategy.java:63)
The text was updated successfully, but these errors were encountered:
Hello,
This is not a critical issue for my development but I have considered it convenient to report it. Basically the services are executed correctly, but the Log Monitor does not treat them in the right way and I'm not sure why. In fact, the operation is adequate when the calls modify a value of the
StatusValue
type, but not when the value to be modified is anInteger
.I attach the code used and the error log below.
The text was updated successfully, but these errors were encountered: