Skip to Content
0
Former Member
Jul 03, 2015 at 04:25 PM

Upgrading from 5.1.0.2 to 5.4 fails due to props table being too large

461 Views

Hi,

Is there a solution for the out of memory problem where the update process fails due to the large size of the props table?

We are aware of the legacy flag but surely there should be a solution?

As stated in the question, we are upgrading from 5.1.0.2 to 5.4.

We very quickly get messages such as : STATUS | wrapper | main | 2015/06/24 09:52:04.270 | Pinging the JVM took 767 seconds to respond. STATUS | wrapper | main | 2015/06/24 09:54:04.957 | Pinging the JVM took 877 seconds to respond. STATUS | wrapper | main | 2015/06/24 09:57:25.125 | Pinging the JVM took 1066 seconds to respond. STATUS | wrapper | main | 2015/06/24 09:57:25.125 | Pinging the JVM took 1057 seconds to respond.

and

INFO | jvm 1 | main | 2015/06/24 10:24:21.130 | Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space INFO | jvm 1 | main | 2015/06/24 10:24:21.130 | at java.io.BufferedOutputStream.(BufferedOutputStream.java:76) INFO | jvm 1 | main | 2015/06/24 10:24:21.130 | at java.io.BufferedOutputStream.(BufferedOutputStream.java:59)