Hey there all,
I'm having issues getting James up and running with MySQL/MariaDB since
v3.1.0.
The main exception it all comes down to is:
org.apache.openjpa.lib.jdbc.ReportingSQLException: Specified key was too
long; max key length is 3072 bytes
I uploaded the logs to my root - as over 64k of logs would be way to
much for a mail:
https://cryptearth.de/~cryptearth/james-server.txt
https://cryptearth.de/~cryptearth/wrapper.txt
Branches worked: 3.0.1-RC and master-3.0.x
Starting with 3.1.0 and later it fails with exception above.
I already asked google about this issue - and many suggestion some
config settings to allow longer primary keys and bigger packages - but
none of the suggested or supported options helped. So it's either a
issue in the database-resource file wich contains all the queries - or
the database-structure is to complex for MySQL/MariaDB to correctly
handle it.
This seems to be a recent change - a master-snapshot from June 3rd 2018
doesn't contain this issue and runs fine. Clone from Jan 1st 2019 has
it. So, somethings change in the past half year.
Connector: mysql-connector-java-8.0.13 from mysql.com (as the one from
dist-repo seems compiled with java-9 and throw a strange
NoSuchMethodError in NIO-package when run with java-8)
Database: mariadb-10.2.15
OS: openSUSE-Leap-15.0
Also: I still had to use openjdk-8 - neither lower versions nor higher
versions are neither able to compile nor run James. I guess that's some
issue with jigsaw. Can anyone confirm on this?
So long,
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
