Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 370345

Summary: Installed plugins go into invalid state for no reason.
Product: [ECD] Orion Reporter: Malgorzata Janczarska <malgorzata.tomczyk>
Component: ClientAssignee: Simon Kaegi <simon_kaegi>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: john.arthorne, ken_walker, mamacdon, simon_kaegi, Szymon.Brandys
Version: unspecified   
Target Milestone: 0.4 RC2   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Bug Depends on:    
Bug Blocks: 361010    

Description Malgorzata Janczarska CLA 2012-02-01 11:31:54 EST 
In random situations some plugins get into an invalid state giving message as in attachment 205222 [details], although they did not change on server side. Those plugins act as they wouldn't be installed, but reloading them makes everything work again.
This probably caused those bugs: Bug 361010, Bug 367326.
Comment 1 Malgorzata Janczarska CLA 2012-02-02 08:02:47 EST 
I noticed that if a plugin is correctly loaded and its contents changes than changes are visible. But if you change a plugin in a way it can't load correctly and then change it back to its original state than this change is not visible, plugin stays invalid and you need to reload it manually.
I suppose the same thing happens when timeout in loading plugins occurs once. The plugin goes into the invalid state and than even if it could load later without timeout it doesn't.
Comment 2 Mark Macdonald CLA 2012-02-02 15:06:47 EST 
I've seen the same issue with fileClientPlugin and authPlugin, but I don't know what caused them to become invalid -- I wasn't changing their code.

Could this happen because the server hosting the plugins was messed up? For example if orion.eclipse.org runs out of handles, would that cause the plugin load to fail, and send it into the invalid state?
Comment 3 Simon Kaegi CLA 2012-02-12 23:12:51 EST 
Targetting RC2 as a test priority.
Comment 4 Simon Kaegi CLA 2012-02-22 12:42:41 EST 
I've been testing this by using sites that I stop and start regularly and believe this is expected behavior. e.g. plugins are disabled because the site is unreachable.

Plugins can timeout however we are at least in slightly better shape this release with our metadata expiring more regularly.