Bug 914758
| Summary: | Acquire semaphore was interrupted | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Dmytro Pogrebniuk <dpogrebn> |
| Component: | EJB | Assignee: | Jaikiran Pai <jpai> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | csuconic, dimitris, mnovak, pslavice |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-16 11:52:29 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
Dmytro Pogrebniuk
2013-02-22 17:03:41 UTC
Apparently the endpoint was undeployed. this is not HornetQ's code... So, this can't be a hornetQ issue Caused by: javax.ejb.EJBException: JBAS014517: Acquire semaphore was interrupted at org.jboss.as.ejb3.pool.strictmax.StrictMaxPool.get(StrictMaxPool.java:111) [jboss-as-ejb3-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:47) [jboss-as-ejb3-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:226) [jboss-as-ejb3-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] ... 39 more this NullPointerException thing.. it's probaly 2.3.0.CR3... there was a fix on stopping the handler versus a synchronization issue that was fixed on 2.3.0.Final (it was part of the SpecJMS fix) which would affect this... maybe this is not happening any longer? This bz describes symptoms reported in bz#912688 and bz#959641. I'll close this bz as duplicate of bz#959641 since the root cause will be solved there. *** This bug has been marked as a duplicate of bug 959641 *** |