EJBAccessException when destroying SLSB

[daniell]

I have a stateless session bean, which is annotated with @RolesAllowed(...). A security-domain is specified in the file jboss.xml. Everything works fine in operation, but when I shut down the JBossAS, I get the following Exception:

java.lang.RuntimeException: javax.ejb.EJBAccessException: Authentication failure
        at org.jboss.ejb3.interceptor.LifecycleInterceptorHandler.preDestroy(LifecycleInterceptorHandler.java:135)
        at org.jboss.ejb3.EJBContainer.invokePreDestroy(EJBContainer.java:624)
        at org.jboss.ejb3.AbstractPool.remove(AbstractPool.java:207)
        at org.jboss.ejb3.InfinitePool.destroy(InfinitePool.java:42)
....

Is there a possibility to get rid of this exception? I'm wondering if noone faces this problem except me.

[jaikiran]

If you have a simple application which can reproduce this issue, please create a JIRA here https://jira.jboss.org/browse/EJBTHREE and attach the app. I'll see if it's some bug or something else.

[jaikiran]

Wait! Which version of JBoss AS do you use? The "tag" you have for your post, seems to suggest 4.2.2. Is that right?

If yes, then I would recommend that you use the latest AS 5.1.0 with our EJB3 plugin http://www.jboss.org/ejb3/ejb3plugin.html. There have been numerous changes in EJB3 since 4.2.2. Infact the code for EJB3 in 4.2.2 community branch is no longer being maintained.

[daniell]

Thanks for your answer!

Yes, We're using 4.2.2. So this should be fixed in version 5.1?

[jaikiran]

Daniel Lechner wrote:

Yes, We're using 4.2.2. So this should be fixed in version 5.1?

I haven't seen anyone reporting that bug against AS-5.1. So I believe it doesn't show up in that version. And if it does, then fixing it in latest EJB3 trunk won't be a big deal, because EJB3 trunk is in active development.

[daniell]

Ok, thanks. I'll try to update as soon as possible and be back when I have any news

[daniell]

In the meantime, I found a solution for JBossAS 4.2.2: see comments of https://jira.jboss.org/browse/EJBTHREE-847

So I've changed my LoginModule to support an "unauthenticatedIdentity" and added @PermitAll to the @Remove methods.

Thanks