javax.naming.NameAlreadyBoundException: [EJB:011224]Unable to bind the interface - JNDI naming collision occurs when two separate applications, EAR and WAR, have the same exact ejb
Last updated on NOVEMBER 14, 2017
Applies to:Oracle WebLogic Server - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
After the WLS 12c upgrade from 10.3.6, we are seeing issues where a domain comes up on Admin mode. Majority of the errors on the server log points to the issue of failing to bind business Interface to the JNDI name due to the fact that another EJB had already bound an interface to that name.
In WLS 12c, JNDI naming collision occurs when two separate applications, EAR and WAR, have the same exact ejb.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms