1 of 1 people found this helpful
It might have something to do with the actual war still being present after restart (in addition to the deployment the AS has stashed away, based on that deployment)
Thanks for your fast respone!
Could you test it fllowing my steps?
I'm not *that* interested ;-) I'll take your word for it, especially since it behaves pretty much as expected and you haven't given any more usecase than a curiosity.
Thanks, I think I will fix it. I think this issue will modify the deployment-scanner subsystem.