Resolution:
Description:
============
The following errors are seen in the HawkAgent.log :  "Failure contacting Hawk Agent", and "OutOfMemoryError: GC overhead limit exceeded"

Environment:
===========
Operating system(s): All
TIBCO Runtime Agent: 5.6 or higher


Symptoms:
========
The following error is seen in the HawkAgent.log on the Administrator side.

java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.util.zip.ZipInputStream.getUTF8String(ZipInputStream.java:347)
at java.util.zip.ZipInputStream.getFileName(ZipInputStream.java:436)
at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:255)
at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:82)
at java.util.jar.JarInputStream.getNextEntry(JarInputStream.java:118)
at java.util.jar.JarInputStream.getNextJarEntry(JarInputStream.java:149)
at com.tibco.archive.helpers.JarInputStreamClassPathResolver.(JarInputStreamClassPathResolver.java:49)
...

And the project will contains large custom JAR(s).

Cause:
=====
The HawkAgent is running out of memory while trying to extract large custom JAR files from the project at deployment time.


Resolution:
==========
1). Increase the Java heap size in the hawkagent_&ltdomain>.tra file by updating the properties java.heap.size.max and java heap.size.initial. The values will depend upon available memory. 
    Bouncing hawkagent is required to pick up the new configurations.

2). Update the project so that the custom JAR files are placed outside of the archive. This can be achieved by adding a File Alias resource to the project and unchecking the Deploy box.

References:
==========
TIBCO Designer -> User's Guide -> Chapter 4 Sharing Resources with Other Projects-> Creating an Alias Library.

The following errors are seen in the HawkAgent.log :"Failure contacting Hawk Agent", and "OutOfMemoryError: GC overhead limit exceeded".