Closed GoogleCodeExporter closed 9 years ago
You are correct in assuming the value passed in receiveMessage(int) should
override
the queue default. I've been using that in my own application. 300 seconds
should be
long enough to keep it hidden from subsequent reads. Are you getting the same
message
ids on the messages? Have you run a simple case where there is only one message
in
the queue so there is no chance of another message fooling you?
I've attached a file that is in subversion. It was my test for the visibility
timeout. have a look and try running it.
David
Original comment by dkavan...@gmail.com
on 7 Sep 2007 at 8:59
Attachments:
to clarify, i am actually "trying" to retrieve an array of messages of size 10
- and
I set the default visibility timeout of the queue to 300...
Thanks
Original comment by loca...@gmail.com
on 7 Sep 2007 at 9:43
Thanks Dave, the previous post (when trying to get one message) actually worked,
there was a bug in my code... however I am fairly certain that the
receiveMessages(int num) doesn't:
I get the same message id returned multiple times...
thanks
Original comment by loca...@gmail.com
on 7 Sep 2007 at 9:45
[deleted comment]
Flo,
I want to make sure this issues is resolved, or that I can fix something if
there is
something I can fix. To clarify, all receive message calls get funneled through
the
same receiveMessages(BigInt, BitInt) call. I saw you asking about the default
visibility timeout for a queue. That is set to 30 seconds (per the developer's
guide).
David
Original comment by dkavan...@gmail.com
on 28 Sep 2007 at 11:11
This turned out not to be a bug in the typica code. Closing this out.
Original comment by dkavan...@gmail.com
on 5 Nov 2007 at 8:31
Original issue reported on code.google.com by
loca...@gmail.com
on 7 Sep 2007 at 8:24