Portal URL iview runtime error

Dear Experts,
i'm trying to create URL iview based on document this "http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0235c19-9493-2b10-64a5-8487b23a7a41?QuickLink=index&overridelayout=true" but when i'm trying to preview there's runtime error.
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 02:16_02/06/10_0003_19556350
Refer to the log file for details about this exception.
i have tried to search the exception id but i found nothing. can you help me..please.
Regards,
dinie.

Hi Mikhail.
Thanks for reply. i have search for the log. but i only got application.log which has the same word and the latest time.
this is some of the logs.
#1.5 #00215EDB08B0006E0000004D00001EAC00048804113F2567#1275450957859#/Applications/WebApplications#sap.com/irj#com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#ZULHIA#14671##prodbwbo_PBJ_19556350#ZULHIA#b611ddc06dfa11df8c8200215edb08b0#SAPEngine_Application_Thread[impl:3]_3##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#Plain###application [irj] prt: init#
#1.5 #00215EDB08B000650000009700001EAC00048804114FF746#1275450958968#/Applications/KMC/RF#sap.com/irj#com.sapportals.wcm.service.applog.OpenSQLAppLog.logToDatabase(Connection,JDBCAppLogEntry)#ZULHIA#14671##prodbwbo_PBJ_19556350#ZULHIA#b611ddc06dfa11df8c8200215edb08b0#SAPEngine_Application_Thread[impl:3]_38##0#0#Info#1#com.sapportals.wcm.service.applog.OpenSQLAppLog#Java###Level: , AppId: , LogTextId: , PrincipalName: , PrincipalType: , ConstId: , Rid: , Param1: , Param2: , Param3: , Param4: #11#2#IndexmanagementService#Index rooms_10c829ad-2850-2d10-3382-cb598d44ca1b created.#null#0#null#null#null#null#null#null#
This is default Trace
#00215EDB08B000650000009800001EAC000488041151865E#1275450959062#com.sapportals.trex.tns.TNSClient#sap.com/irj#com.sapportals.trex.tns.TNSClient#ZULHIA#14671##prodbwbo_PBJ_19556350#ZULHIA#b611ddc06dfa11df8c8200215edb08b0#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###verifyNameServerAddress: NameServer = tcpip://<nameserverhost>:<nameserverport> caught exception: java.net.MalformedURLException: For input string: "<nameserverport>"#
#1.5 #00215EDB08B000650000009900001EAC0004880411518838#1275450959062#com.sapportals.trex.tns.TNSClient#sap.com/irj#com.sapportals.trex.tns.TNSClient#ZULHIA#14671##prodbwbo_PBJ_19556350#ZULHIA#b611ddc06dfa11df8c8200215edb08b0#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Invalid Entry for nameserver: tcpip://<nameserverhost>:<nameserverport> caught Exception: com.sapportals.trex.TrexException: TREX Name Server (including back-up servers) is down or not accessable. (Errorcode 7217)#
#1.5 #00215EDB08B000650000009A00001EAC0004880411519615#1275450959078#com.sapportals.wcm.WcmException#sap.com/irj#com.sapportals.wcm.WcmException.WcmException(90)#ZULHIA#14671##prodbwbo_PBJ
#00215EDB08B000650000009B00001EAC0004880411519BE5#1275450959078#com.sap.ip.collaboration.room.impl.RoomProps#sap.com/irj#com.sap.ip.collaboration.room.impl.RoomProps.RoomProps(240)#ZULHIA#14671##prodbwbo_PBJ_19556350#ZULHIA#b611ddc06dfa11df8c8200215edb08b0#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while trying to create rooms index: creating index failed: Invalid entry in configuration: section nameserver, key address, value tcpip://<nameserverhost>:<nameserverport> is invalid (Errorcode 7213)com.sapportals.wcm.WcmException: creating index failed: Invalid entry in configuration: section nameserver, key address, value tcpip://<nameserverhost>:<nameserverport> is invalid (Errorcode 7213)com.sapportals.wcm.WcmException: creating index failed: Invalid entry in configuration: section nameserver, key address, value tcpip://<nameserverhost>:<nameserverport> is invalid (Errorcode 7213)
#00215EDB08B0005F0000004400001EAC00048804CACA8FB0#1275454070734#System.err#sap.com/irj#System.err#ZULHIA#14957##prodbwbo_PBJ_19556350#ZULHIA#350532c06e0111df934000215edb08b0#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Plain###
>>>>>urlId=readUrl.grid.txtURL.input_component#
#1.5 #00215EDB08B0005F0000004500001EAC00048804CACA901B#1275454070734#System.err#sap.com/irj#System.err#ZULHIA#14957##prodbwbo_PBJ_19556350#ZULHIA#350532c06e0111df934000215edb08b0#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Plain###
>>>>>hiddenXmlParamsId=readUrl.hiddenXmlParams.input_component#
#1.5 #00215EDB08B000660001235000001EAC00048804CAF4EF03#1275454073500#com.sap.jms#sap.com/irj#com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0##n/a##630c16106cae11df9e3b00215edb08b0#Thread[Thread-52,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerSecurityException: You do not have permissions: action create_queue and instance ALL.
Regards,
dinie

Similar Messages

Problem in logging onto portal "Java iView Runtime " error

Hi,
We are getting the following message when trying to logon to the portal.
"Java iView Runtime
Version : 5.0.200212121529
(c) 2001 SAP Portals
The following exception occured while processing your request:
com.sapportals.portal.prt.runtime.PortalRuntimeException: delegatedplugin
Exceptions details :
com.sapportals.portal.prt.runtime.PortalRuntimeException: delegatedplugin
     at com.sapportals.portal.prt.portalconnection.sapnative.DelegatedPlugIn.handleRequest(DelegatedPlugIn.java:1044)
     at com.sapportals.portal.prt.portalconnection.sapnative.PortalPlugIn.handleRequest(PortalPlugIn.java:132)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:635)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
     at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
     at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
     at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
     at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
     at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
     at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
     at com.inqmy.core.cluster.impl3.ParserRunner.run(ParserRunner.java:30)
     at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
Caused by: javax.naming.NameNotFoundException: PortalLicense not found
     at com.sapportals.portal.prt.service.jndi.PortalServiceProviderContext.lookup(PortalServiceProviderContext.java:58)
     at com.sapportals.portal.prt.service.jndi.PortalServiceProviderContext.lookup(PortalServiceProviderContext.java:65)
     at javax.naming.InitialContext.lookup(InitialContext.java:345)
     at com.sapportals.portal.prt.portalconnection.sapnative.DelegatedPlugIn.handleRequest(DelegatedPlugIn.java:240)
     at com.sapportals.portal.prt.portalconnection.sapnative.PortalPlugIn.handleRequest(PortalPlugIn.java:132)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:635)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
     at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
     at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
     at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
     at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
     at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
     at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
     at com.inqmy.core.cluster.impl3.ParserRunner.run(ParserRunner.java:30)
     at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
If this situation persists, please contact your system administrator"
Tried restarting the portal servers but the problem still persists.
Request you to please suggest the solution for the same.

Hi Sireesha,
When it is working last time.
Are any changes made to portal recently
may be it is a permission issue in security zones.
Below links may help you.
http://help.sap.com/saphelp_nw04s/helpdata/en/25/85de55a94c4b5fa7a2d74e8ed201b0/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/ee/acd8403e37762ae10000000a155106/content.htm
Raghu

Java iview Runtime error in Portal Logon

hi
I login portal with
http://<ipaddress>:50000/irj/portal
Java iView Runtime
An exception occured while processing your request.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
If this situation persists, please contact your system administrator.
Can any one help me,,,how to sort this error.
Regards
sushma

Hi Sushma,
It seems that there are problems with permissions in Security Zones.
Check this links below to know more:
http://help.sap.com/saphelp_nw04/helpdata/en/25/85de55a94c4b5fa7a2d74e8ed201b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ee/acd8403e37762ae10000000a155106/content.htm
Thanks
Mihir

Java Iview Runtime error after logon

Hello,
we are facing some problem regarding our EP 7.0 SP13. We have an anonymous page as our home page, with some anonymous ivews, like "help", "news", etc and one iview with authentication set to default where users log into the portal and access to the private section of the portal.
That ivew does a redirection to /irj/portal and since the user is athenticated it will led him to the private home. The problem is that after logon, a Java iview runtime error appears, and users must refresh the browser to access the private section. (user is logged before the error appears).
We have checked this is not happening with users with "super admin" o "content admin" role. They are able to log into the portal, and redirection is working fine. So we think there can be some problem with security zones or authentication somewhere in the portal, but since this is the standard logon component i don´t know why is this not working.
We have checked that the redirection is working, and we have made some tests with different kind of iviews like KM iviews, URL iviews, pictures, etc. Only admin users are able to log in correctly, the others get the java iview runtime error, so we think the problem is with to standard logon...
Here goes a trace of our problem (defaultrace.trc):
#1.5 #000802B3F434005C00000434000024680004646E64997E00#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection#
#1.5 #000802B3F434005C00000435000024680004646E64998C55#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)#
#1.5 #000802B3F434005C00000436000024680004646E64998E05#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)#
#1.5 #000802B3F434005C00000437000024680004646E6499900A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #000802B3F434005C00000438000024680004646E64999183#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)#
#1.5 #000802B3F434005C00000439000024680004646E649992D1#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5 #000802B3F434005C0000043A000024680004646E6499941A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#
#1.5 #000802B3F434005C0000043B000024680004646E6499955B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5 #000802B3F434005C0000043C000024680004646E64999690#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)#
#1.5 #000802B3F434005C0000043D000024680004646E6499984F#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)#
#1.5 #000802B3F434005C0000043E000024680004646E6499999C#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)#
#1.5 #000802B3F434005C0000043F000024680004646E64999AEB#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)#
#1.5 #000802B3F434005C00000440000024680004646E64999C2F#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)#
#1.5 #000802B3F434005C00000441000024680004646E64999D76#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)#
#1.5 #000802B3F434005C00000442000024680004646E64999EDA#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)#
#1.5 #000802B3F434005C00000443000024680004646E6499A01D#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)#
#1.5 #000802B3F434005C00000444000024680004646E6499A15E#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
#1.5 #000802B3F434005C00000445000024680004646E6499A30A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
#1.5 #000802B3F434005C00000446000024680004646E6499A479#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #000802B3F434005C00000447000024680004646E6499A5B7#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #000802B3F434005C00000448000024680004646E6499A718#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
#1.5 #000802B3F434005C00000449000024680004646E6499A855#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
#1.5 #000802B3F434005C0000044A000024680004646E6499B6CC#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException#
#1.5 #000802B3F434005C0000044B000024680004646E6499B86B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:284)#
#1.5 #000802B3F434005C0000044C000024680004646E6499BA7E#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 20 more#
#1.5 #000802B3F434005C0000044D000024680004646E6499CB8B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.core.PortalRequestManagerException: PortalRuntimeException#
#1.5 #000802B3F434005C0000044E000024680004646E6499CD54#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:143)#
#1.5 #000802B3F434005C0000044F000024680004646E6499CE9B#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
#1.5 #000802B3F434005C00000450000024680004646E6499CFDD#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#
#1.5 #000802B3F434005C00000451000024680004646E6499D130#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ContentExceptionHandler.handleException(ContentExceptionHandler.java:100)#
#1.5 #000802B3F434005C00000452000024680004646E6499D277#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ContentExceptionHandler.handlePortalRuntimeException(ContentExceptionHandler.java:27)#
#1.5 #000802B3F434005C00000453000024680004646E6499D512#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.handleRequestException(PortalRequestManager.java:917)#
#1.5 #000802B3F434005C00000454000024680004646E6499D677#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:803)#
#1.5 #000802B3F434005C00000455000024680004646E6499D7F3#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)#
#1.5 #000802B3F434005C00000456000024680004646E6499D943#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 20 more#
#1.5 #000802B3F434005C00000457000024680004646E6499EB58#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: java.lang.UnsupportedOperationException: this implementation does not support getComponentContext()#
#1.5 #000802B3F434005C00000458000024680004646E6499ECFD#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.service.hook.RedirectNode.getComponentContext(RedirectNode.java:50)#
#1.5 #000802B3F434005C00000459000024680004646E6499EE40#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:343)#
#1.5 #000802B3F434005C0000045A000024680004646E6499EF97#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:238)#
#1.5 #000802B3F434005C0000045B000024680004646E6499F0E1#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
#1.5 #000802B3F434005C0000045C000024680004646E6499F21D#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 27 more#
can anyone help us with this problem?
Thanks in advance

The problem was solved, it was a permission problem.
The anonymous role which allow access to the anonymous section of the portal was assigned to anonymous user, but it hasn´t everyone permission. So anonymous users were able to see anonymous pages, but when they login they lose the role, and java iview error happened, unless they had admin rights.
Solved assigned by assigning everyone to that role.
Thanks

Permanent solution for Java iView Runtime error ?

Hi
I have SAP IDES installed in my system...recently i am getting following error when i am trying to login Portal :
Java iView Runtime
Copyright 2002 SAP AG. All rights reserved.
An exception occured while processing your request.
If this situation persists, please contact your system administrator.
I have searched SDN many discussions say that restart server and check memory and...etc......etc
My system also if i restart server problem is solved temprarely....
My system memory is not a problem because i have 16GB Ram amd 1 Tera hard disk still i have 500 GB hard diskk free space...
If i restart simply MMC my J2ee table will not connected so i have to restart hole sytem them start MMC .....then server is up and i can connect to portal .......it seems connection for j2ee table are getting lost.....
Can some one suggest me permanent solution
thanks in advance

Hi Maya,
BEx Web Analyzer requires Portal and is basically a Web template called 0ANALYSIS_PATTERN.
Is Portal configured in your system landscape? If yes try to see if its configured probably using transaction RSPOR_CUST01.
If you have access to SM59, you can test the RFC connection to the portal by running the Test Connection for the corresponding RFC destination ID that you see in RSPOR_CUST01 transaction.
Assign points if helpful
Regards, Uday

Java iview runtime error occuring in EP

Dear Friends ,
We are currently getting java iview runtime error while trying to
access EP logon screen through one of our application server.
We are not facing any errors while trying to access the same logon
screen through the other 2 application servers.
Please look into this issue.
Regards
Gaurav

Hi,
Check whether is there any network problem between application server and CI.
This problem generally comes when there is a problem between connection of UME.
Thanks
Anil

Java iView runtime error on portal 7.3

Hi Experts
There is a specific user who is facing an issue with our client portal version 7.31.
 When the user is trying to access portal link, an error message is observed for the user.This message comes instead of the logon page.
 Error message details :
Java iView Runtime
An exception occured while processing your request.
 Please help to resolve the same.
 The same user is able to logint though citrix.
Regards
Shaily

Hi Shaily,
If this is just happening for one particular user and the same user is able to access the portal through Citrix, this could be a browser issue.
Please ask the user to clear the browser cookies / cache and then try again.
Hope he is using the <FQDN> while accessing the Portal Url.
BR,
Anurag

Java iView runtime error while portal startup

Hi ,
I am facing a problem in starting up the portal .
It was working Fine, But i had to restart it manually through the visual administrator .The J2ee server has started up but not the portal .
following is the error i am getting
Java iView Runtime
Version : 6.4.200512140312
+ Copyright 2002 SAP AG. All rights reserved.
An exception occured while processing your request.
com.sapportals.portal.prt.dispatcher.DispatcherException: Could not find connection portal
com.sapportals.portal.prt.dispatcher.DispatcherException: Could not find connection portal
 at java.lang.Throwable.<init>(Throwable.java:194)
 at java.lang.Exception.<init>(Exception.java:41)
 at com.sapportals.portal.prt.dispatcher.DispatcherException.<init>(DispatcherException.java:45)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:528)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:312)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:368)
 at com.sap.portal.navigation.Gateway.service(Gateway.java:101)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
If this situation persists, please contact your system administrator
Restarting the whole system didn't help too.
I found that ppl faced this problem , but there was no solution given to any . Can anyone help me in bringing up the portal
Thanks in Advances
Lakshmi

Hi Vaibhav ,
DB is running fine , J2EE server is also up .
Below is the log from defaulttrace. we got an error while deploying a par file, and it didn't let us to deploy any par files , then we restarted the system and since then we are facting htis problem. Any chances that an application arroe could bring the whole portal server down? If so can you let me know how to trace and fix it
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)#
_0##0#0#Error##Plain###com.sapportals.portal.prt.dispatcher.DispatcherException: Could not find connection portal#
#1.5#000255532C17004000000AE6000008370004108DF574116A#1144101801300#System.err#sap.com/irj#System.err#Guest#647####aa09ba30c35d11dab15d000255532c17#SAPEngine_Application_Thread[impl:3]_0##0#0#Error##Plain### at java.lang.Throwable.<init>(Throwable.java:194)#
#1.5#000255532C17004000000AE7000008370004108DF57411DA#1144101801300#System.err#sap.com/irj#System.err#Guest#647####aa09ba30c35d11dab15d000255532c17#SAPEngine_Application_Thread[impl:3]_0##0#0#Error##Plain### at java.lang.Exception.<init>(Exception.java:41)#
Thanks,
lakshmi

Java iView Runtime error when try connectin to portal

H, iin my VC i have filled in the address of my portal http://address:50000
Then i click the traffic light icon, and giving me a popup
windows that saying Java iView Runtime
I wonder what could be wrong, i have deployed the portal content and visual composer sda.
And i'm using super user

In fact we're not quite sure on what exactly caused the problem ...
What we did was :
- deploy from NWDS of Webdynpros ... but we don't see how an apllication deployment may has caused a such big issue
- we also enabled 2 services in the portal : Activity Reporting service and Activity data Collector ... may enabling these 2 services have cause this global issue ?
Thanks for your quick response,
Regards,

BI Portal iView Runtime Error

reposted to I believe a more appropriate thread.
Hello,
After a successful integration using SupportDesk tool on our BI Portal (SP14), we were able to successfully test reports but once after publishing it on the PCD - and previewing it gives me an error:
*Portal Runtime Error
An exception occurred while processing your request
Exception id: 11:20_13/10/08_0008_3165050
See the details for the exception ID in the log file.*
How do we resolve this? It says
the log from the defaultTrace is as follows:
[EXCEPTION]
{0}#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template
the problem occured at position 138. Cannot process expression <FPN.PCDHomeLocation>
This one's weird since I believe we did not alter any FPN settings as we have no plans to implement FPN yet
Thank you all.
Edited by: Jan Michael Jaudian on Oct 13, 2008 9:31 AM

Hi ,
The problem might be due to system alias settings, these links might help.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/connectivity
BI Workbooks and the Application Integrator
regards
Naresh Garg

Java iView Runtime Error while loading EP Logon page

hi,
When i load my Enterprise Portal from the url http://epserver:50000/irj/portal i am getting the following error page.
Anyone please help me in this issue.
The Error Page content is given below:
Java iView Runtime
Version : 6.4.200410200018
+ Copyright 2002 SAP AG. All rights reserved.
An exception occured while processing your request.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:296)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:316)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:372)
     at com.sap.portal.navigation.Gateway.service(Gateway.java:68)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     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: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:276)
     ... 24 more
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.runtime.system.hooks.ErrorComponent
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
     at com.sapportals.portal.prt.connection.ContentExceptionHandler.handleException(ContentExceptionHandler.java:67)
     at com.sapportals.portal.prt.connection.ContentExceptionHandler.handlePortalRuntimeException(ContentExceptionHandler.java:27)
     at com.sapportals.portal.prt.core.PortalRequestManager.handleRequestException(PortalRequestManager.java:917)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:803)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
     ... 24 more
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.prt.component.error.ErrorComponent of Portal Component com.sap.portal.runtime.system.hooks.ErrorComponent because: Could not instantiate implementation class
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
     at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
     at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
     at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
     ... 32 more
Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application com.sap.portal.themes.lafservice
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:413)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:385)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem._refresh(PortalApplicationItem.java:505)
     at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoader(PortalApplicationItem.java:1334)
     at com.sapportals.portal.prt.core.broker.PortalComponentItem.getClassLoader(PortalComponentItem.java:569)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getClassLoader(PortalComponentItemFacade.java:102)
     at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
     ... 36 more
If this situation persists, please contact your system administrator.

hi sir,
i checked that .... J2ee Service is running.
Sorry for not including default.trc log file error in my first message.
Here it is ...
JMX connector exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 3584000 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3584000,SAP_J2EECluster="" null null null ]
[EXCEPTION]
com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 314 | src: cluster target-node: 3584000 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3584000,SAP_J2EECluster="" null null null ]
     at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:531)
     at com.sap.engine.services.jmx.RequestMessage.getParams(RequestMessage.java:580)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:90)
     at com.sap.engine.services.jmx.JmxServiceConnectorServer.receiveWait(JmxServiceConnectorServer.java:172)
     at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:81)
     at com.sap.engine.core.cluster.impl6.ms.MSListenerThread.run(MSListenerThread.java:47)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
Caused by: javax.management.InstanceNotFoundException: MBean with name com.sap.default:name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=3584000,SAP_J2EECluster=NET not found in repository
     at com.sap.pj.jmx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1408)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getClassLoaderFor(MBeanServerWrapperInterceptor.java:455)
     at com.sap.engine.services.jmx.CompletionInterceptor.getClassLoaderFor(CompletionInterceptor.java:576)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getClassLoaderFor(BasicMBeanServerInterceptor.java:438)
     at com.sap.jmx.provider.ProviderInterceptor.getClassLoaderFor(ProviderInterceptor.java:330)
     at com.sap.engine.services.jmx.RedirectInterceptor.getClassLoaderFor(RedirectInterceptor.java:501)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getClassLoaderFor(MBeanServerInterceptorChain.java:443)
     at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:525)
     ... 8 more

Java Iview Runtime error at the time of logon

Hi All
i am getting the below error page instead of Portal log on Page.
At the same time when i am connecting to the NWA it is opening successfully,
There I am getting the login Page also.
But when i am trying http://<Server>:50000/irj/portal.
i am getting below error.
Java iView Runtime
Copyright 2002 SAP AG. All rights reserved.
An exception occured while processing your request.
If this situation persists, please contact your system administrator.
I have not touch the portal logon Page.
Neither i have modified any standard Portal page.
Kindly help me with you valuable suggestion and document.
It is effecting the business process of client.
Prashant krishen

Hi Robin,
Thanks for immediate response.
Please help me to find out the log.
i am using this path :
http://<Server>/irj/servlet/prt/portal/prtroot/com.sap.portal.runtime.admin.logviewer.defau
But here in the default trace there are so many default trace file like
defaultTrace.0.trc ;
defaultTrace.1.trc ;
defaultTrace.2.trc ;
defaultTrace.3.trc
defaultTrace.4.trc ;
defaultTrace.5.trc ;
in all the file date has not been maintained. That is why i am not able to send you the exact log .
kindly help me to find the log .
thanx in Advance.

Url iview showing error when displaying a page with frames

Hi,
I have a requirement of putting a site in a url iview in the portal. I created a url iview and when I preview it, it displays correctly. When I assign this to a role and access it through the navigation, it gives an error.
The weird thing is that, it works sometimes and it does not work sometimes. The url I am trying to display is working fine, because even when the portal shows error, if I try the url straight from the browser, it loads without any errors.
So what could be the problem? The site I am trying to display contains frames. Could this be the problem? If so, why is it working sometimes and does not work sometimes?
Thanks in advance.
Regards
Ranjith

Hi Martin,
The issue is still there. But one interesting thing that was noticed by my team mate was that if you add the site to the list of sites on browser which can use cookies, everything works fine. Similarly, if I reduce the privacy setting of my browser to Low, it works fine.
Again, even if you keep the privacy setting as Medium and does not allow the site to use cookies, the iview opens fine if you open it in a new window.
Any thoughts on this?
Thanks & Regards
Ranjith

Portal Java Iview Runtime - Urgentt

dear All Portalers,
we got high issues when SAP ESS/MSS Implementatin for our customer, we got issue about HTTP Session maximum and cause error message "Java Iview Runtime .."
first, this is our landscape
1. We Have SAP EP 7 installed with UME integrated with LDAP (Ms. Exchange 2003)
2. We use SAP ECC 6 SR3 as our Backend System
3. We use ALL SSL Commnunication between Portal and Backend
4. We use SPNEGO for User Authentication Mechanism, so User Join Domain, directly open portal when run Internet Explorer between input User and password
5. Each Uses LDAP mapped use User Mapping
But, after we launch to customer, we got big problem about Session
Here, reproduce the error
1. User Join to Network Domain ( e.g. CORP.CO.ID)
2. After User/laptop join Network Domain and open browser https://portal.CORP.co.id/
3. Directly, User logon automatically at Home of SAP ESS/MSS
4. User finish transaction at SAP Portal and want to Out from Portal by Log off, but after Log off automatically back to entry ( is is Normal ??? )
5. User very annoying, so user close browser
6. After 10 seconds, user Open Browser again, open browser https://portal.CORP.co.id/ but user got this message
"Java Iview Runtime...bla bla bla"
can any help us , i already set OSS Message Very High ... but didn't solve this problem
thanks
regards
ghochi

Hi Ghochi,
First if you want user not to directly log in to Portal then disable the automatic logon setting frominternet explorer.
Tools > Internet Options > Advance > Enable internet Authentication (uncheck checkbox) restart browser. Next time user will not directly login to Portal. But user needs to enter user ID/PWD every time.
Coming to your problem for http sessions,
1. On click of log off button, sessions are not getting released. Please check what is the value once user clicks on log off button. This you can check in Visual admin.
2. Also, go to SM04 in ECC and check how many http sessions you are having.
Thanks.
Sushil

Java iView Runtime error occurs whilw changing Theme Editor

Hi,
i have to face the following error while changing Theme.
Java iView Runtime
Version : 6.4.200512140312
+ Copyright 2002 SAP AG. All rights reserved.
An exception occured while processing your request.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 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:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:284)
 ... 20 more
Caused by: java.lang.OutOfMemoryError
If this situation persists, please contact your system administrator.
Please give me right solution.
Thanks & Regards,
Nisarg Patel

Hi,
 Try out the answers given in the following threads:
Theme Editor : Runtime error
Problem with Theme Editor
Regards,
Pooja.

Portal URL iview runtime error

Similar Messages

Maybe you are looking for