Faulty report generation
Hi,
I have a problem when generating reports - I get a status 500 and the following is generated within the tomcat log file. This is quite the problem (not least due to the lack of reports) as this is seemingly causing the Jazz server to hang (on a daily basis), the second log snippet event was not instigated by any user or process but results in a hang nevertheless. 13:42:03,959 ERROR com.ibm.team.reports - An exception occurred while executing the task 'ReportServiceTask', contributed by component 'com.ibm.team.reports'. The task will be removed from the schedule. java.lang.NullPointerException at com.ibm.team.reports.service.internal.ReportServiceTask.runTask(ReportServiceTask.java:35) at com.ibm.team.repository.service.async.AbstractAutoScheduledTask.executeTask(AbstractAutoScheduledTask.java:116) at com.ibm.team.repository.service.internal.scheduler.InstrumentedAsynchronousTask.executeTask(InstrumentedAsynchronousTask.java:63) at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:147) at java.lang.Thread.run(Thread.java:801) 14-Feb-2008 06:51:20 org.apache.coyote.http11.Http11BaseProtocol pause INFO: Pausing Coyote HTTP/1.1 on http-9091 14-Feb-2008 06:51:21 org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina 14-Feb-2008 06:51:21 org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 29 instance(s) to be deallocated 14-Feb-2008 06:51:22 org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 29 instance(s) to be deallocated 14-Feb-2008 06:51:23 org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 29 instance(s) to be deallocated 14-Feb-2008 06:51:26 org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-9091 14-Feb-2008 06:51:26 org.apache.catalina.core.AprLifecycleListener lifecycleEvent INFO: Failed shutdown of Apache Portable Runtime -- Richard Davies |
One answer
Hi Richard,
It looks like there may be two issues here: 1. NPE in the ReportServiceTask. To track this down, I've opened a work item in the Reports component - let's continue this discussion there. Could you please append to this work item information about what version of the Jazz server you are running, and whether this is a fresh installation or a migration from some previous version? Also, does the directory /tmp/reports exist on your server, and what are the permissions for it? Here's the work item, which I have subscribed you to: https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=44191 2. The hanging of the server - it seems strange that the server would hang given that the task failed with an NPE. This may indicate a repository issue in the async task mechanism, but we'll have to dig a bit deeper to find out. You should be able to ask the VM to issue a thread dump which should indicate the problematic thread(s) by hitting Ctrl+\ (on unix) or Ctrl+Break (on windows) in the console where the server was launched from, when the server is in this state. Also, you indicate a 500 problem while *generating* reports, but the task in the stack trace below shouldn't occur when generating reports, but rather when an asynchronous job runs once a day. Are there any other stack traces in your log that look interesting? Does the timestamp (13:42:03) match the time when you requested the report? Thanks, james richard.daviesr wrote: Hi, |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.