[jboss-jira] [JBoss JIRA] (AS7-6862) EjbUtilities is used without regard for dependencies

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/AS7-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766366#comment-12766366 ] 

RH Bugzilla Integration commented on AS7-6862:
----------------------------------------------

wfink at redhat.com made a comment on [bug 950864|https://bugzilla.redhat.com/show_bug.cgi?id=950864]

Description of problem:
If a SFSB should be removed sometimes a NPE occurs.

The call stack of the application looks quite like this:

1.	client application calls servlet
2.	servlet calls stateless session bean A method which is transactional
3.	stateless session bean method calls some methods on the statefull session bean
4.	stateless session bean calls @remove annotated method on statefull session bean in the same transaction



Caused by: java.lang.NullPointerException
        at org.jboss.as.ejb3.cache.TransactionAwareObjectFactory.getCurrentTransaction(TransactionAwareObjectFactory.java:79) [jboss-as-ejb3-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
        at org.jboss.as.ejb3.cache.TransactionAwareObjectFactory.destroyInstance(TransactionAwareObjectFactory.java:62) [jboss-as-ejb3-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
        at org.jboss.as.ejb3.cache.impl.backing.NonPassivatingBackingCacheImpl.remove(NonPassivatingBackingCacheImpl.java:165) [jboss-as-ejb3-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
        at org.jboss.as.ejb3.cache.impl.backing.NonPassivatingBackingCacheImpl.remove(NonPassivatingBackingCacheImpl.java:57) [jboss-as-ejb3-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
        at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.remove(AbstractCache.java:100) [jboss-as-ejb3-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
        at org.jboss.as.ejb3.cache.spi.impl.AbstractCache.remove(AbstractCache.java:39) [jboss-as-ejb3-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
        at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.removeSession(StatefulSessionComponent.java:283) [jboss-as-ejb3-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
        at org.jboss.as.ejb3.component.stateful.StatefulRemoveInterceptor.processInvocation(StatefulRemoveInterceptor.java:100) [jboss-as-ejb3-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
        at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:67) [jboss-as-ejb3-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
        at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:200) [jboss-as-ejb3-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
        ... 103 more
                
> EjbUtilities is used without regard for dependencies
> ----------------------------------------------------
>
>                 Key: AS7-6862
>                 URL: https://issues.jboss.org/browse/AS7-6862
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
>            Reporter: Stuart Douglas
>            Assignee: jaikiran pai
>             Fix For: 8.0.0.Alpha1
>
>
> org.jboss.as.ejb3.component.EJBUtilities is used to get services in the EJB subsystem, without setting up proper dependencies (e.g. in org.jboss.as.ejb3.component.EJBComponentCreateService#getEJBUtilities). Occasionally this can cause problems at startup as EJBUtilities can end up being null for some EJB's. 
> We should probably just remove this class, or at the very least make sure it is injected properly and not looked up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira