Wasp probe used with CABI won't start. Controller: Max. restarts reached for probe 'wasp' (command = <startup java>)

Document ID : KB000047303
Last Modified Date : 07/06/2018
Show Technical Document Details
Issue:
 
 
Wasp probe used with a new CABI deployment won't start.
The following error is seen in the log:

Controller: Max. restarts reached for probe 'wasp' (command = <startup java>)
 
 
Environment:
UIM 8.x
Cabi 3.x
Cause:
A cause of this issue could be that the parameters for the Java allocated memory in the probe exceeded the actual memory  resources of the system where the probe is deployed.
Resolution:
Example:
With the the following configuration:

<startup>
   options = -Dfile.encoding=UTF-8
   <opt>
      java_mem_max = -Xmx6g
      java_mem_init = -Xms4g
      max_perm_size = -XX:MaxPermSize=512m
      java_stack_size = -Xss6m
      min_perm_size = -XX:PermSize=32m
      java_gc_conc_marc_sweep = -XX:+UseConcMarkSweepGC
      java_cms_classunloading_enable = -XX:+CMSClassUnloadingEnabled
   </opt>
</startup>

And the system with only "2GB memory available" the probe won't start with the error message.

To resolve the issue:
Low the memory parameters within capacity of the system resources.

<startup>
   options = -Dfile.encoding=UTF-8
   <opt>
      java_mem_max = -Xmx1g
      java_mem_init = -Xms256m
      max_perm_size = -XX:MaxPermSize=256m
      java_stack_size = -Xss6m
      min_perm_size = -XX:PermSize=32m
      java_gc_conc_marc_sweep = -XX:+UseConcMarkSweepGC
      java_cms_classunloading_enable = -XX:+CMSClassUnloadingEnabled
   </opt>
</startup>
Additional Information: