Errors under high payload

[d3bt3ch]

I am enqueuing a lot of jobs sometimes upto 10000. I am having two issues primarily ....

1. Sometimes all the jobs does not get completed.

2. The app hangs sometimes.

3. E/AndroidRuntime: FATAL EXCEPTION: job-manager Process: com.pixo.android, PID: 16419 android.database.sqlite.SQLiteCantOpenDatabaseException: unable to open database file (code 14)

4. E/JOBS: error while executing job com.domain.android.jobs.TestSyncJob@16df5239 java.net.SocketException: socket failed: EMFILE (Too many open files) at libcore.io.IoBridge.socket(IoBridge.java:623)

[gotama]

Hi,

Im getting the code 14 issue as well under high stress. the Job Queue just cant handle big loads.

I am running compile 'com.birbit:android-priority-jobqueue:2.0.1'

Also i can reproduce this issue very easily by recursively adding jobs to the queue, if I add a delay to the jobs starting it prolongs the crash but eventually the crash still happens.

This issue is related

Im currently investigating how to reduce the load on the job queue, but I mean its not giving me much confidence in the library when you get locked out of sql because you adding to many jobs to the queue.

Below is my exception :

Fatal Exception: android.database.sqlite.SQLiteCantOpenDatabaseException: unable to open database file (code 14) at android.database.sqlite.SQLiteConnection.nativeExecuteForCursorWindow(SQLiteConnection.java) at android.database.sqlite.SQLiteConnection.executeForCursorWindow(SQLiteConnection.java:845) at android.database.sqlite.SQLiteSession.executeForCursorWindow(SQLiteSession.java:836) at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:62) at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:144) at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:133) at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:197) at android.database.AbstractCursor.moveToNext(AbstractCursor.java:245) at com.birbit.android.jobqueue.persistentQueue.sqlite.SqliteJobQueue.nextJobAndIncRunCount(SqliteJobQueue.java:297) at com.birbit.android.jobqueue.cachedQueue.CachedJobQueue.nextJobAndIncRunCount(CachedJobQueue.java:79) at com.birbit.android.jobqueue.JobManagerThread.getNextJob(JobManagerThread.java:665) at com.birbit.android.jobqueue.JobManagerThread.getNextJob(JobManagerThread.java:642) at com.birbit.android.jobqueue.ConsumerManager.handleIdle(ConsumerManager.java:199) at com.birbit.android.jobqueue.JobManagerThread$1.handleMessage(JobManagerThread.java:231) at com.birbit.android.jobqueue.messaging.PriorityMessageQueue.consume(PriorityMessageQueue.java:39) at com.birbit.android.jobqueue.JobManagerThread.run(JobManagerThread.java:222) at java.lang.Thread.run(Thread.java:841)

Has there been any feedback on this issue?

[shawnlinboy]

I've got this same issue while running MONKEY test on my app, this may also be described as under high payload like your title given above, and here is my issue: https://github.com/yigit/android-priority-jobqueue/issues/407