That's strange that it would be hit more than once. I can't think of a reason that would happen other than the zmq socket delivered it more than once, but, please feel free to email me directly when you're back at your work machine and we'll work through it.
On Sat, Dec 14, 2013 at 5:34 PM, Samantha Atkins <[email protected]> wrote: > I know the call is made as I see it hit in the debugger. But I see it hit > more than once as it is being executed again. I am not at my work machines > for a few days. > > On Dec 14, 2013, at 12:42 PM, James Dennis <[email protected]> wrote: > > Would you be willing to share your environment, so I can reproduce? > > If not, could you try adding logging to verify Brubeck receives the > request and begins processing it until <some line>? > > > On Sat, Dec 14, 2013 at 3:13 PM, Samantha Atkins <[email protected]>wrote: > >> API call made. Fails due to bad parameters. Gets retried internal to >> mongrel2 or brubeck (not sure which) for about 10 seconds before any result >> returns to the client. >> >> >> On Sat, Dec 14, 2013 at 11:40 AM, James Dennis <[email protected]> wrote: >> >>> Hello. >>> >>> I am the author of Brubeck, which is currently under heavy construction: >>> https://github.com/j2labs/brubeck/tree/nubeck >>> >>> There is no particular part of Brubeck which retries something. Could >>> you please elaborate on the behavior you're seeing? >>> >>> James >>> >>> >>> On Fri, Dec 13, 2013 at 6:50 PM, Samantha Atkins <[email protected]>wrote: >>> >>>> I have noticed that sometimes when a web api call fails that some part >>>> of the mongrel2 or the brubeck.io machinery seems to be retrying the >>>> call. This is not desired behavior. Perhaps I missed it in my read >>>> through but how do I turn this behavior off? In particular a call from the >>>> client that should succeed or fail almost immediately instead seems to hang >>>> while some part of the machinery is doing some retry dance. >>>> >>>> How do i change this? >>>> >>>> - samantha >>>> >>> >>> >> > >
