Loading...

XML

Word

Printable

Blocked:
False
Blocked Reason:
None
Ready:
False
Release Note Text:
Documentation issue as the DB column definition is the root cause
Steps to Reproduce:

Hide

Use a MariaDB image with podman

`podman run --name mariadb -e MYSQL_ROOT_PASSWORD=mysql -e MYSQL_DATABASE=jdg -e MYSQL_USER=jdg -e MYSQL_PASSWORD=jdg -p 8080:8080 -p 3306:3306 -d mariadb`

Configure the server with a persistent cache
Run a client adding an entry<String,String> to the cache
Check console or read with the client
Restart the server
Check console or read with the client (do not write the entry again)

Show
Use a MariaDB image with podman `podman run --name mariadb -e MYSQL_ROOT_PASSWORD=mysql -e MYSQL_DATABASE=jdg -e MYSQL_USER=jdg -e MYSQL_PASSWORD=jdg -p 8080:8080 -p 3306:3306 -d mariadb` Configure the server with a persistent cache Run a client adding an entry<String,String> to the cache Check console or read with the client Restart the server Check console or read with the client (do not write the entry again)
Intelligence Requested:
Market:

If a <string-keyed-jdbc-store> is used as persistence the cache is readable by REST or HotRod clients as well as with the console.

But after restarting the server any access will cause an Exception as long as the entries are not written again.

Caused by: org.infinispan.protostream.MalformedProtobufException: Found an invalid protobuf tag (0) having a field number smaller than 1

clones

ISPN-14430 string-keyed-jdbc-store can not recover after server restart

is related to

JDG-5858 [Docs]Add a list of which column type we should use for the supported databases