I'm with you, and also tried that - but for some reason there is a
change between the last working snapshot from june 3rd 2018 wich causes
a table structure alteration even if a working setup was created before
with that working snapshot. So it seems that james registeres the
current table structure doesn't match what it should be and tries to
"correct" it - and fails.
Anyhow - I should had known - cause I had similar issues when opensuse
changed from MySQL to MariaDB - took me a few days to recover the database.
Matt
Am 07.01.2019 um 15:19 schrieb Garry Hurley:
It is also worth noting that once the tables are created, you need not worry s
much, except for putting records in where the data exceeds the size of the field
Sent from my iPad
On Jan 7, 2019, at 7:17 AM, cryptearth <cryptea...@cryptearth.de> wrote:
Hello Benoit,
as always you're such a great help. It took me a bit to get MariaDB 10.3
running (repo for opensuse isn't well maintained - or at least doesn't follow
the guidelines required by opensuse leap 15.0) - at it worked instantly without
any warning. I didn't thought it could be MariaDB itself as I tested some other
dist-versions wich all contain different versions of MariaDB, but all 10.2 or
lower. So I thought maybe it could be an issue with connector (wich really is
when one tries to use the one provided by dist repo - wich has issues) or with
James itself changed in the past half year.
So, now I can spend the rest of me week upgrading to leap 15.0 with James 3.2.0
while watching agdq.
Thanks again, keep it up.
Matt
Am 07.01.2019 um 10:07 schrieb Benoit Tellier:
Hi
I think Marc did run in a similar issue, that he solved with a MariaDB
10.3 upgrade.
Maybe you can give this a try.
Cheers,
On 1/7/19 2:24 PM, cryptearth wrote:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
