stflow handling/behaviour in the http consumer processor is wrong

The stFlow behaviour is wrong in the consumer processor. I call it behaviour because it is actually not only used if st flow is selected but also if the repsonse thread is faster then the request thread could go into suspend. It that latter race condition occurs it wont never work correctly again without a redeploy. The isSTFlow Parameter cannot be a global attribute because that would lead to wrong behaviour for all parallel requests. What makes it more bad is, that this attribute is never resetet back to false. So all follow requests will fail because the response is not present.