I'm trying an experiment where an Activity makes a number of consecutive calls to an IntentService. Each call kicks off some background work that finishes in a few seconds. So there are multiple concurrent instances of the IntentService running. All the instances finish at around the same time and each one does a sendBroadcast to return a message to the Activity that it's finished. When this happens, about 30% of the broadcast intents never get back to the Activity's registered receiver.
It looks as if there is some static state inside the IntentService class that is in conflict when there are multiple invocations running and they are all calling sendBroadcast at about the same time. In other words, sendBroadcast appears to be non-re-entrant. I'd like to package up this example for submission to b.android.com but before I do, I'd like to find out a few things from this forum: 1) Is this a known bug? 2) Is this expected behavior (ie not a bug)? 3) Has anyone seen anything like this or another case where the IntentService worked correctly when used in this way? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
