com.sap.engine.services.jndi.persistent.exceptions...

former_member482483 · ‎09-01-2010

Hi,

We have just finish apply/update our SAP Netweaver WebAS 6.40 (Java) with the support package (SP25). When we test our application, we encountered the following exception

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.

This exception seems to be intermittent. After some time, when we try again, we did not encountered this exception. But after we restart, the error appear again.

Please help.

former_member482483 · ‎09-02-2010

Hi,

On checking the trace log file, I noticed some security exception 'com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.'.

before the 'com.sap.engine.services.jndi.persistent.exceptions.NamingException : Error getting the server-side naming service functionality during getInitialContext operation. '

What could be the cause for 'BaseSecurityException: Caller not authorized' exception?

-

#

#1.5 #0003BA7B25C0002B000000000000394600048F300D41A62A#1283336450450#System.err#sap.com/CRRSRatingEAR#System.err#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Plain###log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.DailyRollingFileAppender.#

#1.5 #0003BA7B25C0002B000000010000394600048F300D437AAE#1283336450570#System.err#sap.com/CRRSRatingEAR#System.err#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Plain###log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.DailyRollingFileAppender.#

#1.5 #0003BA7B25C0002B000000030000394600048F300D47CA6E#1283336450850#com.sap.engine.services.security.authentication.logincontext#sap.com/CRRSRatingEAR#com.sap.engine.services.security.authentication.logincontext#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Java###Caller not authorized.

[EXCEPTION]

#1#com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.

at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)

at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)

at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)

at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:119)

at com.sap.engine.services.security.server.AuthenticationContextImpl.getSessionPool(AuthenticationContextImpl.java:395)

at com.sap.engine.services.security.server.AuthenticationContextImpl.getLoginContextFactory(AuthenticationContextImpl.java:740)

at com.sap.engine.services.security.server.AuthenticationContextImpl.getLoginContext(AuthenticationContextImpl.java:254)

at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:59)

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:135)

at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)

at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)

at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)

at javax.naming.InitialContext.init(InitialContext.java:219)

at javax.naming.InitialContext.<init>(InitialContext.java:195)

at com.mbb.crrs.business.common.InitialContextFactory$SapWasContext.getInitialContext(InitialContextFactory.java:139)

at com.mbb.crrs.business.common.InitialContextFactory.getInitalContext(InitialContextFactory.java:81)

at com.mbb.crrs.business.common.ServiceLocator.<init>(ServiceLocator.java:286)

at com.mbb.crrs.business.common.ServiceLocator.getInstance(ServiceLocator.java:308)

at com.mbb.crrs.web.common.dao.ParamCacheDAO.<init>(ParamCacheDAO.java:56)

at com.mbb.crrs.web.common.ParamCache.loadData(ParamCache.java:182)

at com.mbb.crrs.web.common.ParamCache.loadData(ParamCache.java:166)

at com.mbb.crrs.common.CRRSInitServlet.init(CRRSInitServlet.java:33)

at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)

at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)

at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

#

#1.5 #0003BA7B25C0002B000000040000394600048F300D499B25#1283336450972#com.sap.engine.services.servlets_jsp.Deploy#sap.com/CRRSRatingEAR#com.sap.engine.services.servlets_jsp.Deploy#Guest#0##n/a##9811a6e3b5b211df85fa0003ba7b25c0#SAPEngine_Application_Thread[impl:3]_18##0#0#Warning##Plain###application [CRRSWeb] Initialization of servlet <CRRSInitServlet> failed! The error is: com.mbb.crrs.common.exceptions.ApplicationConfigurationException: Unable to connect to WAS at 172.31.40.10:52004: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.

at com.mbb.crrs.business.common.InitialContextFactory$SapWasContext.getInitialContext(InitialContextFactory.java:143)