Queryable persistence service missing - even when active and functional #84
Comments
…ivated again fixes openhab/openhab-distro#84 Signed-off-by: Kai Kreuzer <kai@openhab.org>
|
Confirmed fixed in OH2 (Build 97 from cloudbees) |
|
Great to hear, thanks for the feedback! |
|
@kaikreuzer This issue seems to be back. I had to manually clear the cache of Karaf, and since then I have 2016-08-05 20:16:05.232 [ERROR] [.eclipse.smarthome.model.persistence] - [org.eclipse.smarthome.core.persistence.manager(90)] The addPersistenceService method has thrown an exception |
|
To be complete: based on the Karaf console, the bundles (persistence, rrd4j,...) are loaded/started |
|
Is this a recent distro? Could you check the version of your compat1x bundle? It should be 2.0.0.201608032032 |
|
Yeah - 2-3 weeks old snapshot. With the version you mention. I will try to remove the cache again. |
|
Removed cache. same result.... |
|
starting the bundle yields 2016-08-05 21:49:32.481 [ERROR] [org.eclipse.smarthome.ui ] - [org.eclipse.smarthome.ui.chart.defaultprovider(111)] The addPersistenceService method has thrown an exception Is there a .jar version problem? |
|
@kaikreuzer same problem on org.eclipse.smarthome.core.persistence.internal.rest making all UI non-responsive |
|
@kaikreuzer based on the exception stack thrown, it seems there is a problem with eclipse-archived/smarthome@c564054 or related commit, no? |
|
The error states: java.lang.AbstractMethodError: org.openhab.core.persistence.internal.QueryablePersistenceServiceDelegate.getName()Ljava/lang/String; After your refactoring, there is no .persistence.internal.QueryablePersistenceServiceDelegate anymore, and that (I suppose) the replacing interface https://github.com/eclipse/smarthome/blob/master/bundles/core/org.eclipse.smarthome.core.persistence/src/main/java/org/eclipse/smarthome/core/persistence/QueryablePersistenceService.java does not define getName() either.... My runtime has 0.9.0.201607082129 for org.eclipse.smarthome.model.persistence and related bundles |
|
If it would help, here is my complete bundle list START LEVEL 100 , List Threshold: 50 ID | State | Lvl | Version | Symbolic name10 | Active | 80 | 2.0.0.201606252309 | org.openhab.binding.miele |
|
@kaikreuzer For my understanding, it is a fact that the core classes for the runtime are never updated via karaf features, and require a regular/blank installation of the runtime? e.g. org.eclipse.smarthome.ui.internal.chart update sits in feature esh-ui, but the reference to mvn:org.eclipse.smarthome.ui/org.eclipse.smarthome.ui/0.9.0-SNAPSHOT is part of the repo-list, and thus, will not be updated? If the case, is this something that will change in the future? if non-core features get updated, it would be logical that the core bundles they depend on are also automatically updated, no? |
Ah, you are living in the future :-) I personally always use the offline distro and deleting the cache of the online distro is nothing that I ever considered a use case. We still have to work out a mechanism of how to update from one version to another, this is nothing that is in place yet. I have no clue why some of the ESH bundles in your installation are old and some are recent; maybe it is due to what remote repos the online distro has configured and what gets installed. It needs to be analyzed and sorted out. For now I would recommend that if you clear the cache that you also replace the runtime folder by the most recent version - then the bundles should hopefully be in sync. |
|
Yeah - the core bundles are 3 weeks old but the features are 3/8/16.... The upgrade process is messy, I am cooking a script with it will never fit the bill for everyone.... |
|
Feel free to copy/fork/otherwise abuse my script that already handles this. I always use the online distribution, so any time I do an update, I clear out the cache and force libs and dependencies to re-download. The problem with this is all the dependency loading at start up. Lots of things are not there at start, and the the log has a lot of errors in it. Once everything is loaded and calmed down, I restart and the log is usually clean after. This is how I am able to keep the online distro up to date and to keep from having problems like @kgoderis . Another person modified it for windows. |
As requested in the forums, issue added.
I have am having an issue trying to use .maximumSince(now.toDateMidnight) in a rule (as well as .minimumSince)
I am using the JDBC persistence service and able to persist data to a mysql database with no issues.
I am able to render a chart using the jdbc persistence service as well.
So connectivity is definitely up to the db.
When the rule runs to calculate my max and min values I get the following error in the logs:
(here is the exact rule line:
postUpdate(Weather_Temp_Max, Weather_Temperature.maximumSince(now.toDateMidnight).state))There is no queryable persistence service registered with the name 'jdbc'If I turn on tracing for the Jdbc stuffs I see the following (showing up in the log eariler - before the rule is run)
2016-01-15 12:17:45.719 [DEBUG] [jdbc.internal.JdbcPersistenceService] - JDBC::getName: returning name 'jdbc' for queryable persistence service.At this point I am at a loss as to how to try and figure out whats going on. I am new to openHab and haven't quite wrapped my head around the environment and all the dependencies. I realise things are really in flux right now with OH2, but I was wondering if there were any tips as to how to try and track this issue down.
I have seen this with the mysql persistence service as well so I don't think its an isolated issue to the Jdbc persistence service.
I am using the following builds
OH2 (Build #84 from cloudbees)
org.openhab.persistence.jdbc-1.9.0-SNAPSHOT.jar (Build #1128 from cloudbees - with a fix to the MANIFEST.MF to include javax.sql and javax.naming so it will load correctly)
The text was updated successfully, but these errors were encountered: