Queue: updateMessage exposes bug in Queue service #105
Comments
ghost
assigned 
gcheng
pushed a commit
to gcheng/azure-sdk-for-java
that referenced
this issue
Feb 27, 2013
jianghaolu
pushed a commit
to jianghaolu/azure-sdk-for-java
that referenced
this issue
Apr 5, 2017
navalev
pushed a commit
to navalev/azure-sdk-for-java
that referenced
this issue
Dec 24, 2019
Adds custom deserializers for well-known types. Allows OffsetDateTime and GeoPoint to roundtrip as strongly typed objects in dynamic Maps Fixes the following indexing test cases to match .Net scenarios: - canIndexWithPascalCaseFields - dynamicDocumentDateTimesRoundTripAsUtc - staticallyTypedDateTimesRoundTripAsUtc - canMergeDynamicDocuments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Copied from issue 207 on the private repository.
According to http://msdn.microsoft.com/en-us/library/windowsazure/hh452234.aspx, the visibilitytimeout when updating "cannot be set to a value later than the expiry time", but that does not seem to be enforced. Here are the HTTP traces showing that is not the case, where first I set the TTL to 6 seconds, then update the visibility timeout to 8 seconds. I'm entering this issue into our database for tracking; I don't know where to enter the issue for the Queue service team.
POST http://azuresdkdev.queue.core.windows.net/qa-691182-a1/messages?timeout=4&messagettl=6
HTTP/1.1 201 Created
GET http://azuresdkdev.queue.core.windows.net/qa-691182-a1/messages
HTTP/1.1 200 OK
c63223fa-4825-4c08-8ac8-f069d73fe856
Wed, 18 Jan 2012 21:15:13 GMT
Wed, 18 Jan 2012 21:15:19 GMT
1
AgAAAAEAAAApAAAAWBVjVibWzAE=
Wed, 18 Jan 2012 21:15:43 GMT
foo bar
PUT http://azuresdkdev.queue.core.windows.net/qa-691182-a1/messages/c63223fa-4825-4c08-8ac8-f069d73fe856?popreceipt=AgAAAAEAAAApAAAAWBVjVibWzAE%3D&visibilitytimeout=8
HTTP/1.1 204 No Content
The text was updated successfully, but these errors were encountered: