Customers with larger collection environments will encounter problems with collections. Typically, symptoms will include sporadic inventory and performance collections and collection alarms.
The FglAM does not have the resources necessary to perform all the collections in the timeframe necessary.
Step 1
If you get the error "java.lang.OutOfMemoryError: Java heap space" you need to add more memory to the FglAM JVM.
A FglAM uses these values by default where the minimum is 22mb and the maximum is 256mb.
-Xms256m
-Xmx256m
To increase the values, follow the steps below:
Stop your FglAM
Version 6.8 / 5.6.7 and lower
Version 7.0 / 5.6.10 and higher
Step 2
If you get the error “The Upstream-data cache settings appear to be too low for the amount of data passing though.” You need to increase the disk space available for caching.
By default the FglAM uses 1024 for caching up and downstream data. vFoglight Storage transmits a large amount of data and this setting might need to be adjusted to 102400
To increase the values, follow the steps below:
Stop your FglAM
<config:upstream max-queue-size="-1" max-disk-space="1024" max-batch-size="500"/>
<config:downstream max-queue-size="-1" max-disk-space="1024" max-batch-size="500"/>
5) Change the max-disk-space to 102400 as shown below.
<config:upstream max-queue-size="-1" max-disk-space="102400" max-batch-size="500"/>
<config:downstream max-queue-size="-1" max-disk-space="102400" max-batch-size="500"/>
c:\Program Files\Quest Software\vFoglight\fglam\state\default\cache\
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center