Support Article
NamingException during server startup
SA-18357
Summary
NamingException was observed in production using FS5.7.0.2.
Object to bind: com.chordiant.service.rmi.RMISmartSkeletonImpl[RemoteStub [ref: [endpoint:[localhost:39458](local),objID:[0]]]]
Exception stack trace: javax.naming.NamingException: cell/persistent/systemtaskprocessor_localhost_110820798. Root exception is org.omg.CosNaming.NamingContextPackage.CannotProceed: IDL:omg.org/CosNaming/NamingContext/CannotProceed:1.0
at com.ibm.ws.naming.distcos.PersistentNameStoreManager.getMasterRootNC(PersistentNameStoreManager.java:1572)
at com.ibm.ws.naming.distcos.PersistentXmlSlaveNC.getMasterRootNC(PersistentXmlSlaveNC.java:682)
Error Messages
Exception stack trace: javax.naming.NamingException: cell/persistent/systemtaskprocessor_localhost_110820798. Root exception is org.omg.CosNaming.NamingContextPackage.CannotProceed: IDL:omg.org/CosNaming/NamingContext/CannotProceed:1.0
at com.ibm.ws.naming.distcos.PersistentNameStoreManager.getMasterRootNC(PersistentNameStoreManager.java:1572)
at com.ibm.ws.naming.distcos.PersistentXmlSlaveNC.getMasterRootNC(PersistentXmlSlaveNC.java:682)
at com.ibm.ws.naming.distcos.PersistentXmlSlaveNC.access$000(PersistentXmlSlaveNC.java:64)
at com.ibm.ws.naming.distcos.PersistentXmlSlaveNC$1.run(PersistentXmlSlaveNC.java:713)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:2362)
Steps to Reproduce
Restart the server.
Root Cause
During server start up, the custom objects helper is trying to re-bind the SystemTaskDispatcher component and DL:omg.org/CosNaming/NamingContext/CannotProceed:1.0 exception has thrown.
This could be observed when tried to rebind a Naming Context that is already bound somewhere in the Interoperable Naming Service (INS). JNDI entries are corrupt. namestore.xml – at node scope, Provides persistent JNDI namespace binding data.
Resolution
Suggested to remove the old JNDI entries entries.
Follow the below steps to clean up the JNDI entries, :
- Take a backup of the namestore.xml file before removing the entries.
- Shutdown the application JVM's, the node agent and the deployment manager.
- Remove the JNDI entries from the following file: WebSphere/DeploymentManager/config/cells//NameStore.xml
- Restart the application server.
As a local change the namestore.xml was manually synchronized.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.