Red Hat Bugzilla – Bug 970177
Cannot browse the GUI while the plugin scan is running
Last modified: 2013-09-11 05:53:50 EDT
Created attachment 756367 [details]
Exception stack trace
Description of problem:
Cannot browse the GUI if the plugin scan task does not execute quickly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Upload a new (version of a) plugin with various resource types (ie as7 plugin)
2.Wait for the plugin scan task to start (look at the server logs)
3.While the server is updating resource types, try to browse the GUI
Cannot browse the GUI and the server logs shows the attached stack trace
Can browse the GUI
The plugin scan is currently triggered with an EJB timer in a @Singleton bean (org.rhq.enterprise.server.core.StartupBean). Those beans by default have container managed concurrency. Without any annotations, the container serializes calls to the bean. So the AuthenticationFilter timeouts on its try to call org.rhq.enterprise.server.core.StartupLocal#isInitialized
Comments from IRC
<mazz> BTW, there are other @Singleton SLSBs we should examine for this same kind of thing
<mazz> I see two that we should look at
<mazz> (that's something jsanda put together for the storage stuff)
<mazz> and org.rhq.enterprise.server.auth.prefs.SubjectPreferencesCacheBean
(In reply to Thomas Segismont from comment #1)
> <mazz> BTW, there are other @Singleton SLSBs we should examine for this same
> kind of thing
> <mazz> and org.rhq.enterprise.server.auth.prefs.SubjectPreferencesCacheBean
That SubjectPreferencesCacheBean is OK - I remember doing this. Its explicitly marked as CONTAINER and we use the EJB LOCK annotations to ensure we have read/write locking around the appropriate places.
We should ask John S. just to confirm that SessionManagerBean is OK.
Fixed in master
Author: Thomas Segismont <email@example.com>
Date: Wed Jun 5 10:57:29 2013 +0200
Bug 970177 - Cannot browse the GUI while the plugin scan is running
Moved two @Singleton beans concurrency management setting to type 'BEAN'. In both cases state is initialized on startup and is thread safe.
Bulk closing of old issues now that HRQ 4.9 is in front of the door.
If you think the issue has not been solved, then please open a new bug and mention this one in the description.