Unexpected error in onHandleIntent java.util.concurrent.RejectedExecutionException [138238197]

Fixed

Bug

Status Update

No update yet.

Description

ro...@gmail.com

created issue #1

Jul 24, 2019 09:16AM

Component used:OneTimeWorkRequest
Version used:2.1.0
Devices/Android versions reproduced on:MINIX/Android 5.1.1

If this is a bug in the library, we would appreciate if you could attach:
07-23 15:02:22.508 1042-1127/E/WM-SystemAlarmDispatche: Unexpected error in onHandleIntent
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@2713e108 rejected from java.util.concurrent.ScheduledThreadPoolExecutor@63770a1[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
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.Executors$DelegatedScheduledExecutorService.schedule(Executors.java:644)
at androidx.work.impl.background.systemalarm.WorkTimer.startTimer(WorkTimer.java:82)
at androidx.work.impl.background.systemalarm.DelayMetCommandHandler.onAllConstraintsMet(DelayMetCommandHandler.java:135)
at androidx.work.impl.background.systemalarm.DelayMetCommandHandler.handleProcessWork(DelayMetCommandHandler.java:211)
at androidx.work.impl.background.systemalarm.CommandHandler.handleDelayMet(CommandHandler.java:272)
at androidx.work.impl.background.systemalarm.CommandHandler.onHandleIntent(CommandHandler.java:171)
at androidx.work.impl.background.systemalarm.SystemAlarmDispatcher$1.run(SystemAlarmDispatcher.java:272)
at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:75)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
07-23 15:02:22.963 1042-1055/com.yantranet.signware.agent.staging A/PowerManager: WakeLock finalized while still held: WorkManager: 72a8dc67-9b97-430d-9fc9-876f7e7c836c (2)

I need to run work request on-demand for a list of workers. The on-demand request can come in multiple times. So I basically loop the requests and create OneTimeWorkRequest for each Worker. I end up with the Exectuor RejectionException as above.

Comments

ra...@google.com <ra...@google.com> #2Jul 24, 2019 04:56PM

Issue is reproducible. More details are here :

https://drive.google.com/corp/drive/folders/1VwmAs_ixSYXoxYzcfwoHqyJ2f9w4DzZq (internal only link).

ap...@google.com <ap...@google.com> #3Jul 24, 2019 08:37PM

I think that ResultReceiver will "forever" stay in the old package since otherwise it would be a breaking AIDL-related change.

ra...@google.com <ra...@google.com> #4Jul 24, 2019 08:41PM

Assigned to ra...@google.com.

Yep, it has to stay in the old package.

> Jetifier is changing the import in the library to "androidx.core.os.ResultReceiver"

Config issue.

ap...@google.com <ap...@google.com> #5Jul 24, 2019 11:14PM

Marked as fixed.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 2bf39653103b1ce6b3b6fc64b44faaa9fcad1c19
Author: Filip Pavlis <pavlis@google.com>
Date: Tue Feb 12 19:41:53 2019

Revert changes in default.config and remove task.

It turned out that we have released (as part of beta03) mappings that
were not supposed to be used externally. This is because we were actively
maintaining "dejetifyArchive" task without realizing that next jetifier
update will contain such changes. As we are done with 28.0.0 I think it
is a good time to sunset the "dejetifyArchive" target. I also reverted
all the config changes that are not supposed to go outside. Please note
that there is still "partiallyDejetifyArchive" for migration purpouses
and is still part of continuous build.

Also added ignore rule for ResultReceiver.

Bug:

b/123651524

Bug:

b/124291947

Test: N/A
Change-Id: I59983d25ae7e0939f2e9e54005460ad0f73beb3c

M buildSrc/jetify.gradle
M buildSrc/src/main/kotlin/androidx/build/AndroidXPlugin.kt
M buildSrc/src/main/kotlin/androidx/build/LibraryVersions.kt
M jetifier/jetifier/core/src/main/resources/default.config
M jetifier/jetifier/core/src/main/resources/default.generated.config

https://android-review.googlesource.com/902433

https://goto.google.com/android-sha1/2bf39653103b1ce6b3b6fc64b44faaa9fcad1c19

ro...@gmail.com <ro...@gmail.com> #6Jul 25, 2019 06:31AM

FYI, in AGP 3.4.0-rc03 and 3.5.0-alpha09, the AGP has been updated to use Jetifier 1.0.0-beta04, which should have the fix for the above issue:

https://android.googlesource.com/platform/tools/base/+/f7fdfbb94aebb43b7e9515c683fd71b8c905ee79.

an...@google.com <an...@google.com> #7Jul 26, 2019 11:32PM

Closing as fixed.

ro...@gmail.com <ro...@gmail.com> #8Aug 14, 2019 06:39AM

Hi,

I used 2.2.0-RC1 and the issue still persists but not as frequent as before.

08-14 11:38:59.141 975-987/ A/PowerManager: WakeLock finalized while still held: WorkManager: bd0a17b6-e87a-4c44-bb7f-6ae195975b36 (2)
08-14 11:39:02.588 975-1102/com.yantranet.signware.agent.staging E/WM-SystemAlarmDispatche: Unexpected error in onHandleIntent
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3b835a4f rejected from java.util.concurrent.ScheduledThreadPoolExecutor@48bb5dc[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
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.Executors$DelegatedScheduledExecutorService.schedule(Executors.java:644)
at androidx.work.impl.background.systemalarm.WorkTimer.startTimer(WorkTimer.java:82)
at androidx.work.impl.background.systemalarm.DelayMetCommandHandler.onAllConstraintsMet(DelayMetCommandHandler.java:135)
at androidx.work.impl.background.systemalarm.DelayMetCommandHandler.handleProcessWork(DelayMetCommandHandler.java:211)
at androidx.work.impl.background.systemalarm.CommandHandler.handleDelayMet(CommandHandler.java:272)
at androidx.work.impl.background.systemalarm.CommandHandler.onHandleIntent(CommandHandler.java:171)
at androidx.work.impl.background.systemalarm.SystemAlarmDispatcher$1.run(SystemAlarmDispatcher.java:276)
at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
08-14 11:39:44.850 975-987/ A/PowerManager: WakeLock finalized while still held: WorkManager: 348bf17e-7aa4-48df-b88e-a2e7e3b5483d (2)

su...@google.com <su...@google.com> #9Aug 14, 2019 05:30PM

Can you please give us a sample app that reproduces this problem?

ra...@google.com <ra...@google.com> #10Aug 14, 2019 05:43PM

Also, are you sure the app in question was using the recent version of WM ?