we have this problem, I am new to azure, and from what I can see it is happening, this sounds very bad.
we have a simple aspx page that is requested by the client, on the code behind the request gets authenticated and then it inserts one row per call, instead we see duplicates up to 60x...
anybody can comment on this? searching the net I could find similar problems reported but most of them as WFC calls; in our case it is a http get to an aspx page
testing the client is shows no problems whatsoever. the problem is somewhere on the front end or backend. but as I said, front end and backend are very simple; done this kind of apps so many times I am pretty sure is nothing wrong with the code. we ran also
tests, which confirmed the client is making only one http get call. yet on the DB we end up with as many as 60 duplicate entires sometimes (the duplicates are random from 2 to 60)
any help would be appreciated; we know we can go around this by filtering out the duplicated, however if there is a much better solution (and I believe it is) we wuold like to implement that one, maybe it is a known issue and we have to configure our azure
services differently?... anything that would help please let us know
thank you
- Edited by OptimalSoftware Monday, July 13, 2015 9:52 AM
Other recent topics
