Closed pandel closed 2 weeks ago
Hi!
From which version are you upgrading?
I upgraded a few weeks ago the last time, but sadly, I don't know the exact version numbers. But it was already ejbca:8
and mariadb:10.3
images. Sorry that I can't be more specific...
But as I did not have any problems over the whole time using and upgrading the images, I did not think about it this time, too. Maybe I should have...
Could you try rolling back to previous images to see where the problem would be?
I am not in the office right now for a while, but I'll try to and report.
So, I retried to downgrade the ejbca
image to 8.2.0-1
. That worked so far, but the error message is still
Caused by: javax.resource.ResourceException: IJ031083: Wrong driver class [org.mariadb.jdbc.Driver] for this connection URL [jdbc:mysql://mariadb:3306/ejbca]
The ejbca
container simply isn't able to connect to the mariadb
container, even though a simply mysql -hmaridb -uroot -pXXXXX
command does the trick. It seems as if the connectiong string is broken somehow with the 10.11
version of mariadb.
EDIT: GOT IT!!! (Downgraded to images ejbca:8.2.0-1
and mariadb:10.6
before)
It was this line
jdbc:mysql://mariadb:3306/ejbca
which had to be changed to this line
jdbc:mariadb://mariadb:3306/ejbca
The mariadb jdbc client 3.4.0 seems to need this exactly. I absolutely don't understand why this happened now and not a lot earlier, but I am glad it worked.
Name and Version
bitnami/ejbca:8
What architecture are you using?
amd64
What steps will reproduce the bug?
Hi!
I updated the
bitnami\ejbca:8
andbitnami\mariadb:10.11
images to the latest version (of today, 21.08.2024) and restarted the docker compose stack. But now, the ejbca container won't start. It does not deploy theejbca.ear
and if I look into the wildfly log, I get the following:The corresponding section in the
standalone.xml
is as follows:The deployed driver file is
mariadb-java-client-3.4.1.jar
. It does not matter if I setEJBCA_DATABASE_FLAVOR
tomariadb
ormysql
.I did not change anything in my
.env
ordocker-compose.yml
.What can I do?
Regards, Holger
What is the expected behavior?
Container EJBCA starts successfully.
What do you see instead?
Container hangs at
ejbca | ejbca 10:27:11.30 INFO ==> Deploying EJBCA application
Additional information
No response