Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via MuleSoft JIRA by Jeroen Verellen, 1 year ago
ThreadPoolExecutor did not accept within 500 MILLISECONDS
via MuleSoft JIRA by Jeroen Verellen, 1 year ago
ThreadPoolExecutor did not accept within 500 MILLISECONDS
java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor did not accept within 500 MILLISECONDS	at org.mule.util.concurrent.WaitPolicy.rejectedExecution(WaitPolicy.java:62)	at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)	at org.mule.work.ScheduleWorkExecutor.doExecute(ScheduleWorkExecutor.java:41)	at org.mule.work.MuleWorkManager.executeWork(MuleWorkManager.java:250)	at org.mule.work.MuleWorkManager.scheduleWork(MuleWorkManager.java:218)	at org.mule.processor.SedaStageInterceptingMessageProcessor.run(SedaStageInterceptingMessageProcessor.java:233)	at org.mule.work.WorkerContext.run(WorkerContext.java:310)	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)	at java.lang.Thread.run(Thread.java:662)