on 03-19-2009 6:44 AM
Hi All,
We have upgraded to SP17 - EP7. We are using customized Masthead. The problem we are facing with SP17 is when we click on Log Off link, we are getting Javascript error. In code we are calling function openLogoffMsg() function. which has a code as
releaseProducerSessions();
When we comment that line, the Pop Up window is coming up for 'Yes' and 'No' options and no Javascript error is coming. But when we select 'Yes' it is giving Portal runtime error with default trace as:
EXCEPTION]
java.lang.NoClassDefFoundError: com.sap.portal.iviewserver.wsrpservice.consumer.wsrpconsuming.sessionmanagement.IWSRPSessionReleaseService
at com.sapportals.portal.navigation.LogOutComponent.doOnNodeReady(LogOutComponent.java:18)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
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(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.ClassNotFoundException: com.sap.portal.iviewserver.wsrpservice.consumer.wsrpconsuming.sessionmanagement.IWSRPSessionReleaseService
-
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@5a005a0]
Parent loader name: [sap.com/com.<company name>.portal.navigation.mastheadSUPO]
References:
not registered!
Resources:
/usr/sap/RPB/JC00/j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.<company name>.portal.navigation.mastheadSUPO/private/classes
/usr/sap/RPB/JC00/j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/com.<company name>.portal.navigation.mastheadSUPO/private/lib/com.sap.portal.navigation.masthead_core.jar
Any Idea why it is happening??
Thanks in Advance!!!
Hi,
This exception shows missing jar files. Check if required jars are present in the lib folder of the customized masthead par file. You can check the jars from standard masthead par.
Regards,
Harini S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Add the jar to Java build path also like this
Right click project -> Properties -> Java Build Path -> Libraries tab -> Add JARs -> Choose all the jars from lib folder and select Ok.
Actually NoClassDefFound is pointing to this class.
com.sap.portal.iviewserver.wsrpservice.consumer.wsrpconsuming.sessionmanagement.IWSRPSessionReleaseService
Use class locator and find which jar contains this class.
Regards,
Harini S
Hi,
If you have added the required jar to lib folder and java build path, the error should go because when u add to build path, it is used when project is building and when it is in lib folder, it is used during runtime. There is no way error remains. If it remains, it could mean the jar required may be different (u r not adding the correct jar). Check the error log again from defaultTrace or error from the code. Check which class is throwing error. Accordingly add the jars.
Regards,
Harini S
Hi Daniel,
The problem should be resolved just by commenting the code "releaseProducerSessions()".
Portal runtime error is coming because you may be adding the JAR that is of different SP Level. Please make sure that the JAR you are adding is of same SP level as your customized component.
Also you just need to add "com.sap.portal.navigation.masthead_core" jar in the LIB folder.
Regards,
Gurmat Bhatia
I just went through this same process to update our masthead to be 'compliant' with SP17, and the releaseProducerSession() code has been removed from the JSP. I would suggest that you look at the new par file deployed with SP17 to learn what has changed before you re-implement functionality that is no longer required.
This just goes to show that altering a base portal component object, while in some cases required, may prove to be more trouble than it's worth.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.