On 10/14/2013 07:06 PM, Larry O'Leary wrote:
Sounds like a bug in the Tomcat plug-in. The problem resource is
most
likely in the agent's persisted inventory. If you want to investigate
the bug further, I would suggest saving off a copy of the
data/inventory.dat file located in the agent installation.
Then, to attempt to clear it up, restart the agent using the --purgedata
command-line argument.
Ok now I have:
+++
2013-10-16 14:05:57,948 DEBUG [WorkerThread#0[10.33.144.7:39851]]
(enterprise.communications.command.server.CommandProcessor)-
{CommandProcessor.executed}Executed command - response is [Command
Response: isSuccessful=[false]; command=[null]; results=[null];
exception=[java.lang.reflect.InvocationTargetException:null ->
org.rhq.core.clientapi.agent.PluginContainerException:Plugin Error:
Resource Component for [Tomcat Connector] Resource with id [10149]: An
exception was thrown. ->
org.rhq.core.util.exception.WrappedRemotingException:Resource component
could not be retrieved for resource [Resource[id=10149,
uuid=e36692aa-663b-46a7-8c51-f148dca399a6, type={Tomcat}Tomcat
Connector, key=Catalina:port=8011,type=Connector, name=?-8011,
parent=Tomcat (8082)]] because the component is not started. Its state
is [STOPPED]]]
+++
Which is more what I was excepting.
Cheers
Jean-Frederic