If you drop a bad plugin jar into ../plugins it will generate server log messages while trying to wait for it to become valid (assuming it's in a mid-copy state). When that times out it throws an exception which bubbles up out of the container. The net effect is that the invalid plugin is still put into the in-mem cache. With the new delete/purge ability it's possible to get rid of the bad plugin from db and file system, but it remains in the cache and generated verbose logging every minute. I think either the exception should be caught and the plugin not placed in the cache, or on delete, maybe purge, it should be removed from the cache. I need someone more familiar to review this, jsanda or mazz.
something very recently came up re: the plugin cache in the plugin scanner code - john s. fixed it (about a week or two ago). we can discuss possible solution
john is fixing this
I believe this issue is slightly different from bug 683545.
Added a finally block to ensure the AgentPluginScanner.scanned list always gets cleared even if ProductPluginDeployer throws an exception when ProductPluginDeployer.pluginDetected() is called. commit hash: 2378d5452826890b0c62b4b93e95b5c24e276be9
created a "bad" plugin by starting with a "good" plugin and then making the rhq-plugin.xml invalid. added the plugin. did not see any residual or invalid plugins in Administration-->plugin.
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.