Runtime error in Web Dynpro Application

Hi Experts,
I am getting a runtime error from a custom Web dynpro Application. The error details are
Category               ABAP Programming Error
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
Except.                CX_SY_REF_IS_INITIAL
Web Dynpro Component   Z*
ABAP Program           /1BCWDY/0O2TGWNVA3D2IUW3YFXJ==CP
Application Component Not Assigned
Could someone please help on resolving this error.
-Regards,
Ragavan

Hi,
Add additional info including the ST22 dump for security you can run find and replace in the st22 dump text and relplace ahost name and sid.
Also when do you get this dump exactly i.e. what are you doing or how are you accessing the webdynpro for the error to be generated.
What is your system patch and kernel levels.
Please provide more information otherwise this is just a guessing game.
Johan

Similar Messages

500Internal Server Error The Web Dynpro application PageBuilder has expired

hi all ,
i am using public url domain to access my portal through internet . i have done a reverse proxy using apache . from my server url i am able to get every page . from public url i am not able to view my webdynpro applications . its showing the following error
500 Internal Server Error
SAP J2EE Engine/7.01
The Web Dynpro application 'PageBuilder' has expired. Restart the application. Choose 'Refresh' in the iView tray or use the browser 'Refresh' button to restart the iView
Details: No details available
i got this log file in the portal
Full Message Text
Session unknown: Request with URI=/webdynpro/dispatcher/sap.com/pb/PageBuilder was sent to unknown session. Either request with wrong session parameters was sent, or session has expired before Wed Oct 20 21:47:46 IST 2010. Current request parameters={sap-ext-sid=DL7cHVE6DiKdbE9gwYkSdg5A6q8C_OKOzgxi0HoLa2iw, sap-wd-cltwndid=WID1287644121668, sap-wd-norefresh=X, sap-ep-version=7.0104.20090422102234.0000}. Is termination request=false. Request was sent from host with IP=172.31.11.95/name=172.31.11.95. Hint: see SAP note 842635 for more details on session expiration. RID=a16ac995dcdf11dfb3e70021281821ee
[EXCEPTION]
com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Session has expired (current request: follow-up request). Please restart the application. Hint: HttpSession seems to be expired due to user inactivity or application is called with wrong URL parameter (sap-wd-norefresh=X).
at com.sap.tc.webdynpro.clientserver.session.RequestManager.findClientSession(RequestManager.java:258)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:146)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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(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)
can anybody helpme in this issue

Hello,
Please see this post:
The Web Dynpro application 'PageBuilder' has expired
I think the problem is solved in this post.
Regards.

Navigation Error in Web Dynpro Application

Hi All,
I developed a web dynpro application with 2 views.
I implemented the navigation paths(in and outbound plugs). I have a Next button in the first view and when
I clicked the next button it opened the second view.
It was working fine until, i created custom controller
and defined model node and model binding by calling RFC.
In the first view, i created a model node corresponding to the custom controller model node and defined the context mapping between the first view and the custom controller.
When I run the application (the first view displays data calling RFC) once I clicked the next button i got this error message.
com.sap.tc.webdynpro.progmodel.context.ContextException: Path null does not point to an attribute, but to com.sap.tc.webdynpro.progmodel.generation.DelegatingView@8fc86f
     at com.sap.tc.webdynpro.progmodel.context.Paths.createAttributePointer(Paths.java:94)
     at com.sap.tc.webdynpro.clientserver.uielib.standard.impl.AbstractInputField.getValue(AbstractInputField.java:1050)
     at com.sap.tc.webdynpro.clientserver.uielib.standard.impl.AbstractInputField.getValue(AbstractInputField.java:1098)
     at com.sap.tc.webdynpro.clientimpl.html.uielib.standard.uradapter.InputFieldAdapter.getValue(InputFieldAdapter.java:550)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.InputFieldRenderer.render(InputFieldRenderer.java:41)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:269)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:95)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.GridLayoutRenderer.renderGridLayoutCellFragment(GridLayoutRenderer.java:626)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.GridLayoutRenderer.renderGridLayoutRowFragment(GridLayoutRenderer.java:330)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.GridLayoutRenderer.renderGridLayoutFragment(GridLayoutRenderer.java:261)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.GridLayoutRenderer.render(GridLayoutRenderer.java:57)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:269)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:95)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.GroupRenderer.renderGroupFragment(GroupRenderer.java:1030)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.GroupRenderer.render(GroupRenderer.java:49)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:269)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:95)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.FlowLayoutRenderer.renderFlowLayoutItemFragment(FlowLayoutRenderer.java:177)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.FlowLayoutRenderer.renderFlowLayoutFragment(FlowLayoutRenderer.java:148)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.FlowLayoutRenderer.render(FlowLayoutRenderer.java:33)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:269)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:95)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.ScrollContainerRenderer.renderScrollContainerFragment(ScrollContainerRenderer.java:344)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.ie6.ScrollContainerRenderer.render(ScrollContainerRenderer.java:41)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:269)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:95)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.UiWindowRenderer.render(UiWindowRenderer.java:43)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:269)
     at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.AbstractRenderManager.render(AbstractRenderManager.java:95)
     at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendHtml(HtmlClient.java:522)
     at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse(HtmlClient.java:351)
     at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse(HtmlClient.java:251)
     at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse(HtmlClient.java:204)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:669)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     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:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Can anyone please tell me what is the reason for this?
and how to fix it?
Thanks

Hi
Are you having any inputfields in your next view?If yes then check if you have bound the context attribute to it.
I think you haven't done that.
Regards,
Ajay

Error when web dynpro application is deployed

Hi,
I get this error when i deploy the web dynpro application
Could you please help to know wat it is about ? my application is extremely simple hello world application.
java.lang.ClassNotFoundException: helloworld.wdp.InternalHelloworld -
Loader Info -
ClassLoader name: [local/helloworld] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization sap.com/tcwddispwda sap.com/tcwdcorecomp service:webdynpro service:sld library:tcddicddicservices library:com.sap.aii.proxy.framework library:tcgraphicsigs library:com.sap.mw.jco library:com.sap.lcr.api.cimclient library:sapxmltoolkit library:com.sap.aii.util.rb library:com.sap.util.monitor.jarm library:tcddicddicruntime library:com.sap.aii.util.xml library:com.sap.aii.util.misc library:tc~cmi Resources: D:\usr\sap\ID6\DVEBMGS00\j2ee\cluster\server0\apps\local\helloworld\webdynpro\public\lib\app.jar Loading model: {parent,references,local} -
thanks......

Hi Murtuza,
I have done it.
Reload means I closed and opened the project
but still i get the error
this time it also says negative cache
The initial exception that caused the request to fail, was:
java.lang.ClassNotFoundException: helloworld.wdp.InternalHelloworld Found in negative cache -
Loader Info -
ClassLoader name: [local/helloworld] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization sap.com/tcwddispwda sap.com/tcwdcorecomp service:webdynpro service:sld library:tcddicddicservices library:com.sap.aii.proxy.framework library:tcgraphicsigs library:com.sap.mw.jco library:com.sap.lcr.api.cimclient library:sapxmltoolkit library:com.sap.aii.util.rb library:com.sap.util.monitor.jarm library:tcddicddicruntime library:com.sap.aii.util.xml library:com.sap.aii.util.misc library:tc~cmi Resources: D:\usr\sap\ID6\DVEBMGS00\j2ee\cluster\server0\apps\local\helloworld\webdynpro\public\lib\app.jar Loading model: {parent,references,local} -

Runtime error in web dynpro java

Hi friends,
i have designed and run the project for adobe pdf form,compliation is ok...but it produce runtime error please tel me what is error how to rectify that...
The error is
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"https://<name>.us:443/AdobeDocumentServices/Config?style=document"
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:980)
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1430)
    at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:78)
    at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:95)
    at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:385)
    ... 35 more
Thanks in advance
Manee R

Hi Mani,
To be able to use PDF forms in Web Dynproapplications:
&#56256;&#56442;SAPNetWeaverDeveloper Studio(minimum SPS 11) is installed
&#56256;&#56442;Adobe LiveCycleDesigner7.0 is installed
&#56256;&#56442;Adobe Reader7.0.x is installed
&#56256;&#56442;SAP NetWeaverWeb AS Javacompatible with the DevStudiois installed
&#56256;&#56442;The Adobe Document Servicesare deployed and configured on the SAP J2EE Engine.
&#56256;&#56442;The Active Component Framework(ACF) of the Interactive Forms integration is installed. (not mandatory)
Check this.
reg errors in webdynpro runtime
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2b6db1c4-0801-0010-faa5-ff4b4df55b45
Regards,
Mithu

Deployment error for Web Dynpro application

Hello, I have developed a new Web Dynpro Welcome application in my local system, which is my laptop. I have both the NW Dev Studio and the app server on my laptop.
When I try to deploy and run the application I get the below error. As far I am concerned I have logged in as j2eadm user and trying to deploy.
Appreciate your help to resolve the error
Sep 23, 2007 6:26:57 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[002]Deployment aborted
Settings
SDM host : Natasha
SDM port : 50018
URL to deploy : file:/C:/WINDOWS/TEMP/temp6475Welcome.ear
Result
=> deployment aborted : file:/C:/WINDOWS/TEMP/temp6475Welcome.ear
Aborted: development component 'Welcome'/'local'/'LOKAL'/'0.2007.09.23.18.26.49':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted

As per the procedure given in 3rd point I have changed the j2eadm password but it gives me the below error when I try to redeploy and run
Result
=> deployment aborted : file:/C:/WINDOWS/TEMP/temp26493Welcome.ear
Aborted: development component 'Welcome'/'local'/'LOKAL'/'0.2007.09.25.22.11.45':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [Natasha] with user name: [admin] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment exception : The deployment of at least one item aborted

The Web Dynpro application 'PageBuilder' has expired

Hi Alll,
We are implementing ESS/MSS and the Portal was working fine.
We set it up for SSL/https and it was working just fine. However when we call it from reverse proxy server the web dynro applications through the following error:
The Web Dynpro application 'PageBuilder' has expired. Restart the application. Choose 'Refresh' in the iView tray or use the browser 'Refresh' button to restart the iView
Details: No details available
When I tested this with a transaction iview they work just. Also when tested directly from Portal they work fine.
Can anyone assist on this please?
Thanks,
Mike

Hello Mike,
After a user is logged in and requested an ESS/MSS application. The pagebuilder service is requested to built the page.
When the user is still logged in but is not working with this application the pagebuilder receives a timeout after a while and the session is expired. The pagebuilder has sometimes the status stopped, you can see this in the Netweaver Administrator. (Search for the pb in the application area)
If an other user is requesting an application the pb service is started again and the page built again.
If you want to get rid of the warning you could set the "timeout" parameter to a higher value in the configtool.
Kind regards,
Marcel

The Web Dynpro Application 'Explorer' has expired

hi,
when I am trying to open the deployed content in the
Content Administrator in the sap portal I am getting the following error
"500   Internal Server Error The Web Dynpro Application 'Explorer' has expired. Restart the application using the Refresh button or via the following link Explorer.
Details:
No details available"
what can I do?
I have read here at sdn that I should increase the expiration time but where can I do this?

Hi Thorsten,
Close your explorer, open a new explorer and run the application from the new browser.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b52de690-0201-0010-c5a6-b4bde0a12e44
<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_ep_sys/~form/handler">SAP Note Number: 519191</a>
<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_fes/~form/handler">SAP Note Number: 856741</a>
Regards,
Mithu

The Web Dynpro Application 'PcrApplication' has expired.

Hi,
I am getting below error:-
500 Internal Server Error:
The Web Dynpro Application 'PcrApplication' has expired. Please restart the application either with the refresh button or click the following link PcrApplication.
Can anyone help me on this.
Best regards
Ali

Hi Rali,
I think you have not been using this application from long time. So the Portal session time must have expired. Well, Let us know if the problem persist even after RESTART of the browser.
Regards
<i><b>Raja Sekhar</b></i>

Web Dynpro application Session time expired in Portal

Hi All ,
   I am runnnig my web dynpro application in portal. When i log in for first time its working fine. But if if lof off and try to log in again in portal in same browser and try to access that web dynpro application then i am gettting error as follows in the browser. And even if i click on link the application could not be refreshed/opened.
500   Internal Server Error
The Web Dynpro Application 'WhowhoAppl' has expired. Restart the application using the Refresh button or via the following link WhowhoAppl.
Details:   No details available
I am also sending detail log trace below. Reply how to send this issue.
#1.#001083FEF475004D00000024000003E00004458D7D628B13#1202373905933#com.sap.tc.we
bdynpro.sessionmanagement#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmana
gement.ExceptionHandler.handleExpiration#J2EE_GUEST#0####fb017f90d55811dc93ff001
083fef475#SAPEngine_Application_Thread[impl:3]_31##0#0#Warning#1#/System/UserInt
erface#Java###Session unknown: Request with URI= was sent to unknown session.
Either request with wrong session parameters was sent, or session has expired b
efore . Current request parameters=. Is termination request=. Request w
as sent from host with IP=/name=. Hint: see SAP note 842635 for more detai
ls on session expiration. RID=
[EXCEPTION]
#8#/webdynpro/dispatcher/asianpaints.com/Whoswho/WhowhoAppl#Thu Feb 07 07:44
:39 IST 2008#{}#false#172.18.40.57#172.18.40.57#faf5bfc0d55811dccc92001083fef475
#com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Sess
ion has expired due to a concurrent invalidation or logoff request. Hint: This m
ight occur if multiple logoff requests are sent to Web Dynpro by the portal as i
t is the case when a logoff is executed and the portal has active embedded and i
solated Web Dynpro applications. Only the first logoff request is processed, all
following logoff requests will lead to this message but but can be ignored. Ple
ase restart the application.
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doSessionMana
gementPostProcessing(ClientSession.java:868)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(
ClientSession.java:302)
        at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing
(RequestManager.java:149)
        at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doConte
nt(DispatcherServlet.java:62)
        at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(D
ispatcherServlet.java:46)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServle
t(HttpHandlerImpl.java:401)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleReq
uest(HttpHandlerImpl.java:266)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServle
t(RequestAnalizer.java:387)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServle
t(RequestAnalizer.java:365)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebCo
ntainer(RequestAnalizer.java:944)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(Requ
estAnalizer.java:266)
        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:9
5)
        at com.sap.engine.services.httpserver.server.Processor.request(Processor
.java:175)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSes
sionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRu
nner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:3
7)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.ja
va:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:1
70)
Edited by: kavita chavan on Feb 8, 2008 12:04 PM

Default expiry time of a webdypro is 3600 sec.Try to increase it in the visual j2ee admin tool.

How to display the error message during the web dynpro application runtime

hi,
    I'm a java developer,During i 'deploy and run ' a web dynpro application on server-1,if the application have some runtime errors. there are displayed many infomation about the runtime error,such as exception track,etc.
    But when i do the same on server-2,there just show something like:
            500   Internal Server Error
                                SAP NetWeaver Application Server 7.00/Java AS 7.00
            Failed to process request. Please contact your system administrator.
but the server-1 will stop the j2ee engine.
how can do i make server-2 show detail error message as server-1. when i debug web dynpro application need these infomation.
Appreciate your inputs...
(Note:server-1 and server-2 have same software version)
Edited by: BingLin Zhong on Feb 18, 2008 2:13 AM

The Sap-Notes 962319:
1. Check in the Visual Administrator, "Licensing Adapter" -> "General" -> "SystemType" !
If it is set to "DEVELOPMENT_MODE", verbose error messages are shown.
If it is undefined, proceed with the next step.
If it is set to something else, only exception IDs are shown. In this case the only chance is to search for this exception ID in the default traces.
2. If the system type is undefined, then in the Config Tool "Configurations" -> "webdynpro" -> "sap.com" -> "tcwddispwda" -> "Propertysheet default" -> "DevelopmentMode" is evaluated. If it is "true", verbose error messages are shown.
3. If verbose error messages are required but still the short version is shown, you probably face an error message that is not raised by Web Dynpro but by other components of the NetWeaver. In the Visual Administrator set "Properties" -> "HTTP Provider" -> "DetailedErrorResponse" to "true".
4. In addition to the error page shown in the browser or client, important messages - including error messages and stack traces - are written to the log and trace files, e.g. to the default traces usr\sap\<SID>\<instance>\j2ee\cluster\server<number>\log\defaulttrace.trc.<number>.
a) In some cases, when an exception ID is included in the error message, the detailed error message can easily be retrieved in the log file.
b) When no exception ID is given, you have to search for the detailed error message in the log specifying time stamp and/or user ID.
Always consider restarting the system after making changes on the settings.
It is not recommended to switch the "SystemType" to an inappropriate value just for viewing verbose error messages. The system type potentially affects framework, applications and licensing in an perhaps unintended way.
In the past there was no distinction between different system types regarding error messages. For security reasons this distiction has been introduced. It is not intended to show stack traces in non-development systems in the future. SAP does not provide workarounds or patches to enable such a behaviour again.

Error - Creating a Web Dynpro Application Accessing ABAP Functions

Dear All,
we are trying to implement a web dynpro application with accessing ABAP functions.
Previous tasks:
-     insert the ABAP system into the SLD from the NWDI System (Transaction RZ70; the ABAP system is correctly insert into the SLD => technical systems)
-     equipped the JCO connections with the web dynpro content manager (ping and test = OK)
Its the standard tutorial out of the SDN called Creating a Web Dynpro Application Accessing ABAP Functions.
Some hints:
-     There are no errors after the implementation and the rebuild of the project in the NWDS
-     The auto deployment works fine to the development runtime system. The application is shown in the Web Dynpro content manager
-     The In the build log I found these entries:
System.err] [Invoked from com.sap.s2x.tools.GUID.getnodeaddress(GUID.java:585)]
[System.err] java.net.UnknownHostException: FRASAPP562: FRASAPP562
[System.err]      at java.net.InetAddress.getLocalHost(InetAddress.java:1191)
[System.err]      at com.sap.s2x.tools.GUID.getnodeaddress(GUID.java:575)
[System.err]      at com.sap.s2x.tools.GUID.<clinit>(GUID.java:179)
[System.err]      at com.sap.s2x.tools.S2XGUID.getGUID(S2XGUID.java:19)
[System.err]      at com.sap.ide.metamodel.core.i18n.LanguageState.createS2XID(LanguageState.java:191)
[System.err]      at com.sap.ide.metamodel.core.i18n.S2XLanguageUnmarshaller.unmarshal(S2XLanguageUnmarshaller.java:52)
[System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.loadLanguageState(TextPoolProxy.java:703)
[System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.prepareLanguageForRead(TextPoolProxy.java:646)
[System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.isEmpty(TextPoolProxy.java:222)
[System.err]      at com.sap.ide.webdynpro.checklayer.MDOChecker.check(MDOChecker.java:23)
[System.err]      at com.sap.ide.webdynpro.checklayer.view.ViewChecker.check(ViewChecker.java:52)
[System.err]      at com.sap.ide.webdynpro.checklayer.controller.ViewControllerChecker.check(ViewControllerChecker.java:96)
[System.err]      at com.sap.ide.webdynpro.checklayer.controller.ControllerChecker.check(ControllerChecker.java:119)
[System.err]      at com.sap.ide.webdynpro.checklayer.controller.ControllerChecker.check(ControllerChecker.java:56)
[System.err]      at com.sap.ide.webdynpro.checklayer.component.ComponentChecker.check(ComponentChecker.java:181)
[System.err]      at com.sap.ide.webdynpro.checklayer.component.ComponentChecker.check(ComponentChecker.java:56)
[System.err]      at com.sap.ide.webdynpro.generation.Generation.check(Generation.java:2039)
[System.err]      at com.sap.ide.webdynpro.generation.Generation.generatePersistentComponent(Generation.java:1296)
[System.err]      at com.sap.ide.webdynpro.generation.console.GenerationConsole.generate(GenerationConsole.java:175)
[System.err]      at com.sap.webdynpro.generation.ant.GenerationAnt.main(GenerationAnt.java:50)
[System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[System.err]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[System.err]      at java.lang.reflect.Method.invoke(Method.java:324)
[System.err]      at com.sap.webdynpro.generation.ant.WDGenAntTask.execute(WDGenAntTask.java:219)
[System.err]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[System.err]      at org.apache.tools.ant.Task.perform(Task.java:364)
[System.err]      at org.apache.tools.ant.Target.execute(Target.java:341)
[System.err]      at org.apache.tools.ant.Target.performTasks(Target.java:369)
[System.err]      at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
[System.err]      at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:112)
[System.err]      at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:61)
[System.err]      at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:213)
[System.err]      at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:190)
[System.err]      at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
[System.err]      at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
[System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[System.err]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[System.err]      at java.lang.reflect.Method.invoke(Method.java:324)
[System.err]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
[System.err]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:102)
[System.err]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:76)
[System.err]      at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)
[System.err]      at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
[System.err]      at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1495)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.build(CBSBuildController.java:727)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.execCommand(CBSBuildController.java:503)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.evalCmdLine(CBSBuildController.java:442)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.run(CBSBuildController.java:314)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.exec(CBSBuildController.java:252)
[System.err]      at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:207)
-     Im able to start the application out of the Web Dynpro content manager with run => only the user interface is displayed without any functionality
-     The normal start over the NWDS fails => error text
com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'local/J08_Flugdat_Daventdcflight~xxx.com' and application 'FlightListApp' are not deployed on the server. Please check the used URL for typos.
There two different URLs in use.
Start via NWDS:
http://frasapp562:50000/webdynpro/dispatcher/J08_Flugdat_Daventdcflight~xxx.com/FlightListApp
Start via web dynpro content manager:
http://frasapp562:50000/webdynpro/dispatcher/xxx.com/aventdc~flight/FlightListApp
For test purposes, we started the BAPI (BAPI_Flight_Getlist) on the ABAP system directly. It works.
Any ideas about the system behaviours (different URLs and missing functionality)?
Thanks a lot in advanced!
Best regards
Christoph

The Error has been solved The implementation of a method was missing....
Thx
Christoph

I am getting a error while executing the Web Dynpro Application Page.

Hi All,
I am getting a Error while executing a web dynpro application :::
: Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component: Z_WEP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
I have checked this error description in ST22 :
What happened?
    The exception 'CX_WDR_RT_EXCEPTION' was raised, but it was not caught anywhere
     along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
     'CL_WDR_CLIENT_APPLICATION=====CP' has to be
    terminated.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_WDR_RT_EXCEPTION', was not caught
     and
    therefore caused a runtime error.
    The reason for the exception is:
    Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component:
    Z_XXP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
Can u plz help me regarding this error.
Thanks,
Deepika

>Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered
Looks to me like you are trying to fire a navigation plug within WDDOMODIFYVIEW. According to the rules of the WD Phase Model this is not allowed.

Web Dynpro application callable object error: Page Builder Not available

Hi, SDN Fellow.
I created a callable object of Web Dynpro application. The callable object is atatched to an Action, and Action --> Block, and Block --> Process.
I initiate the process in GP Runtime, when it comes to the Action screen the Web Dynpro application atatched to, I got the following error:
The page builder required to display this application UI inside the portal environment is not available.
As aa comparison, another callable object that atatched to a Web Dynpro component (that implement GP interface) is working fine.
Please advise.
Thanks in advance,
KC

Hi KC,
When you start your process from GP Runtime, does the actual action/callable object open in a new window?
Have a look at this SAP Note:
[Error when executing a GP task - Page builder|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_gp/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393831353137%7d]
Although the error message you are getting is different, but if your callable object opens in a new window, then the problem (in most probability) is the same as mentioned in the SAP Note.
Also, try testing the Web Dynpro callable object in standalone mode. For more information on this, see:
[Testing Callable Objects|http://help.sap.com/saphelp_nw04s/helpdata/en/4c/588041a17e060de10000000a1550b0/frameset.htm]
Bye
Ankur

First Web Dynpro application error

Hi,
I'm new to SAP portal development, when I tried to deploy my first web dynpro application, I getting the below error. I have followed exactly the same procedure described in the tutorials. I'm using NW Sneak preview. What is DC mean?
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Hide details
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0, version: null, DOM version: null, client type: ns7, client type profile: nn7, ActiveX: disabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
Web Dynpro code generators of DC local/Welcome:
SapDictionaryGenerationCore: 6.4010.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-12-13:22:15:29[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4010.00.0000.20041213121535.0000 (release=630_VAL_REL, buildtime=2004-12-13:22:19:39[UTC], changelist=312712, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4010.00.0000.20041126121122.0000 (release=630_VAL_REL, buildtime=2004-12-13:22:08:55[UTC], changelist=306364, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4010.00.0000.20041209081817.0000 (release=630_VAL_REL, buildtime=2004-12-13:22:37:37[UTC], changelist=311488, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4010.00.0000.20041209081817.0000 (release=630_VAL_REL, buildtime=2004-12-13:22:37:37[UTC], changelist=311488, host=PWDFM026)
SapGenerationFrameworkCore: 6.4010.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2004-12-13:22:07:58[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4010.00.0000.20041104141931.0000 (release=630_VAL_REL, buildtime=2004-12-13:22:24:21[UTC], changelist=298465, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4010.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-12-13:22:12:38[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4010.00.0000.20041126121122.0000 (release=630_VAL_REL, buildtime=2004-12-13:22:09:08[UTC], changelist=306364, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4010.00.0000.20041104141931.0000 (release=630_VAL_REL, buildtime=2004-12-13:22:24:53[UTC], changelist=298465, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: (unknown)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
No information available
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_07-b05, vendor: Sun Microsystems Inc.
Operating system:
Windows XP, version: 5.1, architecture: x86
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for view com.sap.examples.welcome.StartView. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
     at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.<init>(DelegatingView.java:41)
Caused by: java.lang.NoSuchMethodError: com.sap.tc.webdynpro.progmodel.gci.GCIContext.createMappedAttribute(Ljava/lang/String;Ljava/lang/String;Z)Lcom/sap/tc/webdynpro/progmodel/gci/IGCIAttributeInfo;
     at com.sap.examples.welcome.wdp.InternalStartView.<init>(InternalStartView.java:43)
     ... 36 more

Hi Siva,
to my understanding - your problem has nothing to do with J2EE server configuration - your application is already deployed on the server and running (brings error though):
at com.sap.examples.welcome.wdp.InternalStartView.<init>(InternalStartView.java:43)
so your class is already called.
DC = Development Component, but if you created a "simple" WebDynpro project - you should read the hint as "are you sure your project is properly deployed?"
I got similar messages (see your quota about NoSuchMethodException - I'm not really sure I was getting NSME, but definitely "Failed to create delegate for view") in case a Java-type context attribute was not initialized (e.g. you create context attribute of type java.util.Properties, do not put any object there, and request the attribute value). Check if you properly initialize context attributes.
Another thing - I presume you're running DevStudio of the same version as your server. DevStudios of different versions generates different sources - there could be problems in run-time when out of synchronization.
Best regards,
Nick

Runtime error in Web Dynpro Application

Similar Messages

Maybe you are looking for