Error updating upm ([engine.jdbc.spi.SqlExceptionHelper] logExceptions Out of memory)
Asked by jadbaz:

Hello,

I received an error while trying to update upm on my Confluence 6.3.1 server from version 2.2.4 to version 2.2.5.

Below is the tail of atlassian-confluence.log when this happened.

++atlassian-confluence.log++

```
2017-08-25 15:46:29,290 INFO [UpmAsynchronousTaskManager:thread-4] [atlassian.plugin.manager.DefaultPluginManager] updatePlugin Updating plugin 'com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin' from version '2.22.4' to version '2.22.4'
2017-08-25 15:46:29,291 INFO [UpmAsynchronousTaskManager:thread-4] [atlassian.plugin.manager.DefaultPluginManager] broadcastPluginDisabling Disabling com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin
2017-08-25 15:46:33,846 ERROR [pool-919-thread-1] [engine.jdbc.spi.SqlExceptionHelper] logExceptions Out of memory (Needed 8112696 bytes)
 -- url: /rest/plugins/self-update/1.0/ | referer: http://wiki.activeidentity.com/plugins/servlet/upm | traceId: bc47e40aeec0cd3c | userName:?X
2017-08-25 15:46:33,846 WARN [pool-919-thread-1] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions:
 ->[PluginReadWriteTx]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #239037332)
 -- url: /rest/plugins/self-update/1.0/ | referer: http://wiki.activeidentity.com/plugins/servlet/upm | traceId: bc47e40aeec0cd3c | userName:?X
```

A few more questions:

1. Isn't it odd that the log is saying "from version '2.22.4' to version '2.22.4'"
2. Does this have to do with inno_db_log_file_size? I'm 100% sure I fixed that. show variables on my RDS instance returns: innodb_log_file_size=26214400

Here is my [Confluence server information](https://www.dropbox.com/s/r7is8m72s8452e7/ai_confluence_system_information_2017_08_25.xlsx?dl=0)


Answers:
author: Nic Brough -Adaptavist-
body: Not your innodb log file, it seems to need more heap memory in the JVM.

comments: author: jadbaz
body: Thank you,

But wouldn't it have shown in System Information?

System info when the error occurred:

* Maximum Heap Size 1024 MB
* Total Allocated Memory 1024 MB
* Used Memory 556 MB
* Free Allocated Memory 467 MB
* Total Free Memory 467 MB

And here's my system memory:

total used free:  
3950 2427 312

I have several gigs of disk space, if that's somehow relevant.  

It could be that the memory drops only while updating but bounces back, I tried doing this a few times and refreshing System Information. I managed to get the free heap down to 27%. Maybe it goes even lower but I didn't manage to grab it and I don't wanna go just yet into serious profiling.

But still, how did it not manage to allocate 7.7 MB?


author: Nic Brough -Adaptavist-
body: No, system info is just a snapshot taken as the page renders.

It may be just that one process that's going too high. Remember it allocates in chunks, not the whole lot in one go.

Is it possible to **temporarily** increase your heap size by say .5G? The -Xmx setting in setenv.sh/bat


author: AnnWorley
body: [@jadbaz](/t5/user/viewprofilepage/user-id/1139982) Please see my comment on [Error while updating upm plugin (logExceptions Out of memory)](https://community.atlassian.com/t5/Confluence-questions/Error-while-updating-upm-plugin-logExceptions-Out-of-memory/qaq-p/630754). Please update this thread to let us know the results.