Bug 900524 (JBPAPP6-911)
| Summary: | CLONE - Remote EJB clients hanging after EJBClient.createSession when using DIST | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Radoslav Husar <rhusar> |
| Component: | Clustering, EJB | Assignee: | Jaikiran Pai <jpai> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.0 | CC: | dimitris, jkudrnac, jpai, paul.ferraro, rhusar, sgilda, simone.gotti |
| Target Milestone: | --- | ||
| Target Release: | EAP 6.0.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBPAPP6-911 | ||
| Whiteboard: | eap601candidate | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-10-22 04:45:42 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 900611 | ||
|
Description
Radoslav Husar
2012-05-24 15:33:53 UTC
Link: Added: This issue Cloned from AS7-4881 Link: Added: This issue is incorporated by JBPAPP-7577 Link: Added: This issue relates to AS7-4854 Workflow: Removed: GIT Pull Request workflow Added: jira Security: Added: Public Docs QE Status: Added: NEW Labels: Added: eap6_need_triage Release Notes Docs Status: Added: Not Yet Documented Affects: Added: Release Notes Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Release Notes Text: Added: Remote EJB clients sometimes hang after calling method <code>EJBClient.createSession</code> when using DIST mode. The cause of this bug is still under investigation. Link: Added: This issue is related to JBPAPP-8455 Link: Added: This issue is a dependency of JBPAPP-9290 Link: Removed: This issue is incorporated by JBPAPP-7577 Labels: Removed: eap6_need_triage Added: eap601candidate Marking this as resolved for EAP 6.0.1 since Paul has fixed the upstream issue AS7-4881 Verified in DR1 build, closing. Does this need a release note for EAP 6.0.1? If so, the issue needs to be re-opened and the release notes flags set (Affects Release Notes, Not Yet Documented). If not, the issue needs to be re-opened and the release notes flag set to "Release notes not required". Ignore my previous comment. :-) Writer: Added: mistysj reopening to update release notes (these are still documented as known issues from the previous release) Writer: Removed: mistysj Added: Darrin Setting these to "Not Yet Documented" since they required updating from known to resolved issues. Release Notes Docs Status: Removed: Documented as Known Issue Added: Not Yet Documented Release Notes Docs Status: Removed: Not Yet Documented Added: Not Required Release Notes Text: Removed: Remote EJB clients sometimes hang after calling method <code>EJBClient.createSession</code> when using DIST mode. The cause of this bug is still under investigation. Release Notes Docs Status: Removed: Not Required Added: Needs More Info Hi Jaikiran, Can you provide some clarification of this issue for the EAP6.0.1 release notes. I followed the related issues and found https://community.jboss.org/message/747160 and https://issues.jboss.org/browse/ISPN-2153 - so maybe Paul Ferraro might be the right man to ask? Specifically I need clarification on: 1 - Was this specific to EJB clients or what that just the reported situation? Would this have occurred in other scenario? 2 - The root cause of this would seem to be that the KeyAffinityFactory was creating all KAS services in the same thread. Not sure if this meant that each key request was simply getting delayed (and thus appeared hung) or if it was some kind of lock issue that resulted ? 3 - The fix for this also isn't clear, is this now using multiple threads or is the "locking" fixed? (assuming it was a lock issue) Thanks. 1. This was specific to any SFSB creation (regardless of whether client is remote or local) where a DIST mode cache was used. 2. The root cause was my misunderstanding of how the executor supplied to KAS was used. I assumed that the thread was used only to pre-generate SFSB UUIDs as needed - and that a single thread could service all SFSBs. On the contrary, KAS uses this thread for the lifetime of the KAS, so it cannot be shared across multiple KASes. Consequently, DIST mode only worked correctly if your application had only 1 SFSB. Any subsequent SFSBs would hang waiting for a free thread that would never be available! 3. Now, each KAS gets it's own thread, instead of trying to share a thread (which is not possible). Thanks Paul! Release Notes Docs Status: Removed: Needs More Info Added: Not Yet Documented Release Notes Docs Status: Removed: Not Yet Documented Writer: Removed: Darrin Docs QE Status: Removed: NEW This issue was left open because of documentation after JIRA -> BZ migration and is already verified. Therefore closing as verified. |