@Singleton beans using @EJB's in @PreDestroy

[jjohnson_vii]

I have an application we are moving from JBoss 4 to JBoss 7, and as such are taking advantage of many JEE6 features.  We currently have a handful of @Singleton annotated service beans.  These beans have various Stateless EJB's injected into them via @EJB setter injection.  Startup all seems to work fine in that Stateless beans are available in @PostConstruct calls.

@PreDestroy calls are a different story.  Many times the EJB I want to use is already "gone" and thus I get a stack trace about EJBTransactionRolledBackException.  The @DependsOn annotation seems to only work for @Singleton beans that depend on other @Singleton beans, not Stateless EJBs so that isn't a solution.

Has anyone else seen this?  This seems like incorrect behavior... all the EJBs for a service should be available at @PreDestroy time for a @Singleton.  At this point I'm not sure what I can do to fix this.

[jjohnson_vii]

I forgot to mention, I'm using AS 7.1.1

Also, I have looked at the EJB 3.1 spec and this seems like a violation.  Specifically table 3 lists the "Operations allowed in PreDestroy" and includes the list:

SessionContext methods: getBusinessObject, getRollbackOnly, setRollbackOnly, getTimerService, lookup, getContextData

JNDI access to java:comp/env

Resource manager access

Enterprise bean access

EntityManagerFactory access

EntityManager access

TimerService and Timer methods

So... why are my EJBs unavailable at PreDestroy time? 

[jjohnson_vii]

And 1 more piece of info.  I think my EJB is "available" but it is an EJB that uses a @Resource annotated DataSource, and when it tries to use that DataSource during shutdown is when the exception occurs.  Relevant stack:

Caused by: java.lang.NullPointerException

        at org.jboss.security.plugins.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:88)

        at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getSubject(AbstractConnectionManager.java:689)

        at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:463)

        at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:129)

[jjohnson_vii]

https://issues.jboss.org/browse/AS7-4808 is my issue I guess, thanks for reading me type to myself fellow coders!! 

[jbertram]

FYI - You can try out the fix on the latest AS7 nightly.

[jaikiran]

Sorry, I missed this thread. You are right https://issues.jboss.org/browse/AS7-4808 is what is probably causing this and as Justin says, the fix is available in the nightly builds.

[jaikiran]

jaikiran pai wrote:

Sorry, I missed this thread.

Oh, probably not! I see that this was created just a few hours ago while I was asleep!

[sfcoy]

jaikiran pai wrote:

...

Oh, probably not! I see that this was created just a few hours ago while I was asleep!

I don't believe that for a second. It's well known that jaikiran pai never sleeps!

[nickarls]

I don't believe that for a second. It's well known that jaikiran pai never sleeps!

I have a theory he's some sort of JBoss-Bot

[jaikiran]

Ha ha!

Trust me, I'm not a bot, I can pass captcha tests

[nickarls]

Trust me, I'm not a bot, I can pass captcha tests

On the contrary, it proves you must be a bot. I sometimes have to ask for 10 re-captchas before getting anything remotely readable