cancel
Showing results for 
Search instead for 
Did you mean: 

SLD error after upgrade to SP13

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

hi,

check this note1018839 will help u.

regards

ajai

Former Member
0 Kudos

Hi ajai,

thanks alot for your quick reply.

Here, we did the upgrade in 2 instances. In one of them, SLD was not configured at all. Even the initial data import was not performed. The other instance SLD was configured and few ABAP systems were registered in the SLD.

Both the instances, after upgrade shows the same error.

I hope you are clear about the scenario.

And, the most important thing : I am not a basis guy. So please bear with me.

Waiting for your inputs.

Shobin

Former Member
0 Kudos

Hi,

Does it have anything to do with the authorization?

I am logging in with the administrator id which is having LcrAdministrator role.

Can anyone help me out?

Thanks alot

Shobin

Former Member
0 Kudos

Hi ,

I could solve the issue myself.

There was a problem with the authorization with JMS security roles.

Shobin

Former Member
0 Kudos

hi shobin,

i have the same problem, can you explain your solution please. what do you do in visual administrator.

many thanks,

christoph

I'am back to cim modell: 1.5.24 and SAP_CR 2.0 (produced 03/17/2005) from N4S local Installation. It works fine.

Edited by: Christoph Kautz on Jan 30, 2008 10:36 AM

Former Member
0 Kudos

Request you to please give the logical steps perfomed in Visual Admin - > JMS Security Roles.

Former Member
0 Kudos

hi,

i have reinstalled my environment and use the local CIM with version 1.5.24. the problem came after i tried a new model version with import in http://<host>:<port>/sld.

the settings in visual administrator cluster> Security Provider > Runtime(tab) > service.jms.default.authorization>security roles (view, tab) are administrators and clients. adminstrators have security roles administrators and clients have guests. group is SAP_J2EE_ADMIN . they are all Role Reference, is marked. I go to edit mode and when i change the role type to security role comes a popup with message the selected role reference will be replaced by a new role in order to perform the mapping.

After Reinstall my environment, i dont touch this area in visual administrator.

Note: with jspm variant "single support packages" not sp-stack! i'am on sp level 14 with almost all of deployed components. No problems to CAF SP 14, thtas composite application framework, i became an error.

regards,

christoph

Edited by: Christoph Kautz on Jan 31, 2008 11:19 AM