Wasp probe used with new CABI deployment want start. gets error: Controller: Max. restarts reached for probe 'wasp' (command = <startup java>)

Document ID : KB000047303
Last Modified Date : 14/02/2018
Show Technical Document Details
 
 

Problem:

Wasp probe used with new CABI deployment want start.
The probe gets the following errorin the log:
Controller: Max. restarts reached for probe 'wasp' (command = <startup java>)
 

Solution:

The problem in this case was that the machine that the wasp and CABI were installed on only had 2 Gigs of ram.
The wasp probe had the following configurations set:
<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>

When these were changed to the below the wasp came up as expected

<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>