Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 53286 invoked from network); 20 Mar 2010 18:45:46 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Mar 2010 18:45:46 -0000 Received: (qmail 83113 invoked by uid 500); 20 Mar 2010 18:45:46 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 83093 invoked by uid 500); 20 Mar 2010 18:45:46 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 83085 invoked by uid 99); 20 Mar 2010 18:45:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Mar 2010 18:45:46 +0000 X-ASF-Spam-Status: No, hits=-1.2 required=10.0 tests=AWL,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of esjewett@gmail.com designates 209.85.160.47 as permitted sender) Received: from [209.85.160.47] (HELO mail-pw0-f47.google.com) (209.85.160.47) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Mar 2010 18:45:38 +0000 Received: by pwi6 with SMTP id 6so2844947pwi.6 for ; Sat, 20 Mar 2010 11:45:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=Iu7LCOii/6qWpOYsT2slIKYmK5Ey9cE4JW9S+WMVkYM=; b=KoWKYdHxx+l1HxsYMsy99OE6XVSuLDzhgTWu0CwX3UTyctXKhYw/6GajZoVsaArOs4 vo82tE2sBo+eIw9Cu9EzW4fRhOBhJ6wZtjXSYCf3CMWX0lofBZ2gTQfrvoiVrr9J/e4r 37rMy0y0LHC+ioMQ6tThwageFGduU1ln1dGn8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=K9qyVeKwieFVm482rBsrqGbRLKEehgoTLHfQ6G9iDmd1mDjCKi4q6pmzAoJoxKx2JZ Tg56wbNVNCfsiUovAwA4vX/e2kExywviaralgB5cexnVXpcg3oLsuiOdT14kA4ZR76hM irzEUktz+1ifAh9DlOn5Enz/f1kTvVX/GhB+U= MIME-Version: 1.0 Received: by 10.141.107.6 with SMTP id j6mr2667955rvm.288.1269110718300; Sat, 20 Mar 2010 11:45:18 -0700 (PDT) In-Reply-To: References: <68f4a0e81003191425x7abf0845t361837c49371f055@mail.gmail.com> <68f4a0e81003200807v3b39f759p23b3bfaca5502ea1@mail.gmail.com> Date: Sat, 20 Mar 2010 12:45:18 -0600 Message-ID: <68f4a0e81003201145v3473d3ccwe9db305eb6cb1f2@mail.gmail.com> Subject: Re: Current version on Stax From: Ethan Jewett To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Ok, I think I've got it. The reason appears to be the regular action I have set up to pull my Twitter feed puts a message into my user's mailbox. This message is never displayed in the timeline. However, these messages, inserted into my mailbox every 5 minutes, have the affect of pushing other messages out of my mailbox. It takes 5*40 = 200 minutes for 40 of these non-displayed messages to build up in my mailbox and push out all other messages. I have now verified this locally (it goes faster if you set up a bunch of regular actions (every 1 mins)) and I will create a JIRA issue and patch. My patch strategy is going to be to never add messages to the mailbox when they have a message ID of -1, which seems to be the convention for regular actions. Ethan On Sat, Mar 20, 2010 at 10:05 AM, Richard Hirsch wrote: > It is strange - I saw one of the messages from your private pool on the > public streams page a while back. > > There are other users who use twitter feeds as well. Maybe it is the filter > on the twitter stream > > D. > > On Sat, Mar 20, 2010 at 4:07 PM, Ethan Jewett wrote: > >> No, I can't reproduce the problem locally. Everyone else's timelines >> seem to be working fine, so it must be something specific to what I >> have configured. Either a rogue action on the server, or something I >> have done is causing a bug to show up. >> >> Currently, I don't really have anything complicated set up on the server: >> >> 1 action to pull my Twitter feed every 5 minutes and post messages >> containing the words "esme" or "sap" to the ESME instance >> >> 2 pools - one private test one, and one ESME team pool >> >> As far as I can tell, that's it. I'll see if I can access the Stax >> database later today to see if there might be any actions specific to >> me that I can't see in the web ui. >> >> Ethan >> >> On Fri, Mar 19, 2010 at 10:44 PM, Richard Hirsch >> wrote: >> > The trunk. The UI branch doesn't exist amy more. >> > >> > can you reproduce the problem locally? >> > >> > On Fri, Mar 19, 2010 at 10:25 PM, Ethan Jewett >> wrote: >> > >> >> This one is probably for Dick, but in case someone else can answer: >> >> >> >> Is the current ESME deployment on the Stax instance based on trunk or >> >> from the UI branch? I ask because I still have my timeline issue. I >> >> have my fingers crossed that it's not from trunk yet :-) >> >> >> >> Ethan >> >> >> > >> >