java.util.concurrent.RejectedExecutionException

Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@1ae1a3fd rejected from java.util.concurrent.ScheduledThreadPoolExecutor@30db9854[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 32]

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web549

  • via GitHub by sgc-code
    ,
  • Stack trace

    • java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@1ae1a3fd rejected from java.util.concurrent.ScheduledThreadPoolExecutor@30db9854[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 32] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2011) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:793) at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:298) at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:503) at java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:602) at rx.internal.schedulers.NewThreadWorker.scheduleActual(SourceFile:244) at rx.internal.schedulers.NewThreadWorker.schedule(SourceFile:228) at rx.internal.schedulers.NewThreadWorker.schedule(SourceFile:220) at rx.internal.operators.OperatorObserveOn$ObserveOnSubscriber.schedule(SourceFile:190) at rx.internal.operators.OperatorObserveOn$ObserveOnSubscriber.onNext(SourceFile:165) at rx.internal.operators.NotificationLite.accept(SourceFile:152) at rx.internal.operators.OperatorOnBackpressureBuffer$BufferSubscriber.accept(SourceFile:157) at rx.internal.util.BackpressureDrainManager.drain(SourceFile:200) at rx.internal.operators.OperatorOnBackpressureBuffer$BufferSubscriber.onNext(SourceFile:152) at com.mycompany.myclass.send(SourceFile:666)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown visitor
    Unknown visitorOnce,
    batwalrus76batwalrus76
    4 times, last one
    davidvanlaatumdavidvanlaatum
    6 times, last one
    guizmaiiguizmaii
    Once,
    Unknown visitor
    Unknown visitorOnce,
    93 more bugmates