cancel
Showing results for 
Search instead for 
Did you mean: 

java.lang.NullPointerException in Runtime Workbench

Former Member
0 Kudos

We get the error java.lang.NullPointerException in Runtime Workbench

After the upgrade from XI 3.0 to Pi 7.0

The error is triggered when you try to run Message Monitorring

As the part of the upgrade we moved software to the new box but we have adjusted the hostname in all known placess (e.g. Exchange profile)

Can somebody suggest how to approach such error.

Where can I find logs. I checked /cluster/server0/log but did not find anything

Mariusz

Accepted Solutions (0)

Answers (1)

Answers (1)

justin_santhanam
Active Contributor
0 Kudos

Hi,

/usr/sap/<SID>/DVEBMGS12/j2ee/cluster/server0/log/ there you can find defaultTrace.trc file, this contains all the logs.

Best regards,

raj.

Former Member
0 Kudos

I already checked this location. When I trigger this error again I do not see the timestap changing on any of the files:(

I explorer window I can see the following stack trace:

java.lang.NullPointerException

at com.sap.aii.mdt.web.MonitorDynPage.setNewComponent(MonitorDynPage.java:508)

at com.sap.aii.mdt.web.MonitorDynPage.process_go_button(MonitorDynPage.java:373)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)

at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)

at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)

at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)

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

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

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

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

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

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