Application runs fine in standalone mode, but throws an EJBAccessException in domain mode

[dragginlord1]

I'm migrating an application from WebSphere Application Server 6.1 to JBoss EAP 6. I have the application running perfectly in my development environment on JBoss EAP 6 in standalone mode (running it from JDev). However, when I migrate the code to a test server running in default domain mode I get a EJBAccessException: Not Allowed as soon as I run anything that uses an EJB.  The general error message is a "JBAS014134: EJB Invocation failed on component X  javax.ejb.EJBAccessException:JBAS014502: Invocation on method: X is not allowed"

I've been reading through the manuals and doing searches, but so far no clues as to why this is occuring. I'm assuming that domain mode has additional EJB security that is causing the issue. Any ideas as to what might be causing this?

Thanks!

[wdfink]

That looks like that you have a different security configuration in standalone and domain mode.

Or you did not have the correct user settings in domain mode

[dragginlord1]

Thanks   I'll run this by the Admin for the domain mode server and see if it shakes anything loose.

[wdfink]

Let me know your findings

[dragginlord1]

New information. The issue is not tied to Standalone vs Domain mode. The problem is occuring between EAP versions. The application runs fine on version 6.0.1, but breaks on version 6.1.1 and 6.2.0 .  It appears to be tied to the ejb-security-interceptor feature that was added in 6.1.0 .  The application is a legacy that was migrated from WebSphere 6.1 and uses EJB 2.1 .

At this point we're looking at what changed between versions 6.0.1 and 6.1.1 to see what has caused the application to stop working.

[wdfink]

Ah, ok.

In that case I suppose the issue is the changed default behaviour.

Unsecured method inside a secured app are denied by default since EAP6.1.

You might add this to the ejb3 subsystem (example applies to domain mode):

   /profile=default/subsystem=ejb3:write-attribute(name=default-missing-method-permissions-deny-access, value=false)