SAP Knowledge Base Article - Preview

2319148 - OutOfMemory on system update while upgrading from hybris 5.0 to 5.7

Symptom

  • Upgrade from hybris 5.0.0 and to hybris version 5.7.0
  • The update system has following error log :

INFO | jvm 2 | main | 2016/04/11 15:23:07.202 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [Initialization] ############################################################### INFO | jvm 2 | main | 2016/04/11 15:23:07.202 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [Initialization] Updating system ... INFO | jvm 2 | main | 2016/04/11 15:23:07.202 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [Initialization] ############################################################### INFO | jvm 2 | main | 2016/04/11 15:23:07.202 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [Initialization] Please wait. This step can take some minutes to complete. INFO | jvm 2 | main | 2016/04/11 15:23:07.202 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [Initialization] If you do not receive any feedback on this page in this time, consult the applicationserver logs for possible errors. INFO | jvm 2 | main | 2016/04/11 15:23:07.302 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [Initialization] Updating system... INFO | jvm 2 | main | 2016/04/11 15:23:07.302 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [Initialization] ### Starting type system update INFO | jvm 2 | main | 2016/04/11 15:23:07.703 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [Initialization] >>> Updating schema (and type system)... INFO | jvm 2 | main | 2016/04/11 15:23:07.703 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [DbTypeSystemImpl] Fetching type system related entities INFO | jvm 2 | main | 2016/04/11 15:23:07.903 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [DbTypeSystemImpl] 336 deployments have been fetched in 157.0 ms INFO | jvm 2 | main | 2016/04/11 15:23:08.203 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [DbTypeSystemImpl] 1122 composedtypes have been fetched in 289.4 ms INFO | jvm 2 | main | 2016/04/11 15:23:08.704 | �[m INFO | jvm 2 | main | 2016/04/11 15:23:12.308 | �[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [DbTypeSystemImpl] 25345 attributess have been fetched in 4.126 s INFO | jvm 2 | main | 2016/04/11 15:23:12.408 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [DbTypeSystemImpl] 22 atomictypes have been fetched in 95.10 ms INFO | jvm 2 | main | 2016/04/11 15:23:12.608 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [DbTypeSystemImpl] 495 collectiontypes have been fetched in 143.6 ms INFO | jvm 2 | main | 2016/04/11 15:23:12.608 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [DbTypeSystemImpl] 54 maptypes have been fetched in 84.91 ms INFO | jvm 2 | main | 2016/04/11 15:23:12.809 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [DbTypeSystemImpl] 870 enumerationvalues have been fetched in 184.7 ms INFO | jvm 2 | main | 2016/04/11 15:23:12.909 | �[m�[0;32mINFO [ajp-bio-8009-exec-4] [10.16.170.254] [DbTypeSystemImpl] 222 numberseries have been fetched in 74.92 ms INFO | jvm 2 | main | 2016/04/11 15:23:13.409 | �[m INFO | jvm 2 | main | 2016/04/11 15:28:06.518 | 2016-04-11 15:28:06 [3cefd8b5] info [native] Found high autosensor overhead, might hint to time drift problem, tsCounter: 7623 STATUS | wrapper | main | 2016/04/11 15:34:43.283 | Pinging the JVM took 2 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:36:26.224 | Pinging the JVM took 4 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:36:37.544 | Pinging the JVM took 7 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:36:46.156 | Pinging the JVM took 6 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:36:54.669 | Pinging the JVM took 6 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:37:03.079 | Pinging the JVM took 5 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:37:13.093 | Pinging the JVM took 6 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:37:21.611 | Pinging the JVM took 5 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:37:30.020 | Pinging the JVM took 4 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:37:38.331 | Pinging the JVM took 4 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:37:48.342 | Pinging the JVM took 5 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:37:56.653 | Pinging the JVM took 4 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:38:04.863 | Pinging the JVM took 3 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:38:12.874 | Pinging the JVM took 2 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:38:22.487 | Pinging the JVM took 2 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:38:30.700 | Pinging the JVM took 1 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:38:56.235 | Pinging the JVM took 9 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:39:12.157 | Pinging the JVM took 6 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:39:20.263 | Pinging the JVM took 5 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:39:29.774 | Pinging the JVM took 6 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:39:37.684 | Pinging the JVM took 5 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:39:45.698 | Pinging the JVM took 3 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:39:53.607 | Pinging the JVM took 2 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:40:02.924 | Pinging the JVM took 2 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:40:10.842 | Pinging the JVM took 1 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:40:35.570 | Pinging the JVM took 8 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:40:43.077 | Pinging the JVM took 6 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:40:50.484 | Pinging the JVM took 4 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:40:57.896 | Pinging the JVM took 3 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:41:07.007 | Pinging the JVM took 3 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:41:14.825 | Pinging the JVM took 1 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:41:39.562 | Pinging the JVM took 8 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:41:47.169 | Pinging the JVM took 6 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:41:54.678 | Pinging the JVM took 5 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:42:02.390 | Pinging the JVM took 3 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:42:11.705 | Pinging the JVM took 4 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:42:19.518 | Pinging the JVM took 2 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:42:34.436 | Pinging the JVM took 8 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:42:43.554 | Pinging the JVM took 8 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:42:51.066 | Pinging the JVM took 7 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:42:58.676 | Pinging the JVM took 5 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:43:38.128 | Pinging the JVM took 35 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:43:38.128 | Pinging the JVM took 26 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:43:38.128 | Pinging the JVM took 17 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:43:38.128 | Pinging the JVM took 8 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:44:18.681 | Pinging the JVM took 39 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:44:18.681 | Pinging the JVM took 30 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:44:18.681 | Pinging the JVM took 21 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:44:18.681 | Pinging the JVM took 12 seconds to respond. STATUS | wrapper | main | 2016/04/11 15:44:18.681 | Pinging the JVM took 3 seconds to respond. INFO | jvm 2 | main | 2016/04/11 15:50:13.694 | 2016-04-11 15:50:13 [2a2898b5] info [native] Creating Memory Dump upon ResourceExhausted Notification: Java heap space INFO | jvm 2 | main | 2016/04/11 15:50:28.513 | 2016-04-11 15:50:28 [2a2898b5] info [native] Run Garbage Collector INFO | jvm 2 | main | 2016/04/11 15:50:28.513 | 2016-04-11 15:50:28 [2bd238b5] info [native] Got ResourceExhausted Notification: Java heap space, not creating Memory Dump

  • the legacy update is turned off by default ( initialization.legacy.mode=false )


Read more...

Environment

Upgrading from hybris version <= 5.2 to hybris version >= 5.3

Product

SAP Hybris Commerce 6.0 ; SAP hybris Commerce 5.0.3 ; SAP hybris Commerce 5.0.4 ; SAP hybris Commerce 5.7 ; SAP hybris Commerce Suite 5.2 ; SAP hybris Commerce Suite 5.3 ; SAP hybris Commerce Suite 5.4 ; SAP hybris Commerce Suite 5.5 ; SAP hybris Commerce Suite 5.5-1 ; SAP hybris Commerce Suite 5.6 ; hybris Commerce Suite 5.0 ; hybris Commerce Suite 5.1 ; hybris Commerce Suite 5.1.1

Keywords

out of memmory, OOM, GC, garabage collection, updatesystem, system update, props, typesystemprops, upgrade, migration, migrate
, KBA , CEC-COM-CPS-COR , SAP Commerce Core , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.