2164946 - java.lang.OutOfMemoryError: OutOfMemoryError in offline deployment at AS Java startup

• After deployment the AS Java startup fails in the offline deployment phase with an "out of memory" event.
• The /usr/sap/<SID>/<inst_nr>/work/dev_jstart file contain the failed deployment:
   
  F  [Thr 01] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).
  F  [Thr 01] *** LOG => Run level 1 completed.
  F  [Thr 01] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).
  F  ********************************************************************************
  F  *** ERROR => Node 'deployment' failed with exit code 67.
  F  ***
  F  *** Please see section 'Failures in the 'deploying offline components' phase'
  F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
  F  ********************************************************************************
  F  [Thr 01] *** LOG => exiting (exitcode 22002, retcode 1).
  
  
• The /usr/sap/<SID>/<inst_nr>/work/dev_deployment contains the root cause:
  
   408868K->408867K(466432K), 0.6690039 secs]
  ***ERROR (:0): OutOfMemoryError: Could not allocate 0 bytes
  J  java.lang.OutOfMemoryError: GC overhead limit exceeded
  ...
  F 
  F  ********************************************************************************
  F  *** ERROR => Java node 'Deploy_offline' terminated with exit code 67.
  F  ***
  F  *** Please see section 'Java program exit codes'
  F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
  F  ********************************************************************************
  F 
  F  [Thr 2571] *** LOG => exiting (exitcode 67, retcode 1).

SAP NetWeaver AS Java 7.1x and higher

OutOfMemory, exit code 22002, exit code 67, offline deployment, SAP AS Java , KBA , BC-JAS-DPL , Deployment , BC-JAS-SF , Startup Framework , How To