esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hirsch <hirsch.d...@gmail.com>
Subject Re: Something is hitting the stax instance
Date Thu, 17 Dec 2009 16:43:13 GMT
No problem. Just glad we found what was causing the heavy load.

I'd try against the perf instance any way. At the current time, it is
more up-to-date and should have better performance.

D.

On Thu, Dec 17, 2009 at 5:16 PM, Ethan Jewett <esjewett@gmail.com> wrote:
> Ok, it should be killed off. I apologize for that. I had old versions
> of the client running, which I incorrectly thought I had killed off.
> These old versions of the client kept requesting the timeline even
> after their session had expired, and they didn't wait at all between
> requests.
>
> The newer version of the client doesn't suffer from this issue, so we
> should be ok. However, I'm thinking maybe I should test against the
> performance instance for a while to make sure....
>
> Ethan
>
> On Thu, Dec 17, 2009 at 11:07 AM, Ethan Jewett <esjewett@gmail.com> wrote:
>> That'd be my Growl client. Sorry. Killing it now...
>>
>> On Thu, Dec 17, 2009 at 11:06 AM, Richard Hirsch <hirsch.dick@gmail.com> wrote:
>>> Right now, something is flooding the apache instance with calls
>>>
>>> 65.90.202.10 - - [17/Dec/2009:16:00:46 +0000] "GET
>>> /api2/user/messages?timeout=300 HTTP/1.1" 403 0 "-" "-"
>>>
>>> Location of IP Address is:
>>> Camden (New Jersey) in United States
>>>
>>> Anyone know what this could be?
>>>
>>> D.
>>>
>>
>

Mime
View raw message