Skip to Content
0
Former Member
Dec 24, 2007 at 05:26 AM

SLD error after upgrade to SP13

58 Views

Hi experts,

Our enterprise portal instance has a local sld running in the WAS.

Recently, we upgraded from SP09 to SP13. After this, we are not able to connect to sld from webdynpro administrator.

Given below is the log file content in SLD.

#10 12/23/2007 15:26:48.731 [SAPEngine_Application_Thread[impl:3]_20] FATAL com.sap.lcr.cimsrv.CIMOMServlet: SLD initialization failure, can not set up cluster-wide event notification. Please check your JMS provider for errors.

Thrown:

com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: Failed to initialize cluster notification. Please check your JNDI service and JMS provider for errors.

at com.sap.lcr.cimsrv.ClusterNotificationListener.<init>(ClusterNotificationListener.java:154)

at com.sap.lcr.cimsrv.ClusterNotificationListener.start(ClusterNotificationListener.java:69)

at com.sap.lcr.cimsrv.CIMOMServlet.init(CIMOMServlet.java:107)

at javax.servlet.GenericServlet.init(GenericServlet.java:258)

at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.getServlet(WebComponents.java:339)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:354)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

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:100)

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

Caused by: javax.jms.JMSSecurityException: You do not have permissions: action consumer and instance SLDClusterNotificationTopic.

at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:231)

at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2614)

at com.sap.jms.client.session.Session.createConsumer(Session.java:2173)

at com.sap.jms.client.session.TopicSession.createSubscriber(TopicSession.java:39)

at com.sap.lcr.cimsrv.ClusterNotificationListener.<init>(ClusterNotificationListener.java:142)

... 18 more

caused by:

javax.jms.JMSSecurityException: You do not have permissions: action consumer and instance SLDClusterNotificationTopic.

at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:231)

at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2614)

at com.sap.jms.client.session.Session.createConsumer(Session.java:2173)

at com.sap.jms.client.session.TopicSession.createSubscriber(TopicSession.java:39)

at com.sap.lcr.cimsrv.ClusterNotificationListener.<init>(ClusterNotificationListener.java:142)

at com.sap.lcr.cimsrv.ClusterNotificationListener.start(ClusterNotificationListener.java:69)

at com.sap.lcr.cimsrv.CIMOMServlet.init(CIMOMServlet.java:107)

at javax.servlet.GenericServlet.init(GenericServlet.java:258)

at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.getServlet(WebComponents.java:339)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:354)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

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:100)

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

Why does this happen? I tried this with administrator login itself.

Can anyone help me out please?

Thanks alot

Shobin