Bugzilla – Bug 5345
resource not destroyed correctly when time expires and shutdown method is "trash"
Last modified: 2007-05-31 17:27:43
You need to log in before you can comment on or make changes to this bug.
When running time allotment is gone (not speaking of resource termination) and the client had requested a default shutdown method of trash (i.e., no unpropagate, no transport readying), the resource is being destroyed but not in such a way that a notification is generated to the client.
Fix committed to HEAD, will be part of the release after TP1.2.3