Does the problem reproduce with 3.3.1.BETA4?
Queues functionality is implemented solely on the client; queue server code is just a supporting code serving queue initialization parameters to the client.
If you use several queues, this can be the reason, because requests from several queues can work in parallel, thus causing synchronization problems.
Thanks. I didn't know that queues are implemented on client and it makes sense to do it that way. I can't blame them any more than :).
I will try to use 3.3.1 the problem is i can't reproduce it on my development machine it seems to appear on live site or during performance tests and only on some of the requests (very weird :( ).
>If you use several queues, this can be the reason, because requests from >several queues can work in parallel, thus causing synchronization problems.
What synchronization problems? I don't see any concurent calls problem or anything like this it just something is stoping request from processing and i don't know what it is :(.