Community
Participate
Working Groups
See stack trace below: java.util.concurrent.RejectedExecutionException at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1768) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:92) at org.eclipse.mylyn.commons.net.WebUtil.execute(WebUtil.java:351) at org.eclipse.mylyn.commons.net.WebUtil.executeInternal(WebUtil.java:387) at org.eclipse.mylyn.commons.net.WebUtil.execute(WebUtil.java:341) at org.eclipse.mylyn.commons.net.WebUtil.execute(WebUtil.java:315) at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.postFormData(BugzillaClient.java:1012) at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.postTaskData(BugzillaClient.java:1191) at org.eclipse.mylyn.internal.bugzilla.core.BugzillaTaskDataHandler.postTaskData(BugzillaTaskDataHandler.java:385) at org.eclipse.mylyn.internal.tasks.core.sync.SubmitTaskJob.run(SubmitTaskJob.java:82) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
This is likely caused by a third party extension that is not properly releasing connections and hence exhausting the connection pool.