Packet for query is too large - Entity identifying

Hello all,

 

our application server, JBoss, is logging the following message every 5 minutes:

 

11:01:17,784 INFO [stdout] (ElementEventQueue.QProcessor-1) 2019-01-30 11:01:17,783 [ElementEventQueue.QProcessor-1] ERROR org.hibernate.util.JDBCExceptionReporter - Packet for query is too large (7190476 > 4194304). You can change this value on the server by setting the max_allowed_packet' variable.
11:01:17,787 INFO [stdout] (ElementEventQueue.QProcessor-1) 2019-01-30 11:01:17,787 [ElementEventQueue.QProcessor-1] INFO com.appiancorp.cache.sail.StatefulSailCacheImpl - Unable to spool expired entry to database: f5ddd8b4-4264-40d1-bad5-075669dadcab:8d250068-3502-40f2-9982-ac867097279b placing back into memory cache

 

How can I identify which entity or query is causing this issue? I tried the following, but none of these procedures worked:

- I tried to serarch in all the objects in our environment the uuids f5ddd8b4-4264-40d1-bad5-075669dadcab or 8d250068-3502-40f2-9982-ac867097279b. No object exists with this uuid.

- I exported all the datasources in our environment and I searched f5ddd8b4-4264-40d1-bad5-075669dadcab and 8d250068-3502-40f2-9982-ac867097279b in all teir xml files. No matches obtained.

  Discussion posts and replies are publicly visible

Parents Reply Children
No Data