User Tools

Site Tools



Ahsay Backup Software

Backup Set Types

Supported Storage

Features in OBM / ACB

Features in CBS

Brand and Customize



Performance Testing

FAQs and Known Issues

Can't Find What You Need?


ISSUE: GC (Allocation Failure) in catalina log after upgrading AhsayCBS to version 8

Article ID: 8034
Reviewed: 20/03/2019

Product Version:
AhsayCBS: or above
OS: All platforms

Problem Description

After upgrading the AhsayCBS server application to version 8, the following informative message are received in the catalina.out server log file:

DD-MMM-YYYY [CMS-concurrent-preclean-start]
DD-MMM-YYYY [CMS-concurrent-preclean: 0.002/0.002 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
DD-MMM-YYYY [GC (Allocation Failure) DD-MMM-YYYY [ParNewDD-MMM-YYYY [CMS-concurrent-abortable-preclean: 0.038/0.145 secs] [Times: user=0.21 sys=0.01, real=0.14 secs]: 126976K->4096K(126976K), 0.0938717 secs] 543109K->441169K(618432K), 0.0939455 secs] [Times: user=0.12 sys=0.00, real=0.09 secs]
DD-MMM-YYYY hh:mm:ss.xxx0000: [GC (CMS Final Remark) [YG occupancy: 6543 K (126976 K)]DD-MMM-YYYY [GC (CMS Final Remark) DD-MMM-YYYY [ParNew: 6543K->3499K(126976K), 0.0162797 secs] 443617K->444720K(619684K), 0.0163264 secs] [Times: user=0.03 sys=0.00, real=0.02 secs]
DD-MMM-YYYY [Rescan (parallel) , 0.0232216 secs]DD-MMM-YYYY [weak refs processing, 0.0258297 secs]DD-MMM-YYYY [class unloading, 0.0080231 secs]DD-MMM-YYYY [scrub symbol table, 0.0067435 secs]DD-MMM-YYYY [scrub string table, 0.0010432 secs][1 CMS-remark: 441220K(492708K)] 444720K(619684K), 0.0814779 secs] [Times: user=0.12 sys=0.00, real=0.09 secs]
DD-MMM-YYYY [CMS-concurrent-sweep-start]
DD-MMM-YYYY [GC (Allocation Failure) DD-MMM-YYYY [ParNew: 126379K->4095K(126976K), 0.0755672 secs] 299409K->192823K(619684K), 0.0756426 secs] [Times: user=0.08 sys=0.00, real=0.08 secs]
DD-MMM-YYYY [CMS-concurrent-sweep: 0.301/0.376 secs] [Times: user=0.66 sys=0.01, real=0.38 secs]
DD-MMM-YYYY [CMS-concurrent-reset-start]
DD-MMM-YYYY [CMS-concurrent-reset: 0.001/0.001 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
DD-MMM-YYYY [GC (Allocation Failure) DD-MMM-YYYY [ParNew: 126975K->4096K(126976K), 0.0824005 secs] 248798K->144191K(619684K), 0.0824743 secs] [Times: user=0.09 sys=0.00, real=0.08 secs]


This is an informative message returned by the Tomcat web server (AhsayCBS version 8 is bundled with Tomcat version 8.5.34, whereas AhsayCBS version 7 is bundled with Tomcat version 7.0.81).


Even though the message say allocation failure, precisely, "GC (Allocation Failure)" means that the Java garbage collector was initiated, ran out of space in the heap, then tried to allocate more memory.  The GC (Garbage Collection) process was completed successful.

Administrator can safely ignore the message (except if you see "java.lang.OutOfMemoryError: Java heap space"), no user interaction is required.


gc, garbage, collecion, java, heap, memory

public/8034_issue/gc_allocation_failure.txt · Last modified: 2019/03/20 17:19 by edward.chan