Hi,
I will take a look but exactly which resource is the "corresponding Resource"
in this case?
Is it the LDAP resource?
On Wednesday, February 19, 2020, 7:27:46 AM UTC, Francesco Chicchiriccò
wrote:
Hi, the key error message below is
Hi,
the key error message below is
org.apache.openjpa.persistence.PersistenceException: Data truncation: Data too
long for column 'message' at row 1 {prepstmnt 599588377 INSERT INTO TaskExec
(id, endDate, message, startDate, status, TASK_ID) VALUES (?, ?, ?, ?, ?, ?)}
[code=1406, state=22001]
It looks like that large binary data is all zeros, approx. 925728 bytes?
Here's hexdump -C: at the beginning:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ||
*
000e2020 31 36 3a 33 32 3a 33 35 2e 31 39 39 20 45 52 52 |16:32:35.199 ERR|
000e2030 4f 52 20 6f 72
Hi,
I forgot to mention that just before that first message below, there is a very
large line with what appears to be all binary data.
Jim
On Tuesday, February 18, 2020, 5:48:06 PM UTC, oh...@yahoo.com
wrote:
Hi,
We are starting to test running Syncope with larger sets of users and
Hi,
We are starting to test running Syncope with larger sets of users and when we
tested today (with adding 500 users to already existing 500), we are seeing the
following errors:
org.springframework.orm.jpa.JpaSystemException: The transaction has been rolled
back. See the nested exceptions
