Troubleshooting
Problem
User not authorized to Bind a CORBA Naming context.
Symptom
SystemOut.log showing:
SessionFactor W org.hibernate.impl.SessionFactoryObjectFactory addInstance Could not bind factory to JNDI
javax.naming.NoPermissionException: NO_PERMISSION exception caught [Root exception is org.omg.CORBA.NO_PERMISSION: Not authorized to perform bind_new_corba_context operation. vmcid: 0x0 minor code: 0 completed: No]
at com.ibm.ws.naming.jndicos.CNContextImpl.doCreateSubcontext(CNContextImpl.java:2363)
at com.ibm.ws.naming.jndicos.CNContextImpl.createSubcontext(CNContextImpl.java:892)
at com.ibm.ws.naming.util.WsnInitCtx.createSubcontext(WsnInitCtx.java:371)
at com.ibm.ws.naming.util.WsnInitCtx.createSubcontext(WsnInitCtx.java:385)
at
javax.naming.InitialContext.createSubcontext(InitialContext.java:504)
at org.hibernate.util.NamingHelper.bind(NamingHelper.java:69)
...
at xyz.framework.persistence.hibernate.HibernateSessionFactory.getHibernateSession(HibernateSessionFactory.java:68)
...
Caused by: org.omg.CORBA.NO_PERMISSION: Not authorized to perform bind_new_corba_context operation. vmcid: 0x0 minor code: 0 completed: No
Cause
User executing the Bind operation does not have the naming role CosNamingWrite.
Please see topic "Naming roles" in the product documentation for more information on this.
Resolving The Problem
Add CosNamingWrite and CosNamingCreate roles to the user. Restart the entire deployment manager cell (Deployment Manager, Node Agent, and the application server)
Please see topic "Administrative user roles settings and CORBA naming service user settings" on Information Center for more information on this.
Historical Number
69584;7TD;000
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21675560