Home/ Questions/Q 619755
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T18:41:22+00:00

Here’s scenario: I have 2 activities and one service First activity is a landing

  • 0

Here’s scenario:

  1. I have 2 activities and one service
  2. First activity is a landing view/search page. Second activity displays search results
  3. Search is always executed against internal SQLite db
  4. Periodically (say daily) db needs to be updated from the remote source which is a long process
  5. If user performs the search during the update I want to wait until the update is over while displaying “Please wait” progress alert. I don’t want to query and display search results until refresh is fully done.
  6. The db update is triggered by AlarmManager and executed by service which puts “UPDATING” status into db while update is in progress
  7. I can easily query the status but how do I wait and periodically re-query the database? I’m using AsyncTask to process search results and my knee-jerk reaction was to put a loop with wait() into AsyncTask#doInBackground method but that’s dangerous and simply doesn’t work since I’m not controlling the UI thread so I end up with IllegalMonitorStateException.

What would be a “right” way to properly wait (may be even with status update) in this case?

P.S. I placed the “wait” code into a Runnable and executing it even before I get to my AsyncTask. It works e.g. Thread.sleep(2000) still I’m not sure that’s the way to do it safely. Does anyone have any experience with FutureTask?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If user performs the search during the
    update I want to wait until the update
    is over while displaying “Please wait”
    progress alert. I don’t want to query
    and display search results until
    refresh is fully done.

    That’s your call, but bear in mind you are creating your own problem. Personally, I’d dump this requirement. The user should not be inconvenienced just because an alarm went off.

    For example, you could disable the alarm and re-enable it when the activity goes away.

    Or, have the update be performed in such a way that it is atomic (e.g., do the update on a copy of the table, then sync the tables in a transaction), so that the activity can still safely access the database while the update is occurring.

    What would be a “right” way to
    properly wait (may be even with status
    update) in this case?

    Have the service tell the activity when the update is done, via some sort of callback, or perhaps a broadcast Intent. Keep the progress indicator alive until this occurs. This still introduces some timing challenges, which is why I’d just dump the requirement.

    • 0