Hello,
We got a seriious problem. After adding custom service AND rebooting jira mail service stopped working. We need to flush Mail queue manually. Logs are clear: no errors, no warnings, no debug messages.
Two interesting watchings: after server rebooting everything works normally. Then after JIRA restart everything crashes again.
When stopping service we got such error:
2013-05-15 07:39:13,152 WorkerThread-LastJob ERROR ServiceRunner [org.quartz.core.JobRunShell] Job DEFAULT.ServicesJob threw an unhandled Exception: java.lang.NullPointerException at com.atlassian.jira.ComponentManager.getComponent(ComponentManager.java:538) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:36) at org.quartz.core.JobRunShell.run(JobRunShell.java:195) at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) 2013-05-15 07:39:13,152 WorkerThread-LastJob ERROR ServiceRunner [org.quartz.core.ErrorLogger] Job (DEFAULT.ServicesJob threw an exception. org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.lang.NullPointerException] at org.quartz.core.JobRunShell.run(JobRunShell.java:206) at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) • Nested Exception (Underlying Cause) --------------- java.lang.NullPointerException at com.atlassian.jira.ComponentManager.getComponent(ComponentManager.java:538) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:36) at org.quartz.core.JobRunShell.run(JobRunShell.java:195) at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Thank you in advance.
Ragards, Andrey
All services were not working because one of them had endless method.
For our JIRA 2 threads are aviable. So, when service with endless method launched it took one of threads. Other services worked in another free thread. Then after time interval service launched again and we had two copies of the same endless service launched. And other services were waiting for their turn to run, because number of maximum threads is set to 2.
Hey there again, Andrey.
Good to know that the issue is fixed on your side and thank you for sharing the root cause to the problem as well. I believe that this will be very handy for other users that hit into the same problem as well.
Warm regards,
Danial
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hope so, I extended my answer a little. Thank you for following and replying.
Regards, Andrey.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey there, Andrey.
Can you try to increase your JIRA memory and restart your instance again to see if the same problem occurs? Normally, it is related to that.
If the same problem continues to occur, perhaps you might want to create a support ticket to get this looked at quicker. Hope this helps.
Warm regards,
Danial
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your reply, Danial.
Looks like there're other reasons. Our Jira use 422, picked up 494 MB and JVM memmory is set to 2GB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.