I've spent some time at this bug, running automated and random input tests to try reproduce it. I've found 1 probable cause for this issue: url-dispatcher starts apps if they're not running - and it appears to be possible that AppMan is told to respawn the same app around the same time - causing 2 instances of the same app to be executed - one of which AppMan will reject. I had this happen once anyway.
I suspect there's another issue causing this bug too (going by log file output anyway). Am still investigating.
So far, I've been unable to reproduce any user-facing fault related to this issue - AppMan is only rejecting a second instances of an app running.
I've spent some time at this bug, running automated and random input tests to try reproduce it. I've found 1 probable cause for this issue: url-dispatcher starts apps if they're not running - and it appears to be possible that AppMan is told to respawn the same app around the same time - causing 2 instances of the same app to be executed - one of which AppMan will reject. I had this happen once anyway.
I suspect there's another issue causing this bug too (going by log file output anyway). Am still investigating.
So far, I've been unable to reproduce any user-facing fault related to this issue - AppMan is only rejecting a second instances of an app running.