cancel
Showing results for 
Search instead for 
Did you mean: 

Webdyn App doesnt work due to WDTypeNotFoundException, DdException & WebUIE

Former Member
0 Kudos

Hi

My webdynpro application does not work due to the following exception. The stack trace is give below.

But another application accessing another RFC model works. Even if i create a new project using this RFC it wont work.

Please kindly help me regarding this issue.

Environment

-


NWDS SP 9

ADS SP 9

STACK TRACE

-


#1.5#00123F57561D00460000003C00000D7C00040FABD316F9C7#1143130562156#com.sap.engine.services.servlets_jsp.client.RequestInfo#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfo#Guest#2####52122390ba8811dab38100123f57561d#SAPEngine_Application_Thread[impl:3]_39##0#0#Warning##Plain###Cannot send an http error response [500 Application error occurs during processing the request. (details: <pre>com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type extern:com.test.model.types.AdRFCModel:com.test.model.types.Ztmi_Tdat could not be loaded: com.sap.dictionary.runtime.DdException:

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure&\#40;DataTypeBroker.java:297&\#41;

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init&\#40;NodeInfo.java:753&\#41;

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init&\#40;NodeInfo.java:761&\#41;

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init&\#40;NodeInfo.java:761&\#41;

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init&\#40;NodeInfo.java:761&\#41;

at com.sap.tc.webdynpro.progmodel.context.Context.init&\#40;Context.java:40&\#41;

at com.sap.tc.webdynpro.progmodel.controller.Controller.init&\#40;Controller.java:199&\#41;

at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal&\#40;Component.java:433&\#41;

at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext&\#40;Component.java:371&\#41;

at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext&\#40;Component.java:400&\#41;

at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.initAttributeMapping&\#40;AttributeInfo.java:582&\#41;

at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init&\#40;AttributeInfo.java:442&\#41;

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes&\#40;NodeInfo.java:771&\#41;

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init&\#40;NodeInfo.java:756&\#41;

at com.sap.tc.webdynpro.progmodel.context.Context.init&\#40;Context.java:40&\#41;

at com.sap.tc.webdynpro.progmodel.controller.Controller.init&\#40;Controller.java:199&\#41;

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView&\#40;ViewManager.java:540&\#41;

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot&\#40;ViewManager.java:422&\#41;

at com.sap.tc.webdynpro.progmodel.view.ViewManager.init&\#40;ViewManager.java:130&\#41;

at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController&\#40;InterfaceView.java:41&\#41;

at com.sap.tc.webdynpro.progmodel.controller.Controller.init&\#40;Controller.java:200&\#41;

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent&\#40;ClientComponent.java:134&\#41;

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init&\#40;ClientApplication.java:374&\#41;

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute&\#40;WebDynproMainTask.java:593&\#41;

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks&\#40;AbstractClient.java:59&\#41;

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing&\#40;ClientManager.java:249&\#41;

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing&\#40;DispatcherServlet.java:154&\#41;

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent&\#40;DispatcherServlet.java:116&\#41;

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet&\#40;DispatcherServlet.java:48&\#41;

at javax.servlet.http.HttpServlet.service&\#40;HttpServlet.java:740&\#41;

at javax.servlet.http.HttpServlet.service&\#40;HttpServlet.java:853&\#41;

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet&\#40;HttpHandlerImpl.java:385&\#41;

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest&\#40;HttpHandlerImpl.java:263&\#41;

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet&\#40;RequestAnalizer.java:340&\#41;

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet&\#40;RequestAnalizer.java:318&\#41;

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer&\#40;RequestAnalizer.java:821&\#41;

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle&\#40;RequestAnalizer.java:239&\#41;

at com.sap.engine.services.httpserver.server.Client.handle&\#40;Client.java:92&\#41;

at com.sap.engine.services.httpserver.server.Processor.request&\#40;Processor.java:147&\#41;

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process&\#40;ApplicationSessionMessageListener.java:37&\#41;

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run&\#40;UnorderedChannel.java:71&\#41;

at com.sap.engine.core.thread.impl3.ActionObject.run&\#40;ActionObject.java:37&\#41;

at java.security.AccessController.doPrivileged&\#40;Native Method&\#41;

at com.sap.engine.core.thread.impl3.SingleThread.execute&\#40;SingleThread.java:94&\#41;

at com.sap.engine.core.thread.impl3.SingleThread.run&\#40;SingleThread.java:162&\#41;

Caused by: com.sap.dictionary.runtime.DdException:

at com.sap.dictionary.runtime.XmlExtractor.map&\#40;XmlExtractor.java:132&\#41;

at com.sap.dictionary.runtime.DdJavaProvider.getDataType&\#40;DdJavaProvider.java:68&\#41;

at com.sap.dictionary.runtime.DdNameTranslator.&\#60;init&\#62;&\#40;DdNameTranslator.java:53&\#41;

at com.sap.dictionary.runtime.DdNameTranslator.&\#60;init&\#62;&\#40;DdNameTranslator.java:28&\#41;

at com.sap.dictionary.runtime.DdBroker.getDataType&\#40;DdBroker.java:162&\#41;

at com.sap.dictionary.runtime.DdBroker.getStructure&\#40;DdBroker.java:180&\#41;

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure&\#40;DataTypeBroker.java:295&\#41;

... 44 more

</pre>)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.

at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:204)

at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:188)

at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:692)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:838)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:768)

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

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)

Thanks

Praveen

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Praveen,

Try the following in exact sequence.

1) Reimport the Model. Do a Reload+Rebuild.

2) Check that the local dictionary has the type

com.test.model.types.AdRFCModel:com.test.model.types.Ztmi_Tdat

3) Deploy your application again.

4) Restart your WAS.

5) Run the application.

It should run fine.

Regards,

Shubham

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

I have got the solution for this. I have tried recreating(JCO Connections), restarting(SLD Data Supplier, etc.), undeploying(Projects), rebuilding(Projects) and deploying to get rid of this exception. But it did not make any difference.

The main concern with this exception is while re-importing the model where the Netweaver Developer Studio works in a very strange way. It actually shows that it has reimported the model without showing any Deltas(shown in the info window in the last stage while importing the model). While this same application is testing on different machine with same version of NWDS where it actually shows the changed structures in the Deltas info.

So, clean the workspace(back up the projects) including the .METADATA folder(which is very very important) and restart the Netweaver Developer Studio which reinstalls itself and creates new version of .METADATA folder.

Now

1) Reimport the projects into the workspace

2) Reimport the model into the project

3) Restart the J2EE Server (Better undeploying the project using Remote SDM GUI before restarting the J2EE Server)

4) After the server is restarted, then rebuild and redeploy the application. Believe me it works.

Regards

Praveen Tipirneni

Former Member
0 Kudos

Hi Guys,

Thanks for the replies.. But Ive already tried both the ways, unfortunately it wont work.. I believe it is throwing this WebIOException in the last of the stack trace when running through some GZip** compression operation. Is this is a dispatcher problem? Please help me regarding this issue..

Praveen

Former Member
0 Kudos

Hi,

Just check the jco's.if jco's are correct go to sld administraton. stop and start the bridge.after that go to r/3 and execute transaction 'RZ70'for exporting meta data of r/3.if possible restart the WAS.

Regards,

Abhishek.