由于NameAlreadyBoundException导致的Weblogic部署问题-将weblogic从10.3.6升级到Weblogic 12cR2之后

Question

我的应用程序当前在Weblogic 10.3下使用Java 1.6。现在，我们正在尝试将相同的应用程序部署到weblogic 12cR2和Java 1.8，这是我们面临的错误。

Unable to bind Business Interface to the JNDI name: Gen4CServlet_warcontact_Home, throw exception javax.naming.NameAlreadyBoundException: [EJB:011224]Unable to bind the interface com.hh.cc.ce.RemoteContactSession to RemoteContactession. Another EJB has already bound an interface to that name.; remaining name 'ejb/Contact#com/ce'. NestedException Message is :[EJB:011224]Unable to bind the interface com.hh.cc.ce.RemoteContactSession to RemoteContactSession. Another EJB has already bound an interface to that name."
weblogic.application.ModuleException: Unable to bind Business Interface to the JNDI name: iLinqGen4CGEServlet_warcontactge_Home, throw exception javax.naming.NameAlreadyBoundException: [EJB:011224]Unable to bind the interface com.hh.cc.ce.RemoteContactGESession to RemoteContactGESession. Another EJB has already bound an interface to that name.; remaining name 'ejb/Contact#com/hh/cc/ce'. NestedException Message is :[EJB:011224]Unable to bind the interface com.hh.cc.ce.RemoteContactSession to RemoteContactSession. Another EJB has already bound an interface to that name.
        at weblogic.application.internal.ExtensibleModuleWrapper.activate(ExtensibleModuleWrapper.java:123)
        at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:114)
        at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:212)
        at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:207)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
        Truncated. see log file for complete stacktrace

Answer 1

根据Oracle KM 无法将业务接口绑定到JNDI名称javax.naming.NameAlreadyBoundException：[EJB：011224]无法绑定（Doc ID 2254400.1），这可能是由于MANIFESF中的类路径条目所致.MF文件。尝试删除相同的重新部署应用程序。