IBM Support

IBM TRIRIGA Anywhere "Row size too large" error when uploading WorkTaskManagement-10.4.1.apk file

Troubleshooting


Problem

Getting the following error message when uploading WorkTaskManagement-10.4.1.apk into IBM Worklight Application Center: "File WorkTaskManagement-10.4.1.apk not uploaded.". On WebSphere logs we will see as well the message: “Row size too large”.

Symptom

In the IBM Worklight Application Center, we are getting a message that says:"File WorkTaskManagement-10.4.1.apk not uploaded.".

In the WebSphere SystemOut.log and SystemErr.log files we will see the following messages as well:

000000fa UploadService E Exception during resource upload. The transaction has been rolled back. See the nested
exceptions for details on the errors that occurred.
 000000fa UploadService E {
 "id": "5eaa5eff-85c8-4069-9baa-5c2b47f063f2",
 "message": "FWLAC0000E: A server error was detected.",
 "params": [
 ],
 "productVersion": "6.1.0"
}
com.ibm.puremeap.resources.exceptions.SystemException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
 at com.ibm.puremeap.resources.data.impl.ApplicationResourceHelper.createContent(ApplicationResourceHelper.java:502)
 at com.ibm.puremeap.services.UploadService.fileUploaded(UploadService.java:255)
 at com.ibm.puremeap.services.UploadService.__fileUploadedJSON__(UploadService.java:106)
(...)
Caused by: <openjpa-1.2.2-r422266:898935 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline. {prepstmnt 912309929 INSERT INTO APPLICATION_STORAGE (CONTENT, AP_FK) VALUES (?, ?) [params=(InputStream) java.io.ByteArrayInputStream@4785bd6e, (null) null]} [code=1118, state=42000] FailedObject: com.ibm.puremeap.jpa.entity.ApplicationStorageEntity@133d0df
 at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4246)
 at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4211)

Cause

The MySQL database innodb_log_file_size variable value needs to be set higher since apparently the redo-log overwrites the most recent checkpoint for large blobs.

Environment

IBM TRIRIGA Platform 3.4.1.1
IBM TRIRIGA Application 10.4.1.1
IBM WebSphere Application Server 8.5.5.1
Database MySQL Community Server 5.6.23

Diagnosing The Problem

D1) Go to IBM Worklight Application Center and upload file WorkTaskManagement-10.4.1.apk ;

D2) The following messages will be received: "File WorkTaskManagement-10.4.1.apk not uploaded.".

D3) WebSphere SystemOut.log and SystemErr.log files will show the following on a Java stack trace error message: “org.apache.openjpa.persistence.PersistenceException: Row size too large”.

Resolving The Problem

The resolution is to Increase the MySQL database variable innodb_log_file_size property to 256M. As per MySQL forum pages, apparently the redo-log overwrites the most recent checkpoint for large blobs. After that you need to restart your MySQL service (database). For more information on how to change MySQL 3rd party innodb_log_file_size variable, consult your DBA or MySQL forums.

Related Information

IBM TRIRIGA Anywhere

[{"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"IBM TRIRIGA Application Platform","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.4.1","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
17 June 2018

UID

swg21961308

Page Feedback