I am getting internal server error

[Former Member]

Hi Experts,

I am getting one internal server error.

let me explain what i did. in one table i added 6 fields(in which projenddate is one of the new field) and again reimported the model. after that i am getting this error. I also mapped the new table fieds to the controller and also to the corresponding view.

plz help me in solving this.

will i have to restart J2EE?

plz give me possible solution ASAP as it is needed urgently.

I am showing the exception that i got after running the application.

the initial exception that caused the equest to fail is,

com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException:DataNodeInfo(MTES_Project_Maintainance.Z_MTES_Project_Maintain_Input.prjOutPut.T_PrjMaster): strucure field projenddate not found.

at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:295)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:669)

at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)

at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:347)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)

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

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)

[HuseyinBilgen]

Hi,

Yes, at the moment J2EE server needs restart to update the model cache.

We hope SAP will produce a solution for tihs kind of restart needs.

[Former Member]

Hi,

Did the restart fix the problem?

for me the problem exists even after restart.

Thanks in advance!

[Former Member]

Hello,

As far as I've understood it, the J2EE server only needs to be restarted after you add an attribute to an already existing structure. If you remove an attribute it should not be necessary.

It's a big annoyance, I hope SAP will solve it sooner than later.

Regards Mattias