Bug 824850

Description of problem:

Sometimes, more frequently than comfortable, I get agent crashes when either stopping the plugin container or the entire agent.

The crash report always points to Augeas being the culprit:

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  com.sun.jna.Function.invokeInt(I[Ljava/lang/Object;)I+0
j  com.sun.jna.Function.invoke([Ljava/lang/Object;Ljava/lang/Class;Z)Ljava/lang/Object;+315
j  com.sun.jna.Function.invoke(Ljava/lang/Class;[Ljava/lang/Object;Ljava/util/Map;)Ljava/lang/Object;+214
j  com.sun.jna.Library$Handler.invoke(Ljava/lang/Object;Ljava/lang/reflect/Method;[Ljava/lang/Object;)Ljava/lang/Object;+341
j  $Proxy147.aug_close(Lnet/augeas/jna/AugPointer;)I+16
j  net.augeas.Augeas.close()I+16
j  org.rhq.plugins.augeas.AugeasConfigurationComponent.close()V+11
j  org.rhq.plugins.augeas.AugeasConfigurationComponent.finalize()V+1
v  ~StubRoutines::call_stub
j  java.lang.ref.Finalizer.invokeFinalizeMethod(Ljava/lang/Object;)V+0
j  java.lang.ref.Finalizer.runFinalizer()V+45
j  java.lang.ref.Finalizer.access$100(Ljava/lang/ref/Finalizer;)V+1
j  java.lang.ref.Finalizer$FinalizerThread.run()V+11

This leads me to believe we still somehow somewhere do a double close() on an augeas instance, leading to a segmentation fault.

Version-Release number of selected component (if applicable):
4.5.0-SNAPSHOT

How reproducible:
rather frequently

Steps to Reproduce:
1. Start the agent with the augeas based plugins available
2. import a platform, confirm hosts file and sudoers resources are imported, too
3. Do a several rounds of "pc stop" and "pc start" on the agent commandline
4. Start and shutdown agent repeatedly
  
Actual results:
Sometimes, the agent crashes during step 3 or 4.

Expected results:
no crashes, please

Additional info: