[SOLVED] JDBC issue after upgrade to 4.3.2

Setup, Configuration and Use Migration
1

Hello
today I dared to upgrade from 4.1.2 to 4.3.2 in docker container.

First glance to openhab.log shows a lot of issues with mariadb stroing items.
The DB had been used for years without issues.

This is the error message:

2025-02-10 19:45:00.308 [WARN ] [jdbc.internal.JdbcPersistenceService] - JDBC::store: Unable to store item
org.openhab.persistence.jdbc.internal.exceptions.JdbcException: Not initialized, unable to find table for item Kostal_Nord_DEVICE_PVSTRING_1_POWER
        at org.openhab.persistence.jdbc.internal.JdbcMapper.getTable(JdbcMapper.java:359) ~[?:?]
        at org.openhab.persistence.jdbc.internal.JdbcMapper.storeItemValue(JdbcMapper.java:217) ~[?:?]
        at org.openhab.persistence.jdbc.internal.JdbcPersistenceService.internalStore(JdbcPersistenceService.java:174) ~[?:?]
        at org.openhab.persistence.jdbc.internal.JdbcPersistenceService.lambda$1(JdbcPersistenceService.java:146) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
        at java.lang.Thread.run(Thread.java:840) [?:?]

The log is flooded with these entries for all items I wanna store.

How can I find the problem?
Any help is highly appreciated

This is the debug log:

2025-02-10 20:02:00.367 [DEBUG] [persistence.jdbc.internal.JdbcMapper] - JDBC::storeItemValue: item=Kostal_Nord_DEVICE_PVSTRING_1_POWER (Type=NumberItem, State=0, Label=null, Category=energy) state=0 date=null
2025-02-10 20:02:00.367 [DEBUG] [persistence.jdbc.internal.dto.ItemVO] - JDBC:ItemVO tableName=item0174; newTableName=null;
2025-02-10 20:02:00.367 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::storeItemValueProvider: item 'Kostal_Nord_DEVICE_PVSTRING_1_POWER' as Type 'NUMBERITEM' in 'item0174' with state '0'
2025-02-10 20:02:00.367 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::storeItemValueProvider: itemState: '0'
2025-02-10 20:02:00.367 [DEBUG] [persistence.jdbc.internal.dto.ItemVO] - JDBC:ItemVO setValueTypes dbType=DOUBLE; javaType=class java.lang.Double;
2025-02-10 20:02:00.367 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::storeItemValueProvider: newVal.doubleValue: '0.0'
2025-02-10 20:02:00.367 [DEBUG] [istence.jdbc.internal.db.JdbcBaseDAO] - JDBC::doStoreItemValue sql=INSERT INTO item0174 (time, value) VALUES( NOW(3), ? ) ON DUPLICATE KEY UPDATE VALUE= ? value='0.0'
2025-02-10 20:02:00.368 [DEBUG] [jdbc.internal.JdbcPersistenceService] - JDBC: Stored item 'Kostal_Nord_DEVICE_PVSTRING_1_POWER' as '0' in SQL database at Mon Feb 10 20:02:00 CET 2025 in 1 ms.
2

Can you try to find the log entries from when the binding is started? You can either restart openHAB, or just restart the bundle from a karaf console:

bundle:restart org.openhab.persistence.jdbc
3

I found this after restarting the bundle

2025-02-10 21:19:11.509 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : For dependency $000, optional: false; to bind: [[RefPair: ref: [{org.openhab.core.config.core.ConfigOptionProvider, org.openhab.core.persistence.PersistenceServiceRegistry}={service.id=369, service.bundleid=218, service.scope=bundle, osgi.ds.satisfying.condition.target=(osgi.condition.id=true), component.name=org.openhab.core.persistence.internal.PersistenceServiceRegistryImpl, service.config.label=Persistence, component.id=252, service.config.factory=false, default=rrd4j, service.config.category=system, service.config.description.uri=system:persistence, service.pid=[org.openhab.persistence, org.openhab.persistence]}] service: [null]]]
2025-02-10 21:19:11.509 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : For dependency osgi.ds.satisfying.condition, optional: false; to bind: [[RefPair: ref: [{org.osgi.service.condition.Condition}={service.id=6, service.bundleid=0, service.scope=singleton, service.pid=0.org.osgi.service.condition.ConditionImpl, osgi.condition.id=true}] service: [null]]]
2025-02-10 21:19:11.510 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : getting activate: activate
2025-02-10 21:19:11.510 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : Locating method activate in class org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension
2025-02-10 21:19:11.510 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : Declared Method org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension.activate([interface org.osgi.service.component.ComponentContext]) not found
2025-02-10 21:19:11.510 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : Locating method activate in class org.openhab.core.io.console.extensions.AbstractConsoleCommandExtension
2025-02-10 21:19:11.510 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : Declared Method org.openhab.core.io.console.extensions.AbstractConsoleCommandExtension.activate([interface org.osgi.service.component.ComponentContext]) not found
2025-02-10 21:19:11.510 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : Locating method activate in class java.lang.Object
2025-02-10 21:19:11.511 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : Declared Method java.lang.Object.activate([interface org.osgi.service.component.ComponentContext]) not found
2025-02-10 21:19:11.511 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : activate method [activate] not found, ignoring
2025-02-10 21:19:11.511 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : Set implementation object for component
2025-02-10 21:19:11.511 [DEBUG] [nternal.console.JdbcCommandExtension] - bundle org.openhab.persistence.jdbc:4.3.2 (321)[org.openhab.persistence.jdbc.internal.console.JdbcCommandExtension(458)] : Changed state from satisfied to active
4

Unfortunately I can’t figure out from that what’s going on. A small thing to check just entered my mind: Do you by any chance have a manually installed JAR for the jdbc persistence service?

5

No it is the bundle comming with the container.

I did a backup of my whole VM and repeated the update and this error was gone.
Now there are big issues with shelly binding but I guess i have to open a new threat.

Thanks anyway for your support.