如果您对Oraclejob实现自动化任务和oraclejob不自动执行感兴趣，那么这篇文章一定是您不可错过的。我们将详细讲解Oraclejob实现自动化任务的各种细节，并对oraclejob不自动执行
如果您对Oracle job 实现自动化任务和oracle job不自动执行感兴趣，那么这篇文章一定是您不可错过的。我们将详细讲解Oracle job 实现自动化任务的各种细节，并对oracle job不自动执行进行深入的分析，此外还有关于Android Priority Job Queue (Job Manager)（一）、Android Priority Job Queue (Job Manager)：后台线程任务结果传回前台（三）、Android Priority Job Queue (Job Manager)：多重不同Job并发执行并在前台获得返回结果（四）、Android Priority Job Queue (Job Manager)：线程任务的容错重启机制（二）的实用技巧。
本文目录一览：- Oracle job 实现自动化任务（oracle job不自动执行）
- Android Priority Job Queue (Job Manager)（一）
- Android Priority Job Queue (Job Manager)：后台线程任务结果传回前台（三）
- Android Priority Job Queue (Job Manager)：多重不同Job并发执行并在前台获得返回结果（四）
- Android Priority Job Queue (Job Manager)：线程任务的容错重启机制（二）
Oracle job 实现自动化任务（oracle job不自动执行）
在实际开发的过程中我们可以通过 spring 配置或者 oracle job 来实现一些自动化任务的执行，前者不再多说，主要总结一下 oracle job 实现的自动化任务。
1. 创建测试表 test
CREATE TABLE "TEST"."TEST"
( "UPDATE_TIME" DATE)
2. 创建测试存储过程 insertTestData
create or replace procedure insertTestData
is
begin
insert into test(update_time) values (sysdate);
end;
3. 创建 job 每分钟运行一次
declare
testJob number;
begin
dbms_job.submit(testJob, ''insertTestData;'', sysdate, ''sysdate+1/(24*60)'');
end;
4. 查看 job 信息
select job,log_user,to_char(last_date,''yyyy-mm-dd hh24:mi:ss'') last_date,to_char
(next_date,''yyyy-mm-dd hh24:mi:ss'') next_date,interval,what from user_jobs
注意：LAST_DATE 内容是空，表示此 JOB 没有被执行过，因此这个 JOB 将永远不会被自动的执行。
5. 如果 LAST_DATE 内容是空，可能存在以下问题，并且进行解决
5.1 show parameter job_queue_processes 首先查看 job_queue_processes 这个参数，如果这个参数为 0，说明所有 JOb 都不能运行。
5.2 alter system set job_queue_processes =10 scope=spfile; 修改参数后，重启数据库。
6. 运行，停止，删除，修改 job
begin
dbms_job.run (v_job); -- 运行 job
dbms_job.broken (v_job,true,next_date); -- 停止一个 job, 里面参数 true 也可是 false，next_date（某一时刻停止）也可是 sysdate（立刻停止）。
dbms_job.remove (v_job); -- 删除某个 job
dbms_job.what (v_job,''sp_fact_charge_code;''); -- 修改某个 job 名
dbms_job.next_date (v_job,sysdate); -- 修改下一次运行时间
end;
7.job 运行时间设置
''TRUNC (SYSDATE+1)+(5*60+30)/(24*60) ''-- 每天上午 5 点半触发一次
''SYSDATE + 1'' -- 每天运行一次
''SYSDATE + 1/24'' -- 每小时运行一次
''SYSDATE + 10/（60*24）'' -- 每十分钟运行一次
''SYSDATE + 30/(60*24*60)'' -- 每 30 秒运行一次
''TRUNC (LAST_DAY (ADD_MONTHS (SYSDATE,1))) + 23/24'' -- 每个月最后一天运行一次
''NEXT_DAY (TRUNC (SYSDATE), ''''TUESDAY'''' ) + 12/24'' -- 每星期二中午 12 点
''TRUNC (LEAST (NEXT_DAY (SYSDATE, ''''SATURDAY"), NEXT_DAY (SYSDATE,"SUNDAY"))) + (6*60+10)/(24*60)'' -- 每星期六和日早上 6 点 10 分
数据库定时任务 每天的 6:00,12:00,18:00，24:00 这四个时间点执行
VARIABLE jobno number;
begin
DBMS_JOB.SUBMIT(:jobno,
'' 你定时执行的存储过程；'',
TO_DATE(
TO_CHAR(SYSDATE,''YYYYMMDD'')||
LPAD(TRUNC(TO_NUMBER(TO_CHAR(SYSDATE,''HH24''))/6)*6,2,''0'')
,''YYYYMMDDHH24''),
''TO_DATE(
TO_CHAR(SYSDATE,''''YYYYMMDD'''')||
LPAD(TRUNC(TO_NUMBER(TO_CHAR(SYSDATE,''''HH24''''))/6)*6,2,''''0'''')
,''''YYYYMMDDHH24'''')+0.25'');
commit;
end;
Android Priority Job Queue (Job Manager)（一）
Android Priority Job Queue (Job Manager)（一）
一、为什么要引入Android Priority Job Queue (Job Manager)？
如今的APP开发中，几乎绝大多数APP没有不需要后台线程操作和运行的任务，Android平台自身提供了一些后台线程的编程实现模型和API。比如常见的主流后台+线程处理方式：
A、 AsyncTask，
B、 Loaders，
C、 以及更复杂的Service组合线程池（Thread Pool），
D、Java的Thread结合Handler。
等等。
但是以上方式的问题很多，尤其是在耦合到Android本身的Activity或Fragment生命周期时候，要处理各种实际的场景，还有就是当在线程操作中如果处理失败，又该怎么办？有些情况，比如当用户在WIFI或者2G/3G/4G不同网络时候的不同网络加载策略。假设用户在发送一条消息到服务器，但是在线程发送过程中网络中断，在一定时延后网络又接通，此时线程又该如何决定发送任务的再次处理？如果使用Java Thread，Android本身又不允许在主线程外更新UI。如果使用Service，那么还要解决Service和，等等等诸如此类问题全部丢到线程中处理，将会额外但又不得不处理多种状态情况。
所以，为解决上述问题，就需要引入一种相对完善、可以解决后台+线程的简单易用的线程任务调度管理框架，为此引入Android Priority Job Queue (Job Manager)。
Android Priority Job Queue (Job Manager)是github上的一个Android开源项目，项目主页是：https://github.com/yigit/android-priority-jobqueue
Android Priority Job Queue (Job Manager)在其项目主页有完整的项目研究背景和作用，简单概括起来就是简化了Android涉及到的后台线程编程开发工作，使得开发者从后台线程繁琐的开发和代码维护中解脱出来，专注于业务逻辑。
二、Android Priority Job Queue (Job Manager)使用简介。
(1) Android Priority Job Queue (Job Manager)首先需要初始化和配置，在初始化和配置阶段，Android Priority Job Queue (Job Manager)类似Java线程池，写一个MyApplication继承自
Android Application，在此完成初始化。MyApplication.java：
package zhangphil.app;
import android.app.Application;
import android.util.Log;
import com.birbit.android.jobqueue.JobManager;
import com.birbit.android.jobqueue.config.Configuration;
import com.birbit.android.jobqueue.log.CustomLogger;
/**
* Created by Phil on 2016/10/9.
*/
public class MyApplication extends Application {
private JobManager jobManager;
private static MyApplication instance;
public MyApplication() {
instance = this;
}
public static MyApplication getInstance() {
return instance;
}
@Override
public void onCreate() {
super.onCreate();
getJobManager();// ensure it is created
}
public synchronized JobManager getJobManager() {
if (jobManager == null) {
configureJobManager();
}
return jobManager;
}
private void configureJobManager() {
Configuration.Builder builder = new Configuration.Builder(this)
.customLogger(new CustomLogger() {
private static final String TAG = "zhangphil job";
@Override
public boolean isDebugEnabled() {
return true;
}
@Override
public void d(String text, Object... args) {
Log.d(TAG, String.format(text, args));
}
@Override
public void e(Throwable t, String text, Object... args) {
Log.e(TAG, String.format(text, args), t);
}
@Override
public void e(String text, Object... args) {
Log.e(TAG, String.format(text, args));
}
@Override
public void v(String text, Object... args) {
}
})
.minConsumerCount(1)//always keep at least one consumer alive
.maxConsumerCount(3)//up to 3 consumers at a time
.loadFactor(3)//3 jobs per consumer
.consumerKeepAlive(120);//wait 2 minute
jobManager = new JobManager(builder.build());
}
}实际上在自己的项目中，Android Priority Job Queue (Job Manager)的初始化工作基本上不用做修改大体按照上面的写就好了，调整的地方在于任务数量这些有关系统性能开销的地方控制。
写完了记得要在Androidmainfest.xml写到application下面：
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="zhangphil.app">
<application
android:name=".MyApplication"
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:supportsRtl="true"
android:theme="@style/AppTheme">
<activity android:name=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
（2）写一个请求的任务逻辑，这是Android Priority Job Queue (Job Manager)使用的关键地方。首先需要继承自Android Priority Job Queue (Job Manager)得Job类，我写了一个测试的MyJob类，在此类中用于完成后台+线程的任务操作，Android Priority Job Queue (Job Manager)的Job有些类似于Java的Runnable，可以比照Java的Runnable理解Android Priority Job Queue (Job Manager)的Job。耗时线程任务在onRun里面做，MyJob.java：
package zhangphil.app;
import android.os.SystemClock;
import android.support.annotation.NonNull;
import android.support.annotation.Nullable;
import android.util.Log;
import com.birbit.android.jobqueue.Job;
import com.birbit.android.jobqueue.Params;
import com.birbit.android.jobqueue.RetryConstraint;
/**
* Created by Phil on 2016/10/9.
*/
public class MyJob extends Job {
private String tag;
public MyJob(String tag) {
super(new Params(500).requireNetwork().persist().groupBy(tag));
this.tag = tag;
Log.d(tag, "初始化");
}
@Override
public void onAdded() {
Log.d(tag, "添加任务");
}
//在这里面放置耗时的后台线程化任务
@Override
public void onRun() throws Throwable {
Log.d(tag, "开始运行...");
int i = 0;
while (true) {
i++;
SystemClock.sleep(2000);
Log.d(tag, String.valueOf(i));
if (i == 10)
break;
}
Log.d(tag, "完成");
}
@Override
protected RetryConstraint shouldReRunOnThrowable(@NonNull Throwable throwable, int runCount, int maxRunCount) {
// An error occurred in onRun.
// Return value determines whether this job should retry or cancel. You can further
// specify a backoff strategy or change the job''s priority. You can also apply the
// delay to the whole group to preserve jobs'' running order.
Log.d(tag, "runCount：" + runCount);
return RetryConstraint.createExponentialBackoff(runCount, 1000);
}
@Override
protected void onCancel(int cancelReason, @Nullable Throwable throwable) {
}
}（3）测试的MainActivity.java：
package zhangphil.app;
import android.app.Activity;
import android.os.Bundle;
import com.birbit.android.jobqueue.JobManager;
public class MainActivity extends Activity {
private JobManager jobManager;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
//setContentView(R.layout.activity_main);
jobManager=MyApplication.getInstance().getJobManager();
jobManager.addJobInBackground(new MyJob("任务1")); //启动任务，跑！
//jobManager.addJobInBackground(new MyJob("任务2"));
//jobManager.addJobInBackground(new MyJob("任务3"));
//jobManager.addJobInBackground(new MyJob("任务4"));
//jobManager.addJobInBackground(new MyJob("任务5"));
//jobManager.addJobInBackground(new MyJob("任务6"));
}
}
附录我写的Android线程相关文章：
【1】《Java线程池：ExecutorService，Executors》链接地址：http://blog.csdn.net/zhangphil/article/details/43898637
【2】《Java线程池及Future、Callable获得线程返回结果【Java线程池系列2】》链接地址：http://blog.csdn.net/zhangphil/article/details/49701219
【3】《Java线程池之FutureTask【Java线程池系列3】》链接地址：http://blog.csdn.net/zhangphil/article/details/49702751
Android Priority Job Queue (Job Manager)：后台线程任务结果传回前台（三）
Android Priority Job Queue (Job Manager)：后台线程任务结果传回前台（三）
在附录文章4,5的基础上改造MainActivity.java和MyJob.java，改造后的代码，将使MyJob在后台完成线程任务后返回数据给前台。
实现的技术路线：
（1） 首先需要在MyJob里面定义一个结果值，假设这个值就是打算盛放后台线程计算结果的容器bean等等，然后当线程在后台计算完成后赋值。同时写一个public公共的get方法，这个get操作暴露给其他代码使用。
package zhangphil.app;
import android.os.SystemClock;
import android.support.annotation.NonNull;
import android.support.annotation.Nullable;
import android.util.Log;
import com.birbit.android.jobqueue.Job;
import com.birbit.android.jobqueue.Params;
import com.birbit.android.jobqueue.RetryConstraint;
/**
* Created by Phil on 2016/10/10.
*/
public class MyJob extends Job{
private String tag;
//此处的结果将传回给发起线程的上层代码
//比如经过一个耗时的长期后台线程完成后，一个结果获得，然后传回给需求方
private String result;
public MyJob(String tag) {
super(new Params(500).requireNetwork().persist().groupBy(tag));
this.tag = tag;
Log.d(tag, "初始化");
}
public String getResult(){
return result;
}
@Override
public void onAdded() {
Log.d(tag, "添加任务");
}
//在这里面放置耗时的后台线程化任务
@Override
public void onRun() throws Throwable {
Log.d(tag, "开始运行...");
SystemClock.sleep(10000);
//此处抛出异常后，jobqueue将立即自动进入shouldReRunOnThrowable
//throw new Exception();
result="任务完成！";
Log.d(tag,"完成");
}
@Override
protected RetryConstraint shouldReRunOnThrowable(@NonNull Throwable throwable, int runCount, int maxRunCount) {
// An error occurred in onRun.
// Return value determines whether this job should retry or cancel. You can further
// specify a backoff strategy or change the job''s priority. You can also apply the
// delay to the whole group to preserve jobs'' running order.
Log.d(tag, "runCount: " + runCount + " maxRunCount: " + maxRunCount);
//这样的返回将导致onRun方法的再次执行，重启线程,重启将导致代码再次进入onRun。同时，runCount自加1
return RetryConstraint.RETRY;
}
//如果重试超过限定次数，将onCancel.
//如果用户主动放弃删掉这个任务，也一样进入onCancel
@Override
protected void onCancel(int cancelReason, @Nullable Throwable throwable) {
Log.d(tag, "放弃：" + cancelReason);
}
@Override
protected int getRetryLimit() {
//仅仅重启5次次，超过5次则放弃任务。
return 5;
}
}
（2） JobManager添加后台线程任务时候，重写回调方法，在回调里面等待结果。
package zhangphil.app;
import android.support.annotation.NonNull;
import android.support.annotation.Nullable;
import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;
import android.util.Log;
import com.birbit.android.jobqueue.Job;
import com.birbit.android.jobqueue.JobManager;
import com.birbit.android.jobqueue.callback.JobManagerCallback;
public class MainActivity extends AppCompatActivity {
private JobManager jobManager;
private String tag=this.getClass().getName();
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
//setContentView(R.layout.activity_main);
jobManager=MyApplication.getInstance().getJobManager();
MyJob job=new MyJob("任务1");
jobManager.addJobInBackground(job);
jobManager.addCallback(new JobManagerCallback() {
@Override
public void onJobAdded(@NonNull Job job) {
}
@Override
public void onJobRun(@NonNull Job job, int resultCode) {
}
@Override
public void onJobCancelled(@NonNull Job job, boolean byCancelRequest, @Nullable Throwable throwable) {
}
@Override
public void onDone(@NonNull Job job) {
MyJob myJob= (MyJob) job;
Log.d(tag,job.getId()+" onDone : "+myJob.getResult());
}
@Override
public void onAfterJobRun(@NonNull Job job, int resultCode) {
}
});
}
}代码运行结果：
附录：
【1】《Java线程池：ExecutorService，Executors》链接地址：http://blog.csdn.net/zhangphil/article/details/43898637
【2】《Java线程池及Future、Callable获得线程返回结果【Java线程池系列2】》链接地址：http://blog.csdn.net/zhangphil/article/details/49701219
【3】《Java线程池之FutureTask【Java线程池系列3】》链接地址：http://blog.csdn.net/zhangphil/article/details/49702751
【4】《Android Priority Job Queue (Job Manager)（一）》链接地址：http://blog.csdn.net/zhangphil/article/details/52777196
【5】《Android Priority Job Queue (Job Manager)：线程任务的容错重启机制（二）》链接地址：http://blog.csdn.net/zhangphil/article/details/52778525
Android Priority Job Queue (Job Manager)：多重不同Job并发执行并在前台获得返回结果（四）
Android Priority Job Queue (Job Manager)：多重不同Job并发执行并在前台获得返回结果（四）
在Android Priority Job Queue (Job Manager)中，如果两个或者若干多个完全不同的Job子任务并发执行，如何在前台获得返回结果呢？现在给出一个例子说明。
假设有两个完全不同的子任务JobA和JobB。当JobA任务完成后返回一个结果给前台回调，同样当任务JobB任务完成后返回一个结果给前台回调使用。
写两个Job：JobA和JobB。
JobA.java：
package zhangphil.app;
import android.os.SystemClock;
import android.support.annotation.NonNull;
import android.support.annotation.Nullable;
import android.util.Log;
import com.birbit.android.jobqueue.Job;
import com.birbit.android.jobqueue.Params;
import com.birbit.android.jobqueue.RetryConstraint;
/**
* Created by Phil on 2016/11/2.
*/
public class JobA extends Job {
private String tag;
private String result;
public String getResult() {
return result;
}
public JobA(String tag) {
super(new Params(500).requireNetwork().persist().groupBy(tag));
this.tag = tag;
Log.d(tag, "构造");
}
@Override
public void onAdded() {
Log.d(tag, "onAdded");
}
@Override
public void onRun() throws Throwable {
Log.d(tag, "开始运行...");
SystemClock.sleep(3000);
result = tag + "的结果:" + System.currentTimeMillis();
Log.d(tag, "完成:" + result);
}
@Override
protected void onCancel(int cancelReason, @Nullable Throwable throwable) {
}
@Override
protected RetryConstraint shouldReRunOnThrowable(@NonNull Throwable throwable, int runCount, int maxRunCount) {
return null;
}
}
JobB.java：
package zhangphil.app;
import android.os.SystemClock;
import android.support.annotation.NonNull;
import android.support.annotation.Nullable;
import android.util.Log;
import com.birbit.android.jobqueue.Job;
import com.birbit.android.jobqueue.Params;
import com.birbit.android.jobqueue.RetryConstraint;
/**
* Created by Phil on 2016/11/2.
*/
public class JobB extends Job {
private String tag;
private String result;
public String getResult() {
return result;
}
public JobB(String tag) {
super(new Params(500).requireNetwork().persist().groupBy(tag));
this.tag = tag;
Log.d(tag, "构造");
}
@Override
public void onAdded() {
Log.d(tag, "onAdded");
}
@Override
public void onRun() throws Throwable {
Log.d(tag, "开始运行...");
SystemClock.sleep(3000);
result = tag + "的结果:" + System.currentTimeMillis();
Log.d(tag, "完成:" + result);
}
@Override
protected void onCancel(int cancelReason, @Nullable Throwable throwable) {
}
@Override
protected RetryConstraint shouldReRunOnThrowable(@NonNull Throwable throwable, int runCount, int maxRunCount) {
return null;
}
}
前台回调获得结果：
package zhangphil.app;
import android.support.annotation.NonNull;
import android.support.annotation.Nullable;
import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;
import android.util.Log;
import com.birbit.android.jobqueue.Job;
import com.birbit.android.jobqueue.JobManager;
import com.birbit.android.jobqueue.callback.JobManagerCallback;
public class MainActivity extends AppCompatActivity {
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
//setContentView(R.layout.activity_main);
JobManager jobManager = MyApplication.getInstance().getJobManager();
JobA a = new JobA("任务->A");
JobA b = new JobA("任务->B");
jobManager.addJobInBackground(a);
jobManager.addJobInBackground(b);
jobManager.addCallback(new JobManagerCallback() {
@Override
public void onJobAdded(@NonNull Job job) {
}
@Override
public void onJobRun(@NonNull Job job, int resultCode) {
}
@Override
public void onJobCancelled(@NonNull Job job, boolean byCancelRequest, @Nullable Throwable throwable) {
}
@Override
public void onDone(@NonNull Job job) {
if (job instanceof JobA) {
JobA a = (JobA) job;
Log.d("返回", a.getResult());
}
if (job instanceof JobB) {
JobB b = (JobB) job;
Log.d("返回", b.getResult());
}
}
@Override
public void onAfterJobRun(@NonNull Job job, int resultCode) {
}
});
}
}需要注意须用instanceof判断回调的实例是具体哪一个。
代码运行结果如图（添加关键词‘任务’过滤）：
关于MyApplication的配置和写法和附录文章4,5,6相同。
附录：
【1】《Java线程池：ExecutorService，Executors》链接地址：http://blog.csdn.net/zhangphil/article/details/43898637
【2】《Java线程池及Future、Callable获得线程返回结果【Java线程池系列2】》链接地址：http://blog.csdn.net/zhangphil/article/details/49701219
【3】《Java线程池之FutureTask【Java线程池系列3】》链接地址：http://blog.csdn.net/zhangphil/article/details/49702751
【4】《Android Priority Job Queue (Job Manager)（一）》链接地址：http://blog.csdn.net/zhangphil/article/details/52777196
【5】《Android Priority Job Queue (Job Manager)：线程任务的容错重启机制（二）》链接地址：http://blog.csdn.net/zhangphil/article/details/52778525
【6】《 Android Priority Job Queue (Job Manager)：后台线程任务结果传回前台（三）》链接：http://blog.csdn.net/zhangphil/article/details/52787588
Android Priority Job Queue (Job Manager)：线程任务的容错重启机制（二）
Android Priority Job Queue (Job Manager)：线程任务的容错重启机制（二）
附录文章 4 简单介绍了如何启动一个后台线程任务，Android Priority Job Queue (Job Manager) 有一个重要的机制在附录文章 4 还没有体现：线程任务失败后重试、重启线程任务。这个机制在某些开发场景中非常常用，假设从网络中请求数据，但不幸的是网络出现故障，导致在线程体 onRun 内的代码失败，问题是失败该如何处理？这个时候，常规的做法是自己增加一堆状态字或者返回值加以控制，但是这样无疑使得开发者陷入繁琐的线程状态机的维护中来。
Android Priority Job Queue (Job Manager) 完整的解决上上述问题：容错重试回滚任务机制。具体体现在 onRun 和 shouldReRunOnThrowable，如果一个线程任务在 onRun 里面抛出异常失败，那么将自动进入 shouldReRunOnThrowable，然后在 shouldReRunOnThrowable 会决定是否重试 RetryConstraint.RETRY，或者干脆放弃任务 RetryConstraint.CANCEL，这里面的重试或者放弃逻辑策略由开发者决定，比如一般的，可以由重试次数决定线程是否还有必要执行，假设一个任务重试了 3 次仍然不成功，那么就放弃（返 RetryConstraint.CANCEL）。一旦放弃后，代码将进入 onCanel 内，在这里面处理善后事宜，这个机制有些类似 Java 的 try-catch 机制。
在附录文章 4 的基础上，仅仅修改 MyJob.java 代码演示上述机制：
package zhangphil.app;
import android.os.SystemClock;
import android.support.annotation.NonNull;
import android.support.annotation.Nullable;
import android.util.Log;
import com.birbit.android.jobqueue.Job;
import com.birbit.android.jobqueue.Params;
import com.birbit.android.jobqueue.RetryConstraint;
/**
* Created by Phil on 2016/10/9.
*/
public class MyJob extends Job {
private String tag;
public MyJob(String tag) {
super(new Params(500).requireNetwork().persist().groupBy(tag));
this.tag = tag;
Log.d(tag, "初始化");
}
@Override
public void onAdded() {
Log.d(tag, "添加任务");
}
//在这里面放置耗时的后台线程化任务
@Override
public void onRun() throws Throwable {
Log.d(tag, "开始运行...");
SystemClock.sleep(2000);
//此处抛出异常后，jobqueue将立即自动进入shouldReRunOnThrowable
throw new Exception();
//Log.d(tag, "完成");
}
@Override
protected RetryConstraint shouldReRunOnThrowable(@NonNull Throwable throwable, int runCount, int maxRunCount) {
// An error occurred in onRun.
// Return value determines whether this job should retry or cancel. You can further
// specify a backoff strategy or change the job''s priority. You can also apply the
// delay to the whole group to preserve jobs'' running order.
Log.d(tag, "runCount: " + runCount + " maxRunCount: " + maxRunCount);
//如果重试了3次仍未成功，那么就放弃执行任务
if (runCount == 3)
return RetryConstraint.CANCEL;
//这样的返回将导致onRun方法的再次执行，重试,重试将导致代码再次进入onRun。同时，runCount自加1
return RetryConstraint.RETRY;
}
//如果重试超过限定次数，将onCancel.
//如果用户主动放弃删掉这个任务，也一样进入onCancel
@Override
protected void onCancel(int cancelReason, @Nullable Throwable throwable) {
Log.d(tag, "cancelReason：" + cancelReason);
}
}
代码运行后 Logcat 完整输出：
10-10 15:51:39.488 16856-16856/zhangphil.app D/任务1: 初始化
10-10 15:51:39.488 16856-16856/zhangphil.app D/zhangphil job: [queue_ADD_JOB_2] post message com.birbit.android.jobqueue.messaging.message.AddJobMessage@b1a3ff0
10-10 15:51:39.488 16856-16856/zhangphil.app D/Activity: performCreate Call Injection manager
10-10 15:51:39.488 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085899495109636
10-10 15:51:39.488 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085899495109636
10-10 15:51:39.488 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:39.488 16856-17353/zhangphil.app D/zhangphil job: [queue_ADD_JOB_2] remove message com.birbit.android.jobqueue.messaging.message.AddJobMessage@b1a3ff0
10-10 15:51:39.488 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] consuming message of type ADD_JOB
10-10 15:51:39.488 16856-16856/zhangphil.app I/InjectionManager: dispatchOnViewCreated > Target : zhangphil.app.MainActivity isFragment :false
10-10 15:51:39.528 16856-17353/zhangphil.app D/zhangphil job: added job class: MyJob priority: 500 delay: 0 group : 任务1 persistent: true
10-10 15:51:39.528 16856-17353/zhangphil.app D/任务1: 添加任务
10-10 15:51:39.528 16856-17353/zhangphil.app D/zhangphil job: considering adding a new consumer. Should poke all waiting? false isRunning? true waiting workers? 0
10-10 15:51:39.528 16856-17353/zhangphil.app D/zhangphil job: check above load factor: totalCons:0 minCons:1 maxConsCount: 3, loadFactor 3 remainingJobs: 1 running holders: 0. isAbove:true
10-10 15:51:39.528 16856-17353/zhangphil.app D/zhangphil job: nothing has been poked. are we above load factor? true
10-10 15:51:39.528 16856-17353/zhangphil.app D/zhangphil job: adding another consumer
10-10 15:51:39.538 16856-16856/zhangphil.app D/SecWifiDisplayUtil: Metadata value : SecSettings2
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085899551798802
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085899551798802
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:39.548 16856-16856/zhangphil.app D/ViewRootImpl: #1 mView = com.android.internal.policy.PhoneWindow$DecorView{8602777 I.E...... R.....ID 0,0-0,0}
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [queue_ADD_JOB_2] remove message null
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: joq idle. running:? true
10-10 15:51:39.548 16856-17358/zhangphil.app D/zhangphil job: flushing messages at time 1476085899553556250
10-10 15:51:39.548 16856-17358/zhangphil.app D/zhangphil job: [consumer_3] remove message null
10-10 15:51:39.548 16856-17358/zhangphil.app D/zhangphil job: consumer manager on idle
10-10 15:51:39.548 16856-17358/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] post message com.birbit.android.jobqueue.messaging.message.JobConsumerIdleMessage@a013fe4
10-10 15:51:39.548 16856-17358/zhangphil.app D/zhangphil job: [consumer_3] will wait on the lock forever
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: Job queue idle. next job at: -9223372036854775808
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: add delayed message com.birbit.android.jobqueue.messaging.message.ConstraintChangeMessage@257dc4d at time -9223372036854775808
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] did on idle post a message? true
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085899555766615
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085899555766615
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [queue_CONSTRAINT_CHANGE_5] post message com.birbit.android.jobqueue.messaging.message.ConstraintChangeMessage@257dc4d
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [queue_CONSTRAINT_CHANGE_5] remove message com.birbit.android.jobqueue.messaging.message.ConstraintChangeMessage@257dc4d
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] consuming message of type CONSTRAINT_CHANGE
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: considering adding a new consumer. Should poke all waiting? true isRunning? true waiting workers? 0
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: check above load factor: totalCons:1 minCons:1 maxConsCount: 3, loadFactor 3 remainingJobs: 1 running holders: 0. isAbove:false
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: nothing has been poked. are we above load factor? false
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085899559063386
10-10 15:51:39.548 16856-17359/zhangphil.app D/OpenGLRenderer: Use EGL_SWAP_BEHAVIOR_PRESERVED: true
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085899559063386
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [queue_CONSTRAINT_CHANGE_5] remove message null
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [queue_ADD_JOB_2] remove message null
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] remove message com.birbit.android.jobqueue.messaging.message.JobConsumerIdleMessage@a013fe4
10-10 15:51:39.548 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] consuming message of type JOB_CONSUMER_IDLE
10-10 15:51:39.558 16856-16856/zhangphil.app W/ActivityThread: AppLock checkAppLockState isAppLocked = false pkgName = zhangphil.app showWhenLocked = false
10-10 15:51:39.568 16856-17353/zhangphil.app D/zhangphil job: [consumer_3] post message com.birbit.android.jobqueue.messaging.message.RunJobMessage@725c413
10-10 15:51:39.568 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085899571643802
10-10 15:51:39.568 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085899571643802
10-10 15:51:39.568 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:39.568 16856-17353/zhangphil.app D/zhangphil job: [queue_CONSTRAINT_CHANGE_5] remove message null
10-10 15:51:39.568 16856-17353/zhangphil.app D/zhangphil job: [queue_ADD_JOB_2] remove message null
10-10 15:51:39.568 16856-17353/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] remove message null
10-10 15:51:39.568 16856-17353/zhangphil.app D/zhangphil job: joq idle. running:? true
10-10 15:51:39.568 16856-17358/zhangphil.app D/zhangphil job: flushing messages at time 1476085899571733438
10-10 15:51:39.568 16856-17358/zhangphil.app D/zhangphil job: [consumer_3] remove message com.birbit.android.jobqueue.messaging.message.RunJobMessage@725c413
10-10 15:51:39.568 16856-17358/zhangphil.app D/zhangphil job: running job JobHolder
10-10 15:51:39.568 16856-17358/zhangphil.app D/zhangphil job: running job MyJob
10-10 15:51:39.568 16856-17358/zhangphil.app D/任务1: 开始运行...
10-10 15:51:39.568 16856-17353/zhangphil.app D/zhangphil job: Job queue idle. next job at: null
10-10 15:51:39.568 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] did on idle post a message? false
10-10 15:51:39.588 16856-17359/zhangphil.app I/Adreno: QUALCOMM build : 0039a8c, I5bc0f577f9
Build Date : 08/03/16
OpenGL ES Shader Compiler Version: XE031.08.00.02
Local Branch :
Remote Branch : refs/tags/AU_LINUX_ANDROID_LA.HB.1.1.1.C1.06.00.00.165.223
Remote Branch : NONE
Reconstruct Branch : NOTHING
10-10 15:51:39.588 16856-17359/zhangphil.app D/libEGL: eglInitialize EGLDisplay = 0x7f93bfa188
10-10 15:51:39.588 16856-17359/zhangphil.app I/OpenGLRenderer: Initialized EGL, version 1.4
10-10 15:51:39.618 16856-16856/zhangphil.app D/ViewRootImpl: MSG_RESIZED_REPORT: ci=Rect(0, 96 - 0, 0) vi=Rect(0, 96 - 0, 0) or=1
10-10 15:51:39.628 16856-16856/zhangphil.app W/DisplayListCanvas: DisplayListCanvas is started on unbinded RenderNode (without mOwningView)
10-10 15:51:39.668 16856-16856/zhangphil.app I/Timeline: Timeline: Activity_idle id: android.os.BinderProxy@87b6b1c time:249284264
10-10 15:51:41.568 16856-17358/zhangphil.app E/zhangphil job: error while executing job zhangphil.app.MyJob@9eb605a
java.lang.Exception
at zhangphil.app.MyJob.onRun(MyJob.java:38)
at com.birbit.android.jobqueue.Job.safeRun(Job.java:229)
at com.birbit.android.jobqueue.JobHolder.safeRun(JobHolder.java:132)
at com.birbit.android.jobqueue.ConsumerManager$Consumer.handleRunJob(ConsumerManager.java:398)
at com.birbit.android.jobqueue.ConsumerManager$Consumer.access$000(ConsumerManager.java:317)
at com.birbit.android.jobqueue.ConsumerManager$Consumer$2.handleMessage(ConsumerManager.java:345)
at com.birbit.android.jobqueue.messaging.SafeMessageQueue.consume(SafeMessageQueue.java:36)
at com.birbit.android.jobqueue.ConsumerManager$Consumer.run(ConsumerManager.java:380)
at java.lang.Thread.run(Thread.java:818)
10-10 15:51:41.568 16856-17358/zhangphil.app D/任务1: runCount: 1 maxRunCount: 20
10-10 15:51:41.568 16856-17358/zhangphil.app D/zhangphil job: safeRunResult for zhangphil.app.MyJob@9eb605a : false. re run:true. cancelled: false
10-10 15:51:41.578 16856-17358/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] post message com.birbit.android.jobqueue.messaging.message.RunJobResultMessage@2fa28b
10-10 15:51:41.578 16856-17358/zhangphil.app D/zhangphil job: flushing messages at time 1476085901581361354
10-10 15:51:41.578 16856-17358/zhangphil.app D/zhangphil job: [consumer_3] remove message null
10-10 15:51:41.578 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085901581436927
10-10 15:51:41.578 16856-17358/zhangphil.app D/zhangphil job: consumer manager on idle
10-10 15:51:41.578 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085901581436927
10-10 15:51:41.578 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:41.578 16856-17353/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] remove message com.birbit.android.jobqueue.messaging.message.RunJobResultMessage@2fa28b
10-10 15:51:41.578 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] consuming message of type RUN_JOB_RESULT
10-10 15:51:41.578 16856-17358/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] post message com.birbit.android.jobqueue.messaging.message.JobConsumerIdleMessage@a013fe4
10-10 15:51:41.578 16856-17358/zhangphil.app D/zhangphil job: [consumer_3] will wait on the lock forever
10-10 15:51:41.598 16856-17353/zhangphil.app D/zhangphil job: reinsert job result true
10-10 15:51:41.598 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085901603381718
10-10 15:51:41.598 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085901603381718
10-10 15:51:41.598 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:41.598 16856-17353/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] remove message null
10-10 15:51:41.598 16856-17353/zhangphil.app D/zhangphil job: [queue_CONSTRAINT_CHANGE_5] remove message null
10-10 15:51:41.598 16856-17353/zhangphil.app D/zhangphil job: [queue_ADD_JOB_2] remove message null
10-10 15:51:41.598 16856-17353/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] remove message com.birbit.android.jobqueue.messaging.message.JobConsumerIdleMessage@a013fe4
10-10 15:51:41.598 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] consuming message of type JOB_CONSUMER_IDLE
10-10 15:51:41.608 16856-17353/zhangphil.app D/zhangphil job: [consumer_3] post message com.birbit.android.jobqueue.messaging.message.RunJobMessage@725c413
10-10 15:51:41.608 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085901615635572
10-10 15:51:41.608 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085901615635572
10-10 15:51:41.608 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:41.608 16856-17353/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] remove message null
10-10 15:51:41.608 16856-17353/zhangphil.app D/zhangphil job: [queue_CONSTRAINT_CHANGE_5] remove message null
10-10 15:51:41.608 16856-17353/zhangphil.app D/zhangphil job: [queue_ADD_JOB_2] remove message null
10-10 15:51:41.608 16856-17358/zhangphil.app D/zhangphil job: flushing messages at time 1476085901615705104
10-10 15:51:41.608 16856-17353/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] remove message null
10-10 15:51:41.608 16856-17353/zhangphil.app D/zhangphil job: joq idle. running:? true
10-10 15:51:41.608 16856-17358/zhangphil.app D/zhangphil job: [consumer_3] remove message com.birbit.android.jobqueue.messaging.message.RunJobMessage@725c413
10-10 15:51:41.608 16856-17358/zhangphil.app D/zhangphil job: running job JobHolder
10-10 15:51:41.608 16856-17358/zhangphil.app D/zhangphil job: running job MyJob
10-10 15:51:41.608 16856-17358/zhangphil.app D/任务1: 开始运行...
10-10 15:51:41.608 16856-17353/zhangphil.app D/zhangphil job: Job queue idle. next job at: null
10-10 15:51:41.618 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] did on idle post a message? false
10-10 15:51:43.608 16856-17358/zhangphil.app E/zhangphil job: error while executing job zhangphil.app.MyJob@1ef2826
java.lang.Exception
at zhangphil.app.MyJob.onRun(MyJob.java:38)
at com.birbit.android.jobqueue.Job.safeRun(Job.java:229)
at com.birbit.android.jobqueue.JobHolder.safeRun(JobHolder.java:132)
at com.birbit.android.jobqueue.ConsumerManager$Consumer.handleRunJob(ConsumerManager.java:398)
at com.birbit.android.jobqueue.ConsumerManager$Consumer.access$000(ConsumerManager.java:317)
at com.birbit.android.jobqueue.ConsumerManager$Consumer$2.handleMessage(ConsumerManager.java:345)
at com.birbit.android.jobqueue.messaging.SafeMessageQueue.consume(SafeMessageQueue.java:36)
at com.birbit.android.jobqueue.ConsumerManager$Consumer.run(ConsumerManager.java:380)
at java.lang.Thread.run(Thread.java:818)
10-10 15:51:43.608 16856-17358/zhangphil.app D/任务1: runCount: 2 maxRunCount: 20
10-10 15:51:43.608 16856-17358/zhangphil.app D/zhangphil job: safeRunResult for zhangphil.app.MyJob@1ef2826 : false. re run:true. cancelled: false
10-10 15:51:43.608 16856-17358/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] post message com.birbit.android.jobqueue.messaging.message.RunJobResultMessage@2fa28b
10-10 15:51:43.608 16856-17358/zhangphil.app D/zhangphil job: flushing messages at time 1476085903619928280
10-10 15:51:43.608 16856-17358/zhangphil.app D/zhangphil job: [consumer_3] remove message null
10-10 15:51:43.608 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085903620000572
10-10 15:51:43.608 16856-17358/zhangphil.app D/zhangphil job: consumer manager on idle
10-10 15:51:43.608 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085903620000572
10-10 15:51:43.608 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:43.608 16856-17353/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] remove message com.birbit.android.jobqueue.messaging.message.RunJobResultMessage@2fa28b
10-10 15:51:43.618 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] consuming message of type RUN_JOB_RESULT
10-10 15:51:43.618 16856-17358/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] post message com.birbit.android.jobqueue.messaging.message.JobConsumerIdleMessage@a013fe4
10-10 15:51:43.618 16856-17358/zhangphil.app D/zhangphil job: [consumer_3] will wait on the lock forever
10-10 15:51:43.628 16856-17353/zhangphil.app D/zhangphil job: reinsert job result true
10-10 15:51:43.628 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085903636682603
10-10 15:51:43.628 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085903636682603
10-10 15:51:43.628 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:43.628 16856-17353/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] remove message null
10-10 15:51:43.628 16856-17353/zhangphil.app D/zhangphil job: [queue_CONSTRAINT_CHANGE_5] remove message null
10-10 15:51:43.628 16856-17353/zhangphil.app D/zhangphil job: [queue_ADD_JOB_2] remove message null
10-10 15:51:43.628 16856-17353/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] remove message com.birbit.android.jobqueue.messaging.message.JobConsumerIdleMessage@a013fe4
10-10 15:51:43.628 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] consuming message of type JOB_CONSUMER_IDLE
10-10 15:51:43.638 16856-17353/zhangphil.app D/zhangphil job: [consumer_3] post message com.birbit.android.jobqueue.messaging.message.RunJobMessage@725c413
10-10 15:51:43.638 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085903643573436
10-10 15:51:43.638 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085903643573436
10-10 15:51:43.638 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:43.638 16856-17353/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] remove message null
10-10 15:51:43.638 16856-17353/zhangphil.app D/zhangphil job: [queue_CONSTRAINT_CHANGE_5] remove message null
10-10 15:51:43.638 16856-17358/zhangphil.app D/zhangphil job: flushing messages at time 1476085903643628228
10-10 15:51:43.638 16856-17353/zhangphil.app D/zhangphil job: [queue_ADD_JOB_2] remove message null
10-10 15:51:43.638 16856-17353/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] remove message null
10-10 15:51:43.638 16856-17353/zhangphil.app D/zhangphil job: joq idle. running:? true
10-10 15:51:43.638 16856-17358/zhangphil.app D/zhangphil job: [consumer_3] remove message com.birbit.android.jobqueue.messaging.message.RunJobMessage@725c413
10-10 15:51:43.638 16856-17358/zhangphil.app D/zhangphil job: running job JobHolder
10-10 15:51:43.638 16856-17358/zhangphil.app D/zhangphil job: running job MyJob
10-10 15:51:43.638 16856-17358/zhangphil.app D/任务1: 开始运行...
10-10 15:51:43.638 16856-17353/zhangphil.app D/zhangphil job: Job queue idle. next job at: null
10-10 15:51:43.638 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] did on idle post a message? false
10-10 15:51:45.638 16856-17358/zhangphil.app E/zhangphil job: error while executing job zhangphil.app.MyJob@12572bd
java.lang.Exception
at zhangphil.app.MyJob.onRun(MyJob.java:38)
at com.birbit.android.jobqueue.Job.safeRun(Job.java:229)
at com.birbit.android.jobqueue.JobHolder.safeRun(JobHolder.java:132)
at com.birbit.android.jobqueue.ConsumerManager$Consumer.handleRunJob(ConsumerManager.java:398)
at com.birbit.android.jobqueue.ConsumerManager$Consumer.access$000(ConsumerManager.java:317)
at com.birbit.android.jobqueue.ConsumerManager$Consumer$2.handleMessage(ConsumerManager.java:345)
at com.birbit.android.jobqueue.messaging.SafeMessageQueue.consume(SafeMessageQueue.java:36)
at com.birbit.android.jobqueue.ConsumerManager$Consumer.run(ConsumerManager.java:380)
at java.lang.Thread.run(Thread.java:818)
10-10 15:51:45.638 16856-17358/zhangphil.app D/任务1: runCount: 3 maxRunCount: 20
10-10 15:51:45.638 16856-17358/zhangphil.app D/zhangphil job: safeRunResult for zhangphil.app.MyJob@12572bd : false. re run:false. cancelled: false
10-10 15:51:45.638 16856-17358/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] post message com.birbit.android.jobqueue.messaging.message.RunJobResultMessage@2fa28b
10-10 15:51:45.638 16856-17358/zhangphil.app D/zhangphil job: flushing messages at time 1476085905647085571
10-10 15:51:45.638 16856-17358/zhangphil.app D/zhangphil job: [consumer_3] remove message null
10-10 15:51:45.638 16856-17358/zhangphil.app D/zhangphil job: consumer manager on idle
10-10 15:51:45.638 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085905647246300
10-10 15:51:45.638 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085905647246300
10-10 15:51:45.638 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:45.638 16856-17353/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] remove message com.birbit.android.jobqueue.messaging.message.RunJobResultMessage@2fa28b
10-10 15:51:45.638 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] consuming message of type RUN_JOB_RESULT
10-10 15:51:45.638 16856-17353/zhangphil.app D/任务1: cancelReason：5
10-10 15:51:45.638 16856-17358/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] post message com.birbit.android.jobqueue.messaging.message.JobConsumerIdleMessage@a013fe4
10-10 15:51:45.638 16856-17358/zhangphil.app D/zhangphil job: [consumer_3] will wait on the lock forever
10-10 15:51:45.658 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085905666501300
10-10 15:51:45.658 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085905666501300
10-10 15:51:45.658 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:45.658 16856-17353/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] remove message null
10-10 15:51:45.658 16856-17353/zhangphil.app D/zhangphil job: [queue_CONSTRAINT_CHANGE_5] remove message null
10-10 15:51:45.658 16856-17353/zhangphil.app D/zhangphil job: [queue_ADD_JOB_2] remove message null
10-10 15:51:45.658 16856-17353/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] remove message com.birbit.android.jobqueue.messaging.message.JobConsumerIdleMessage@a013fe4
10-10 15:51:45.658 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] consuming message of type JOB_CONSUMER_IDLE
10-10 15:51:45.668 16856-17353/zhangphil.app D/zhangphil job: keep alive: 1476086025647041248
10-10 15:51:45.668 16856-17353/zhangphil.app D/zhangphil job: Consumer idle, will kill? false . isRunning: true
10-10 15:51:45.668 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] looking for next message at time 1476085905680193019
10-10 15:51:45.668 16856-17353/zhangphil.app D/zhangphil job: flushing messages at time 1476085905680193019
10-10 15:51:45.668 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] next delayed job null
10-10 15:51:45.668 16856-17353/zhangphil.app D/zhangphil job: [queue_RUN_JOB_RESULT_6] remove message null
10-10 15:51:45.678 16856-17353/zhangphil.app D/zhangphil job: [queue_CONSTRAINT_CHANGE_5] remove message null
10-10 15:51:45.678 16856-17353/zhangphil.app D/zhangphil job: [queue_ADD_JOB_2] remove message null
10-10 15:51:45.678 16856-17353/zhangphil.app D/zhangphil job: [queue_JOB_CONSUMER_IDLE_4] remove message null
10-10 15:51:45.678 16856-17353/zhangphil.app D/zhangphil job: joq idle. running:? true
10-10 15:51:45.678 16856-17353/zhangphil.app D/zhangphil job: Job queue idle. next job at: null
10-10 15:51:45.678 16856-17353/zhangphil.app D/zhangphil job: [priority_mq] did on idle post a message? false
上述完整 Logcat 输出显示了代码在 onRun 里面抛出异常然后容错回滚机制发挥作用重启了任务，过滤 “任务” 后精简的关键 Logcat 输出：
10-10 15:51:39.488 16856-16856/zhangphil.app D/任务1: 初始化
10-10 15:51:39.528 16856-17353/zhangphil.app D/zhangphil job: added job class: MyJob priority: 500 delay: 0 group : 任务1 persistent: true
10-10 15:51:39.528 16856-17353/zhangphil.app D/任务1: 添加任务
10-10 15:51:39.568 16856-17358/zhangphil.app D/任务1: 开始运行...
10-10 15:51:41.568 16856-17358/zhangphil.app D/任务1: runCount: 1 maxRunCount: 20
10-10 15:51:41.608 16856-17358/zhangphil.app D/任务1: 开始运行...
10-10 15:51:43.608 16856-17358/zhangphil.app D/任务1: runCount: 2 maxRunCount: 20
10-10 15:51:43.638 16856-17358/zhangphil.app D/任务1: 开始运行...
10-10 15:51:45.638 16856-17358/zhangphil.app D/任务1: runCount: 3 maxRunCount: 20
10-10 15:51:45.638 16856-17353/zhangphil.app D/任务1: cancelReason：5附录：
【1】《Java 线程池：ExecutorService，Executors》链接地址：http://blog.csdn.net/zhangphil/article/details/43898637
【2】《Java 线程池及 Future、Callable 获得线程返回结果【Java 线程池系列 2】》链接地址：http://blog.csdn.net/zhangphil/article/details/49701219
【3】《Java 线程池之 FutureTask【Java 线程池系列 3】》链接地址：http://blog.csdn.net/zhangphil/article/details/49702751
【4】《Android Priority Job Queue (Job Manager)（一）》链接地址：http://blog.csdn.net/zhangphil/article/details/52777196
关于Oracle job 实现自动化任务和oracle job不自动执行的问题就给大家分享到这里，感谢你花时间阅读本站内容，更多关于Android Priority Job Queue (Job Manager)（一）、Android Priority Job Queue (Job Manager)：后台线程任务结果传回前台（三）、Android Priority Job Queue (Job Manager)：多重不同Job并发执行并在前台获得返回结果（四）、Android Priority Job Queue (Job Manager)：线程任务的容错重启机制（二）等相关知识的信息别忘了在本站进行查找喔。
本文标签：
