We have found this exception a lot of times in our log. We are using Zephyr 184.108.40.2063 and JIRA v6.0.4 both with valid commercial licenses.
2013-08-01 15:50:37,163 ajp-bio-8081-exec-26 ERROR johndoe 950x1378x4 13g69w2 192.168.0.2 /rest/zephyr/latest/schedule [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service java.lang.NullPointerException at com.thed.zephyr.je.rest.ScheduleResource.getSchedulesByIssueId(ScheduleResource.java:212) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
What does this exception mean and how can stop it?
Thanks for your time and help.
Removed "It may also be related to serious slow downs of jira - which render jira almost unusable." because these issues are not related.
We released Zephyr for JIRA 2.0 a few days ago. The upgrade to this should solve that error you are seeing in the logs.
After you upgrade to Zephyr for JIRA 2.0 please IMMEDIATELY re index your JIRA then re index Zephyr in that order.
The reason you got this error is because when you re-indexed, the thread that waits for the re index currently times out after 60 seconds. Sometimes a re-index will take longer than 60 and if this is the case Zephyr for JIRA will throw that error. However, the re-index will still occur, just you will not know what time it will occurred.
We have changed the way this works in our Zephyr for JIRA 2.0. In Zephyr for JIRA 2.0 the timeout will not occur. Instead, it will just wait until the index is finished and let you know when it is done.
I get a lot of this errors after updating from JIRA 5.1.8 to JIRA 6.0.8, too. And I'm not able to succesfully make a Zephyr reindex. After starting the Zephyr reindex I get a red error message saying "Error occured during setting updates:" and no details on the error.
Was there a solution for the problem?
The exception that you are currently seeing is due to a change that was made in JIRA 6.0. The way we load our libraries and the way that JIRA handles it in 6.0 are a bit different. However, we have fixed this in Zephyr for JIRA 2.0.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot