Null pointer exception when starting application

[Former Member]

Hi:

I had a application running fine, then i had to change some parameters in my RFC. I reimported the model, removed all the excess mapping, rebuild, deployed , restarted the server.

Then when i run the application, i get the below error.

Anyone has any idea?

java.lang.NullPointerException

at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.initReferenceAttribute(AttributeInfo.java:503)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initStructureType(NodeInfo.java:808)

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

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

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

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

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.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)

at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:374)

at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:403)

at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.initAttributeMapping(AttributeInfo.java:596)

at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:456)

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

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

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.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)

at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:374)

at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:403)

at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)

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

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

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.progmodel.view.ViewManager.getView(ViewManager.java:540)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)

at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)

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

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)

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

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:252)

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:392)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)

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

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

[Former Member]

Hi:

Solved this problem. OSS suggested I take a look at my reference table. I found that one of the reference field was removed. R/3 does not give an error but j2ee gives an error because it cannot find the reference field.

Subramania.

[Former Member]

As you can see from the error, there is no reference to which view or controller the error is orginating.

So i put in debug in my init function of main view and controller, but the system does not even reach this point.

So I think this error occurs even before my application gets triggered.

[Former Member]

Hi Subramania,

You said:

<i>"I had a application running fine, then i had to change some parameters in my RFC. I reimported the model, removed all the excess mapping, rebuild, deployed , restarted the server."</i>

You have removed all mappings between controller and view.

But, have you removed bindings between context attributes and view elements?

I guess problem is in binding between context and ui elements only.

Check it out and let me know.

Regards,

Bhavik

[Former Member]

Hi Subramania,

Have you resolved this issue?

If yes then please close this thread.

Regards,

Bhavik

[guru_subramanianb]

Hi,

Just a suggestion.Try to print the value of the variable using Message manager class before dispalying and see there by you can make sure what value passes from the RFC.

Rdgs,

Guru

[Former Member]

Hi Subramania

It looks like an attribute has lost reference to its parent node. Is there any nodes dangling in some view or controller from your old mapping which you forgot to delete??

Regards

Pran