Solution needed VERY URGENTLY - DELIVER IN 30 minutes

[Former Member]

All experts

Please help. We have copied a running web dynpro project A by another name B and changed the look and feel and other minor changes to the view. The RFCs used in both are same.

When we deploy the 2 projects on WAS one by one, they both get deployed.

But when one project is deployed and we try to run second project or vice versa then we get the following stack trace.

PLEASE HELP. NO IDEA WHAT THE PROBLEM IS AND WE NEED TO PUT THIS TO PRODUCTION

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to get deployable object part info for component com.sap.mtes.res_task_alloc.MTES_Resource_Task_Alloc

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getComponentDeploymentDescription(ClientComponent.java:682)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.<init>(ClientComponent.java:707)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.<init>(ClientApplication.java:292)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.createApplication(ClientApplication.java:279)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.createApplication(WebDynproMainTask.java:738)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:598)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)

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.doGet(DispatcherServlet.java:48)

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.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:95)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)

[Former Member · Accepted solution]

Please post the complete stack trace (including nested exception).

Armin

[Former Member · Accepted solution]

Please let us know what do you mean by nested exception. Anyways posting the log as we see in error window.

Client

Web Dynpro Client Type HTML Client

User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)

Version

DOM version

Client Type msie6

Client Type Profile ie6

ActiveX enabled

Cookies enabled

Frames enabled

Java Applets enabled

JavaScript enabled

Tables enabled

VB Script enabled

Server

Web Dynpro Runtime Vendor: SAP, Build ID: 6.4014.00.0000.20050905165427.0000 (release=630_VAL_REL, buildtime=2005-09-20:20:24:49[UTC], changelist=366934, host=PWDFM026)

J2EE Engine 6.40 patchlevel 98256.313

Java VM Java HotSpot(TM) Server VM, version:1.4.2_07-b05, vendor: Sun Microsystems Inc.

Operating system Windows 2003, version: 5.2, architecture: x86

Other

Session Locale en_US

Time of Failure Tue Jan 24 12:18:26 EST 2006 (Java Time: 1138123106845)

Web Dynpro Code Generation Infos

local/Mtes_Task_allocation

SapDictionaryGenerationCore 6.4014.00.0000.20050818151336.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:08:16[UTC], changelist=363802, host=PWDFM026.wdf.sap.corp)

SapDictionaryGenerationTemplates (unknown)

SapGenerationFrameworkCore 6.4014.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:01:32[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)

SapIdeWebDynproCheckLayer 6.4014.00.0000.20050818152737.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:15:40[UTC], changelist=363825, host=PWDFM026.wdf.sap.corp)

SapMetamodelCommon 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:02:26[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)

SapMetamodelCore 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:02:18[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)

SapMetamodelDictionary 6.4014.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:05:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)

SapMetamodelWebDynpro 6.4014.00.0000.20050818152356.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:11:31[UTC], changelist=363818, host=PWDFM026.wdf.sap.corp)

SapWebDynproGenerationCTemplates 6.4014.00.0000.20050905165427.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:26:46[UTC], changelist=366934, host=PWDFM026)

SapWebDynproGenerationCore 6.4014.00.0000.20050818152737.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:16:08[UTC], changelist=363825, host=PWDFM026.wdf.sap.corp)

SapWebDynproGenerationTemplates 6.4014.00.0000.20050905165427.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:26:46[UTC], changelist=366934, host=PWDFM026)

sap.com/tc_wddispwda

No information available

sap.com/tc_wdcorecomp

No information available

Detailed Error Information

Detailed Exception Chain

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to get deployable object part info for component com.sap.mtes.res_task_alloc.MTES_Resource_Task_Alloc

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getComponentDeploymentDescription(ClientComponent.java:682)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.<init>(ClientComponent.java:707)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.<init>(ClientApplication.java:292)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.createApplication(ClientApplication.java:279)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.createApplication(WebDynproMainTask.java:738)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:598)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)

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.doGet(DispatcherServlet.java:48)

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.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:95)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)

[Former Member · Accepted solution]

Check if deployment went throug without errors and that you call the application using the correct URL.

You can use the Web Dynpro content administrator application to check the status of your application on the server.

Also look into the logfiles if there are additional exceptions.

Armin

(10 minutes left

[Former Member · Accepted solution]

The URLs generated when we deploy the 2 applications one by one are below

http://epdf:50000/webdynpro/dispatcher/local/MTES/MTES_Resource_Task_Alloc?SAPtestId=19

http://epdf:50000/webdynpro/dispatcher/local/MTES_Resource_Task_Allocate/MTES_Resource_Task_Alloc?SA...

The second application we tried to run from NWDS instead of "Deploy New Archive and Run" failed in the errors listed above. Same error occurs vice versa.

We work from offshore so dont have rights to see WD Content Administrator.

PLEASE HELP.

[Former Member · Accepted solution]

If you completely rebuild the application in NWDS, do you get any errors in the "Tasks" view?

Armin

[Former Member · Accepted solution]

We dont get errors in both the projects when we Rebuild.

If first is deployed and run, and second is just run, then first one runs fine but second one gives errors listed above.

Please let me know what more information you need.

[Former Member · Accepted solution]

Thanks for your suggestion. We checked the status of our application in Content Administrator and also checked the application properties for both the applications.

What had happened was our applications had different project names but same package, application name and component name.

Hence when one as running the other used to fail to load, and vice versa.

We changed one of the names (package name) and played around to confirm. When the names were not same both ran perfectly.

Thanks for your suggestion. One request can you explain the logic behind what happened above.

Also, will you help me in solving another of my problems in performance. The client is beating us a lot on it and I want to give them the best solution.

I will post a proper query but I dont know how to assign it to you

All points awarded for your timely help and apologies for closing this out late (was not in office yesterday)