intersect scans may fail to act on stop signal

Please se MB-30930 for 5.5.2
Intersect scans (ordered or not) only set their state to stopped if it is received from the getItem side.
If the stop signal is received from the sendItem side, this not stopped is not set, and upon exiting the intersect scan will try to process the queue all the same.
If there are more items to be processed than what the channel allows, this will lead to a go routine hang and a memory leak.