Hi Adel, I looked into an issue you had reported. I ran your sample application attached to the JIRA QPID-7420 and found that every time when application fails it sends 2 similar requests: first one is handled by the broker successfully and the other one fails because the work is already performed as part of first request. For example, if first request deletes the queue, the second one receives 404, as queue does not exist anymore.
Unfortunately it was tricky to discover that two same requests are made from the application, as Broker operational logging does not log failed management operation attempts. It seems we need to improve logging in this area. I had to switch to DEBUG logging in order to find the cause of the problem. I am not familiar with jersey and not sure why 2 requests are sent. It could be an issue with jersey itself or some settings... I am going to resolve QPID-7420 as not an issue. Kind Regards, Alex On 8 September 2016 at 09:24, Adel Boutros <[email protected]> wrote: > Hello guys, > > As I mentioned in my previous post, I am having some random REST call > failures when deleting and creating a queue. I was able to have a smaller > test code but still the error is very random. I launch my test code 10 000 > times to get the exception: The failure occurs sometimes at run 600 or run > 2000, etc... > > I don't know if someone has faced a similar issue before. > > I have also created a Jira issue for this with the minimalist test code I > could find so far: > https://issues.apache.org/jira/browse/QPID-7420 > > Do not hesitate to let me know if there are missing information. > > I have tested with Java Broker 6.0.0, 6.0.1 and 6.0.4 and they all have the > issue. > > I would like to keep debugging the issue from my side. So I was wondering if > you could provide me some hints where to look in the code or what to activate > to see in the logs if possible? > > Regards, > Adel > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
