on 08-01-2006 2:08 PM
Hello,
could someone please take a look at the following error, which I get, if I try to export the performance history (tsv files) in the NWA in the section Monitoring.
I click on "Export History" and than the Application asks "It may take a long time to export the history. Do you want to continue?". I confirm with yes and get the following error.
Is that a programming error or an configuration error?
Thanks in advance for your help!
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
java.lang.NullPointerException
at com.sap.engine.admin.model.performance.tsvexport.SerializableMonitorNode.setHistory(SerializableMonitorNode.java:99)
at com.sap.engine.admin.model.performance.tsvexport.MonitoringSerializer.setPerfData(MonitoringSerializer.java:73)
at com.sap.engine.admin.model.performance.tsvexport.TsvExport.monitors(TsvExport.java:291)
at com.sap.engine.admin.model.performance.tsvexport.TsvExport.export(TsvExport.java:101)
at com.sap.engine.admin.model.performance.impl.TsvFileExportImpl.generateFile(TsvFileExportImpl.java:40)
... 53 more
Complete Error Message:
java.lang.reflect.UndeclaredThrowableException
at com.sap.engine.admin.model.performance._gen.TsvFileExport$Impl.generateFile(TsvFileExport.java:100)
at com.sap.webadmin.performance.viewer.comp.MainView.onTheActionApproved(MainView.java:1356)
at com.sap.webadmin.performance.viewer.comp.wdp.InternalMainView.wdInvokeEventHandler(InternalMainView.java:984)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:271)
at com.sap.webadmin.performance.viewer.comp.wdp.InternalMessageController.wdFireEventActionApproved(InternalMessageController.java:160)
at com.sap.webadmin.performance.viewer.comp.MessageController.fireActionApproved(MessageController.java:137)
at com.sap.webadmin.performance.viewer.comp.wdp.InternalMessageController.fireActionApproved(InternalMessageController.java:141)
at com.sap.webadmin.performance.viewer.comp.MessageView.onActionYes(MessageView.java:177)
at com.sap.webadmin.performance.viewer.comp.wdp.InternalMessageView.wdInvokeEventHandler(InternalMessageView.java:170)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649)
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.doPost(DispatcherServlet.java:55)
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: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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: javax.management.MBeanException
at com.sap.engine.admin.model.performance.impl.TsvFileExportImpl.generateFile(TsvFileExportImpl.java:44)
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.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at javax.management.StandardMBean.invoke(StandardMBean.java:286)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:253)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.lm.webadmin.connection.jmx.MBeanServerConnectionWrapper.invoke(MBeanServerConnectionWrapper.java:470)
at com.sap.engine.admin.model.performance._gen.TsvFileExport$Impl.generateFile(TsvFileExport.java:96)
... 35 more
Caused by: java.lang.NullPointerException
at com.sap.engine.admin.model.performance.tsvexport.SerializableMonitorNode.setHistory(SerializableMonitorNode.java:99)
at com.sap.engine.admin.model.performance.tsvexport.MonitoringSerializer.setPerfData(MonitoringSerializer.java:73)
at com.sap.engine.admin.model.performance.tsvexport.TsvExport.monitors(TsvExport.java:291)
at com.sap.engine.admin.model.performance.tsvexport.TsvExport.export(TsvExport.java:101)
at com.sap.engine.admin.model.performance.impl.TsvFileExportImpl.generateFile(TsvFileExportImpl.java:40)
... 53 more
Hi,
I am facing the same problem on EP 6.0 SP 15. Did u get any solution for this?
Regards,
Sreeram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.