This post is basically informative.
We had a situation where two zip files and some string information was being persisted to a MySQL database. The interesting fact was that the processing would complete without problem on a Windows XP system, but then turning arouond and running the exact same code with the exact same zip files on our Solaris server system would indeed get the Subject 'Out of memory' exception.
In process of elimination we eliminated the MySQL as the problem (therefore this is not in a MySQL forum).
The only significant difference between the two systems was that the XP system had jdk1.6.0_10 and the Solaris system had jdk1.5.0_14. When Solaris was updated to the Java 6 the processing worked as it did on the XP system.
More of the stack trace follows:
[Toplink Warning]: 2009.02.03 07:02:04.274--UnitOfWork(3022623)--Exception [TOPLINK-4002]
oracle.toplink.essentials.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Out of memory (Needed 12002512 bytes)
Error Code:5
Call: INSERT INTO ziptable (zip_filename, zip_file, zip_id, zip_filename2, zip_cmd, zip_file2, zip_crc, zip_type) VALUES (?, ?, ?, ?, ?, ?, ?, ?)
bind => [filename2, [B@fefe3f, id, filename, command, [B@e61a35, 2198567692, zipType]
Query: InsertObjectQuery(com.company.mysql.persistence.Ziptable[zipId=null])
Hope this is helpful information to pass along.
