Bug 910193
Summary: | ejb timer service creates empty directories for all ejbs including those without timers | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Brad Maxwell <bmaxwell> |
Component: | EJB | Assignee: | Jaikiran Pai <jpai> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.1 | CC: | cdewolf, chaowan, dimitris, jlivings, jmartisk, jpai, rdickens, sdouglas, smumford |
Target Milestone: | ER3 | ||
Target Release: | EAP 6.1.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
In previous versions of Red Hat JBoss Enterprise Application Platform 6, it was found that the EJB timer service was being created for every bean that was eligible to have a timer service, rather than being limited to beans actually using a timer. As a result the service would create unnecessary directories to store timer data when the service started.
This issue has been resolved and a timer service is now only started for beans that have timeout or schedule methods. Other EJBs use a non-functional timer service that can still be looked up in JNDI (as per the Java EE specification) but does not schedule timers (as the EJB does not have a timeout method).
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-16 20:24:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brad Maxwell
2013-02-12 00:24:39 UTC
Stuart Douglas <stuart.w.douglas> updated the status of jira AS7-6357 to Resolved Verified in EAP 6.1.1.ER3 Jaikiran, can I request some deeper explanation of how this was rectified and what was causing it? Ideally we need to know what the problem was in the code, how this manifested in the product (in this case, creating empty folders), what was changed to fix it, and how the product behaves now (I assume it no longer creates unnecessary folders). Thanks for any assistance you can offer. The timer service was being created for every EJB that was eligible to have a timer service, and as a result it would eagerly create a directory to store the timer data when the service started. Now we only start a real timer service for EJB's that have timeout or schedule methods, other EJB's just use a non-functional timer service, that can still be looked up in JNDI as per the Java EE specs, but does not allow you to schedule timers (as the EJB does not have a timeout method). Thanks for the input Stuart. I've added a release note and marked it for inclusion in the document. Please comment if the text above is inaccurate in any way. |