Resolution:
Since garbage collections happens using a low priority thread,  java objects not being released in time.
In such scenarios you can tune the garbage collection parameters to increase the throughput
of the Admin Server.

Add the below property in your tibcoadmin_&ltdomainName>.tra and restart the Admin
Server.
      >&gtjava.extended.properties=-XX:NewSize=64m -XX:MaxNewSize=128m

(A general guideline for this value is 25% of -Xmx)

Turning verbose gc ON using the below option and starting the Admin Server from the command
prompt will give you GC snap shot (if support needs to review).

>&gtjava.extended.properties=-Xincgc  -XX:NewSize=128m  -XX:MaxNewSize=128m  -verbose:gc

NewSize  The lower bound number of megabytes of memory
MaxNewSize  The upper bound number of megabytes of memory.
(This value should not exceed one-half the total JVM heap size)

Continious large simulataneous deployments complains"java.lang.OutOfMemoryError: Java heap space"in the Admin GUI and logs . Even after increasing java Heap Size, there is continious memroy growth in the Admin Server.