Tuesday, May 27, 2003 06:19 AM
OOMs occur when you're trying to allocate a lot of objects and are never freeing them.
Is your update being performed within a transaction? If so, this can create a lot of transactional objects for state. If possible, do not use a transaction for this update.
I understand that you usually want to havea transaction for this type of thing, so removing the transaction might not be an option.
Does this only happen when you do this large update?
Another option is to raise the amound of memory available to the JVM from the command-line. You may have to use your server's configuration tool or edit a shell script to change this value.