Zephyr Nullpointerexception

[Dennis Fabri]

We have found this exception a lot of times in our log. We are using Zephyr 1.7.3.1043 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.

-- Edit

Removed "It may also be related to serious slow downs of jira - which render jira almost unusable." because these issues are not related.

[Emily Schneider · Accepted solution]

Hi Everyone,

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.

:::::IMPORTANT NOTE:::::

After you upgrade to Zephyr for JIRA 2.0 please IMMEDIATELY re index your JIRA then re index Zephyr in that order.

Kind Regards,

Emily

[Chris Miller]

Henning,

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.

Kind Regards,
Chris

[Henning Tietgens]

Hi Chris,

thanks, good news :-) Is there any information on the NPE itself?

Thanks,

Hening

[Dennis Fabri]

Zephyr has now (October 21) released a new version. We will check if this issue has been resolved.

[Emily Schneider]

Hi Dennis,

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.

Kind Regards,

Emily

[Team TI/BA]

Hi,

We have the same problem after updating to Jira 6.0.8. Any idea to solve the error?

Best regards,

Wilm

[Henning Tietgens]

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?

[Chris Miller]

Hi,

Zephyr is working directly with Dennis from our support ticketing system.

Kind Regards,

Chris

[Chris Miller]

Hi Dennis,

Can you please send the entire Atlassian-JIRA log over to Zephyr support please? We are at support at getzephyr dot com. We'd like to take a look at it.

Kind Regards,
Chris