Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-6622

"Packet too large" error thrown from inserting into Session document table

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-rc2, 2.0
    • Component/s: Development, Performance
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-2146Unique Contraints on KCB_ tables are too large for MySQL
      KULRICE-2483Fix KREN tables with unique constraints too large for MySQL
      KULRICE-97Add paging for large role/group memberships on KIM documents
      KULRICE-1352form is not restored from session for multipart request
      KULRICE-13726Rework Documentation and Contribution notes from KD sessions
      KULRICE-13408Very large HistoryFlows cause Out Of Memory error.
      KULRICE-12338Very large HistoryFlows cause OOM error.
      KULRICE-4443Allow workflow sessions to fail over between nodes to prevent document loss
      KULRICE-6916KRIM_ENTITY_CACHE_T.PRSN_NM is too small
      KULRICE-5341UserSession gets bound to a thread, and eDocLite documents are not establishing user session properly
    • Rice Module:
      KNS, KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      We were getting this occastionally in dev2, looks like it's coming from KRMS agenda editor.

      2012-02-02 18:09:38,623 [http-bio-8082-exec-24] u:admin/d: INFO  org.kuali.rice.krad.maintenance.MaintenanceUtils - starting checkForLockingDocument (by MaintenanceDocument)
      2012-02-02 18:09:39,044 [http-bio-8082-exec-24] u:admin/d: ERROR org.apache.ojb.broker.accesslayer.JdbcAccessImpl - 
      * SQLException during execution of sql-statement:
      * sql statement was 'INSERT INTO KRNS_SESN_DOC_T (SESN_DOC_ID,DOC_HDR_ID,PRNCPL_ID,IP_ADDR,SERIALZD_DOC_FRM,LAST_UPDT_DT,CONTENT_ENCRYPTED_IND) VALUES (?,?,?,?,?,?,?) '
      * Exception message is [Packet for query is too large (1419722 > 1048576). You can change this value on the server by setting the max_allowed_packet' variable.]
      * Vendor error code [0]
      * SQL state code [S1000]
      * Target class is 'org.kuali.rice.krad.bo.SessionDocument'
      * PK of the target object is [sessionId=c8b4439e-d916-4d95-b152-61bc85c58ae7, documentNumber=3011, principalId=admin, ipAddress=10.209.103.40]
      * Source object: org.kuali.rice.krad.bo.SessionDocument@618da[documentNumber=3011,sessionId=c8b4439e-d916-4d95-b152-61bc85c58ae7,lastUpdatedDate=2012-02-02 18:09:38.68,serializedDocumentForm={-84,-19,0,5,115,114,0,44,111,114,103,46,107,117,97,108,105,46,114,105,99,101,46,107,114,97,100,46,119,101,98,46,102,111,114,109,46,77,97,105,110,116,101,110,97,110,99,101,70,111,114,109,-81,109,-112,119,-79,-56,81,-128,2,0,2,76,0,19,100,97,116,97,79,98,106,101,99,116,67,108,97,115,115,78,97,109,101,116,0,18,76,106,97,118,97,47,108,97,110,103,47,83,116,114,105,110,103,59,76,0,17,109,97,105,110,116,101,110,97,110,99,101,65,99,116,105,111,110,113,0,126,0,1,120,114,0,45,111,114,103,46,107,117,97,108,105,46,114,105,99,101,46,107,114,97,100,46,119,101,98,46,102,111,114,109,46,68,111,99,117,109,101,110,116,70,111,114,109,66,97,115,101,30,101,101,-103,-28,-71,-26,-64,2,0,5,76,0,10,97,110,110,111,116,97,116,105,111,110,113,0,126,0,1,76,0,7,99,111,109,109,97,110,100,113,0,126,0,1,76,0,5,100,111,99,73,100,113,0,126,0,1,76,0,11,100,111,99,84,121,112,101,78,97,109,101,113,0,126,0,1,76,0,8,100,111,99,117,109,101,110,116,116,0,39,76,111,114,103,47,107,117,97,108,105,47,114,105,99,101,47,107,114,97,100,47,100,111,99,117,109,101,110,116,47,68,111,99,117,109,101,110,116,59,120,114,0,40,111,114,103,46,107,117,97,108,105,46,114,105,99,101,46,107,114,97,100,46,119,101,98,46,102,111,114,109,46,85,105,102,70,111,114,109,66,97,115,101,117,6,105,108,-124,-109,43,-30,2,0,25,90,0,15,100,101,102,97,117,108,116,115,65,112,112,108,105,101,100,90,0,14,114,101,110,100,101,114,70,117,108,108,86,105,101,119,90,0,13,118,97,108,105
      ...
      ...
      

      The above output goes on and on forever (eating up a huge amount of space in the logs.

      Root cause is:

      Caused by: com.mysql.jdbc.PacketTooBigException: Packet for query is too large (1454664 > 1048576). You can change this value on the server by setting the max_allowed_packet' variable.
      	at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3291)
      	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1983)
      	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2163)
      	at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2624)
      	at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2127)
      	at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2427)
      	at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2345)
      	at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2330)
      	at org.enhydra.jdbc.core.CorePreparedStatement.executeUpdate(CorePreparedStatement.java

        Activity

        Hide
        Eric Westfall added a comment -

        Jerry, can you close this issue once you've removed the offending code from KRAD?

        Show
        Eric Westfall added a comment - Jerry, can you close this issue once you've removed the offending code from KRAD?
        Hide
        Jessica Coltrin (Inactive) added a comment -

        Closing since these items are now in the release notes.

        Show
        Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

          People

          • Assignee:
            Jerry Neal (Inactive)
            Reporter:
            Eric Westfall
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel