Description of problem: An exception thrown inside the ResourceComponent.start() method will get rethrown as InvalidPluginConfigurationException which is not being caught inside the InventoryManager. As a result, the agent will stop the plugin container and will try to restart it a couple of times, eventually giving up. How reproducible: always Steps to Reproduce: 1. Inventory apache, unset the pinging URL in its connection properties 2. Stop the apache server 3. Restart the agent Actual results: agent will not start up again with an exception coming from the apache plugin Expected results: the agent starts up, only the apache resource will be stopped Additional info:
commit 47a5ff64c25c0f4d8648ed8101152d17863abe4d Author: Lukas Krejci <lkrejci> Date: Tue Jun 7 18:40:22 2011 +0200 BZ 711484 - catching all the exceptions that can happen during resource activation
Note that for the repro steps to work, the SNMP module must NOT be setup in the apache instance.
Verified on build 149 (Version: 4.1.0-SNAPSHOT Build Number: 04f721e) Inventoried Apache which is not configured for SNMP module. After unsetting the URL property, stopped the apache server and restarted the agent successfully. The avail command at the agent prompt displays the Apache resource as down. Marking as verified.
marking VERIFIED BZs to CLOSED/CURRENTRELEASE
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE