Iterative Publishing of a WLP Application through OEPE results in Null Pointer Exception Followed by javax.naming.NameAlreadyBoundException
(Doc ID 1538384.1)
Last updated on JANUARY 15, 2025
Applies to:
Oracle WebLogic Portal - Version 10.3.4 to 10.3.7 [Release AS10gR3]Oracle WebLogic Server - Version 10.3.4.0.1 to 10.3.6
Information in this document applies to any platform.
Symptoms
Iterative publishing of a WebLogic Portal Application through OEPE (WLP 10.3.5) for the 3rd time to the WebLogic Server fails with the following exception:
####<Sep 28, 2012 9:58:52 AM MDT> <Warning> <HTTP> <MACHINE> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1348847932029> <BEA-101162> <User defined listener weblogic.wsee.deploy.ServletDeployListener failed: java.lang.NullPointerException.
java.lang.NullPointerException
at weblogic.wsee.monitoring.WseeBaseRuntimeMBeanImpl.unregisterPorts(WseeBaseRuntimeMBeanImpl.java:285)
at weblogic.wsee.monitoring.WseeBaseRuntimeMBeanImpl.unregister(WseeBaseRuntimeMBeanImpl.java:255)
at weblogic.wsee.monitoring.WseeV2RuntimeMBeanImpl.unregister(WseeV2RuntimeMBeanImpl.java:58)
at weblogic.management.runtime.RuntimeMBeanDelegate.unregisterChildren(RuntimeMBeanDelegate.java:350)
at weblogic.management.runtime.RuntimeMBeanDelegate.unregister(RuntimeMBeanDelegate.java:274)
at weblogic.wsee.ws.WsRegistry$1.run(WsRegistry.java:325)
..
at weblogic.wsee.ws.WsRegistry.unregisterMBean(WsRegistry.java:321)
at weblogic.wsee.ws.WsRegistry.unregister(WsRegistry.java:272)
at weblogic.wsee.deploy.DeployInfo.clean(DeployInfo.java:462)
at weblogic.wsee.deploy.WSEEModule.destroy(WSEEModule.java:448)
at weblogic.wsee.deploy.WSEEWebModule.destroy(WSEEWebModule.java:380)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.deactivate_and_unprepare(AppDeploymentExtensionFactory.java:145)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.removeModule(AppDeploymentExtensionFactory.java:61)
at weblogic.wsee.deploy.ServletDeployListener.contextDestroyed(ServletDeployListener.java:37)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
.....
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 28, 2012 9:58:55 AM MDT> <Warning> <HTTP> <MACHINE> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1348847935944> <BEA-101162> <User defined listener weblogic.wsee.deploy.ServletDeployListener failed: java.lang.RuntimeException: weblogic.management.DeploymentException: Error encountered during prepare phase of deploying WebService module '<WAR FILE>.war'. While deploying WebService module '<WAR FILE>.war'. Failed to bind wsdl port to internal name wsee/<WAR FILE>#wsrp-1.0-ServiceDescriptionPortComponent javax.naming.NameAlreadyBoundException: TestWeb#wsrp-1.0-ServiceDescriptionPortComponent is already bound; remaining name 'app/wsee'.
java.lang.RuntimeException: weblogic.management.DeploymentException: Error encountered during prepare phase of deploying WebService module '<WAR FILE>.war'. While deploying WebService module '<WAR FILE>.war'. Failed to bind wsdl port to internal name wsee/<WAR FILE>#wsrp-1.0-ServiceDescriptionPortComponent javax.naming.NameAlreadyBoundException: <WAR FILE>#wsrp-1.0-ServiceDescriptionPortComponent is already bound; remaining name 'app/wsee'
at weblogic.wsee.deploy.ServletDeployListener.contextPrepared(ServletDeployListener.java:25)
at weblogic.servlet.internal.EventsManager$FireContextPreparedAction.run(EventsManager.java:503)
....
at weblogic.application.internal.DeploymentStateChecker.start(DeploymentStateChecker.java:281)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.start(AppContainerInvoker.java:265)
at weblogic.deploy.internal.targetserver.operations.ModuleRedeployOperation.moduleLevelRedeploy(ModuleRedeployOperation.java:141)
at weblogic.deploy.internal.targetserver.operations.ModuleRedeployOperation.doPrepare(ModuleRedeployOperation.java:81)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
...
Caused By: weblogic.management.DeploymentException: Error encountered during prepare phase of deploying WebService module '<WAR FILE>.war'. While deploying WebService module '<WAR FILE>.war'. Failed to bind wsdl port to internal name wsee/<WAR FILE>#wsrp-1.0-ServiceDescriptionPortComponent javax.naming.NameAlreadyBoundException:<WAR FILE>#wsrp-1.0-ServiceDescriptionPortComponent is already bound; remaining name 'app/wsee'
at weblogic.wsee.deploy.WSEEModule.prepare(WSEEModule.java:149)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.prepare_and_activate(AppDeploymentExtensionFactory.java:95)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.addModule(AppDeploymentExtensionFactory.java:45)
at weblogic.wsee.deploy.ServletDeployListener.contextPrepared(ServletDeployListener.java:22)
at weblogic.servlet.internal.EventsManager$FireContextPreparedAction.run(EventsManager.java:503)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
....
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameAlreadyBoundException: <WAR FILE>#wsrp-1.0-ServiceDescriptionPortComponent is already bound; remaining name 'app/wsee'
at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:324)
at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:277)
at weblogic.wsee.deploy.WSEEWebModule.bindInternalPort(WSEEWebModule.java:279)
at weblogic.wsee.deploy.WSEEWebModule.updateAddress(WSEEWebModule.java:333)
at weblogic.wsee.deploy.WSEEWebModule.registerEndpoint(WSEEWebModule.java:246)
at weblogic.wsee.deploy.WSEEModule.prepare(WSEEModule.java:137)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.prepare_and_activate(AppDeploymentExtensionFactory.java:95)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.addModule(AppDeploymentExtensionFactory.java:45)
at weblogic.wsee.deploy.ServletDeployListener.contextPrepared(ServletDeployListener.java:22)
....
at weblogic.deploy.internal.targetserver.AppContainerInvoker.start(AppContainerInvoker.java:265)
at weblogic.deploy.internal.targetserver.operations.ModuleRedeployOperation.moduleLevelRedeploy(ModuleRedeployOperation.java:141)
at weblogic.deploy.internal.targetserver.operations.ModuleRedeployOperation.doPrepare(ModuleRedeployOperation.java:81)
...
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
java.lang.NullPointerException
at weblogic.wsee.monitoring.WseeBaseRuntimeMBeanImpl.unregisterPorts(WseeBaseRuntimeMBeanImpl.java:285)
at weblogic.wsee.monitoring.WseeBaseRuntimeMBeanImpl.unregister(WseeBaseRuntimeMBeanImpl.java:255)
at weblogic.wsee.monitoring.WseeV2RuntimeMBeanImpl.unregister(WseeV2RuntimeMBeanImpl.java:58)
at weblogic.management.runtime.RuntimeMBeanDelegate.unregisterChildren(RuntimeMBeanDelegate.java:350)
at weblogic.management.runtime.RuntimeMBeanDelegate.unregister(RuntimeMBeanDelegate.java:274)
at weblogic.wsee.ws.WsRegistry$1.run(WsRegistry.java:325)
..
at weblogic.wsee.ws.WsRegistry.unregisterMBean(WsRegistry.java:321)
at weblogic.wsee.ws.WsRegistry.unregister(WsRegistry.java:272)
at weblogic.wsee.deploy.DeployInfo.clean(DeployInfo.java:462)
at weblogic.wsee.deploy.WSEEModule.destroy(WSEEModule.java:448)
at weblogic.wsee.deploy.WSEEWebModule.destroy(WSEEWebModule.java:380)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.deactivate_and_unprepare(AppDeploymentExtensionFactory.java:145)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.removeModule(AppDeploymentExtensionFactory.java:61)
at weblogic.wsee.deploy.ServletDeployListener.contextDestroyed(ServletDeployListener.java:37)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
.....
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 28, 2012 9:58:55 AM MDT> <Warning> <HTTP> <MACHINE> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <
java.lang.RuntimeException: weblogic.management.DeploymentException: Error encountered during prepare phase of deploying WebService module '<WAR FILE>.war'. While deploying WebService module '<WAR FILE>.war'. Failed to bind wsdl port to internal name wsee/<WAR FILE>#wsrp-1.0-ServiceDescriptionPortComponent javax.naming.NameAlreadyBoundException: <WAR FILE>#wsrp-1.0-ServiceDescriptionPortComponent is already bound; remaining name 'app/wsee'
at weblogic.wsee.deploy.ServletDeployListener.contextPrepared(ServletDeployListener.java:25)
at weblogic.servlet.internal.EventsManager$FireContextPreparedAction.run(EventsManager.java:503)
....
at weblogic.application.internal.DeploymentStateChecker.start(DeploymentStateChecker.java:281)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.start(AppContainerInvoker.java:265)
at weblogic.deploy.internal.targetserver.operations.ModuleRedeployOperation.moduleLevelRedeploy(ModuleRedeployOperation.java:141)
at weblogic.deploy.internal.targetserver.operations.ModuleRedeployOperation.doPrepare(ModuleRedeployOperation.java:81)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
...
Caused By: weblogic.management.DeploymentException: Error encountered during prepare phase of deploying WebService module '<WAR FILE>.war'. While deploying WebService module '<WAR FILE>.war'. Failed to bind wsdl port to internal name wsee/<WAR FILE>#wsrp-1.0-ServiceDescriptionPortComponent javax.naming.NameAlreadyBoundException:<WAR FILE>#wsrp-1.0-ServiceDescriptionPortComponent is already bound; remaining name 'app/wsee'
at weblogic.wsee.deploy.WSEEModule.prepare(WSEEModule.java:149)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.prepare_and_activate(AppDeploymentExtensionFactory.java:95)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.addModule(AppDeploymentExtensionFactory.java:45)
at weblogic.wsee.deploy.ServletDeployListener.contextPrepared(ServletDeployListener.java:22)
at weblogic.servlet.internal.EventsManager$FireContextPreparedAction.run(EventsManager.java:503)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
....
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameAlreadyBoundException: <WAR FILE>#wsrp-1.0-ServiceDescriptionPortComponent is already bound; remaining name 'app/wsee'
at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:324)
at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:277)
at weblogic.wsee.deploy.WSEEWebModule.bindInternalPort(WSEEWebModule.java:279)
at weblogic.wsee.deploy.WSEEWebModule.updateAddress(WSEEWebModule.java:333)
at weblogic.wsee.deploy.WSEEWebModule.registerEndpoint(WSEEWebModule.java:246)
at weblogic.wsee.deploy.WSEEModule.prepare(WSEEModule.java:137)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.prepare_and_activate(AppDeploymentExtensionFactory.java:95)
at weblogic.wsee.deploy.AppDeploymentExtensionFactory.addModule(AppDeploymentExtensionFactory.java:45)
at weblogic.wsee.deploy.ServletDeployListener.contextPrepared(ServletDeployListener.java:22)
....
at weblogic.deploy.internal.targetserver.AppContainerInvoker.start(AppContainerInvoker.java:265)
at weblogic.deploy.internal.targetserver.operations.ModuleRedeployOperation.moduleLevelRedeploy(ModuleRedeployOperation.java:141)
at weblogic.deploy.internal.targetserver.operations.ModuleRedeployOperation.doPrepare(ModuleRedeployOperation.java:81)
...
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
This exception occurs when the java class is modified in WebLogic Portal application and you try to publish it, the publishing will go through successfully for the first two times. However, on modifying the class for the third time and trying to publish it, the server will try to undeploy the app subsequently resulting in the above exception. In order to recover from this error, you have to restart your servers.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |