Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 47733 invoked from network); 8 Nov 2010 11:39:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Nov 2010 11:39:58 -0000 Received: (qmail 24870 invoked by uid 500); 8 Nov 2010 11:40:30 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 24808 invoked by uid 500); 8 Nov 2010 11:40:28 -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 24800 invoked by uid 99); 8 Nov 2010 11:40:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 11:40:26 +0000 X-ASF-Spam-Status: No, hits=4.7 required=10.0 tests=FREEMAIL_FROM,FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of esjewett@gmail.com designates 209.85.212.47 as permitted sender) Received: from [209.85.212.47] (HELO mail-vw0-f47.google.com) (209.85.212.47) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Nov 2010 11:40:19 +0000 Received: by vws17 with SMTP id 17so1621457vws.6 for ; Mon, 08 Nov 2010 03:39:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=0GL8/DPSPsruQaeJtFhBUw+Pa3kU31HZxXg/4NWVHW4=; b=AvkIS0euLBqY4TR4KIrT5wnjOU4P6gAq6mPW8dSw07Y5sLbiA6fywXCpt1cj8yagve 4fENzH7SFT5FUuH8L3TG+QuLLj9v1BvQfx/i2pEQbZUo9o+5c+206Y886SIqROEAhu+8 u+eqMX41JulelGhqDZIhTKSxjQ8jR0VC2CXtM= 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=nJ628oVRGbXakshouXngwX5sCVfXtBy1ZSj5JTcGc8MnI2IWw02wEz+RONBMfbCGyc Ax/KhsI4mzPtrCVJERd5LAfFIB8wHC3WFXF2mgzEcIkSW/65YEQu1QT4vOsZRAvg92/z 2SpkJkx50AAZXbuQRxt5rFtaPeUWzYt7EBIqs= MIME-Version: 1.0 Received: by 10.224.201.137 with SMTP id fa9mr3985793qab.10.1289216398042; Mon, 08 Nov 2010 03:39:58 -0800 (PST) Received: by 10.220.188.75 with HTTP; Mon, 8 Nov 2010 03:39:57 -0800 (PST) In-Reply-To: References: Date: Mon, 8 Nov 2010 12:39:57 +0100 Message-ID: Subject: Re: The 'other' Anne breaks the timeline From: Ethan Jewett To: esme-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=20cf300faf4b71a4a30494891563 X-Virus-Checked: Checked by ClamAV on apache.org --20cf300faf4b71a4a30494891563 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hmmm, Anne's user page isn't working now. Can you check the logs for the last 2 hrs? My timeline is always like that (empty) after a server restart. I'm not sur= e why that happens to me, but I bet it has to do with the invisible messages in my timeline from the "every 5 mins" actions. I have been meaning to try to refactor and evict those messages into a whole separate messaging subsystem for the actors, but I haven't even gotten around to thinking abou= t if that makes sense, much less creating a Jira item for it :-) Ethan On Mon, Nov 8, 2010 at 10:10 AM, Richard Hirsch wrot= e: > Still looks good - I'll look into the stax log every once in a while > to see if have any more exceptions. > > On Mon, Nov 8, 2010 at 9:08 AM, Richard Hirsch > wrote: > > Just deployed on stax with vassil's code change. > > > > Anne's timeline is now visible without an error. What is even stranger > > is that ethan's timeline is also visible but just with my last > > message. Normally Ethan's timeline is empty, so I was a little bit > > surprised. > > > > I'll take another look in 5 minutes to see if everything is still visib= le > > > > D. > > > > On Sun, Nov 7, 2010 at 3:59 PM, Richard Hirsch > wrote: > >> @vassil Thanks for fixing the bug - it was filling our stax log > >> > >> I'll do a new stax deployment tomorrow and then we'll see if the prob > >> was the rss feed. > >> > >> D. > >> > >> On Sat, Nov 6, 2010 at 9:16 AM, Vassil Dichev > wrote: > >>> You're right, it doesn't seem like parsing the feed should break the > >>> timeline, but it's good to fix this so that we eliminate any doubt > >>> that it causes problems. Besides, it's not a good idea to assume that > >>> only correctly formatted dates will be passed our way, so I wanted to > >>> put an end to ESME-275. > >>> > >>> I've just committed a fix and closed the issue. > >>> > >>> Vassil > >>> > >>> > >>> On Sat, Nov 6, 2010 at 10:06 AM, Ethan Jewett > wrote: > >>>> Dick, > >>>> > >>>> If you want to disable my actions to test, that's fine. I'm fairly > >>>> confident my actions are responsible for the stack trace you sent. > >>>> (Thanks for looking in to it Vassil.) > >>>> > >>>> I just don't see how an issue with actions could be the cause of the > >>>> timeline issue. As far as I know, loading a timeline does not trigge= r > >>>> this action code that is failing. I could definitely be wrong, but I > >>>> think there should be a second stack trace or a Lift error message > >>>> that shows up in the logs when someone tries to load Anne or David's > >>>> user page. > >>>> > >>>> Ethan > >>>> > >>>> On Saturday, November 6, 2010, Vassil Dichev > wrote: > >>>>> The reason for the stack trace is that a date in an RSS feed cannot > be > >>>>> parsed properly, or there is no date at all (which as I see is > allowed > >>>>> by the RSS spec). It would help if we can find which RSS feed is th= e > >>>>> culprit, but I will try to come up with a patch anyway. > >>>>> > >>>>> Vassil > >>>>> > >>>>> > >>>>> On Sat, Nov 6, 2010 at 9:05 AM, Richard Hirsch < > hirsch.dick@gmail.com> wrote: > >>>>>> I'm working on the following assumptions: > >>>>>> > >>>>>> 1) that someone anne follows is the culprit > >>>>>> 2) That the reason is some sort of an action that is called ever= y > 5 > >>>>>> minutes or so > >>>>>> 3) Checking the database shows that the most of these actions ar= e > from Ethan > >>>>>> > >>>>>> What I'm going to try is to create a test user and then follow the > >>>>>> users that anne follows. > >>>>>> > >>>>>> However, you are correct in saying that I'm following you as well > and > >>>>>> my timeline is working. > >>>>>> > >>>>>> If you want, we can wait until I do this test before taking such > >>>>>> drastic "Big Brother" actions. > >>>>>> > >>>>>> D. > >>>>>> > >>>>>> > >>>>>> > >>>>>> On Fri, Nov 5, 2010 at 8:25 PM, Ethan Jewett > wrote: > >>>>>>> I knew I shouldn't have implied it might be me :-) > >>>>>>> > >>>>>>> I definitely have RSS actions, but I'm wondering what makes you > think it's > >>>>>>> my actions that are breaking only Anne & Dave's timelines? You an= d > several > >>>>>>> others follow me, and your timelines are not broken. Before we sa= w > this sort > >>>>>>> of thing happened because of special characters in some messages, > right? > >>>>>>> > >>>>>>> I'm really wondering if the stack trace you found was the only > error. I > >>>>>>> think the stack trace you found was the issue in Jira item > >>>>>>> https://issues.apache.org/jira/browse/ESME-275 This appears to > still be > >>>>>>> unresolved, but I don't think we ever linked it to an issue with > displaying > >>>>>>> a timeline (which should have nothing to do with a feed or action= ). > >>>>>>> > >>>>>>> Ethan > >>>>>>> > >>>>>>> On Fri, Nov 5, 2010 at 7:42 PM, Richard Hirsch < > hirsch.dick@gmail.com>wrote: > >>>>>>> > >>>>>>>> Going through the database - looks like Ethan might be the culpr= it > - > >>>>>>>> though I don't know why. > >>>>>>>> > >>>>>>>> @Ethan do want to disable your rss actions manually or should I = do > it > >>>>>>>> via big brother ;-> > >>>>>>>> > >>>>>>>> D. > >>>>>>>> > >>>>>>>> On Fri, Nov 5, 2010 at 2:07 PM, Anne Kathrine Petter=F8e > >>>>>>>> wrote: > >>>>>>>> > LOL :-) > >>>>>>>> > > >>>>>>>> > > >>>>>>>> > On 5 November 2010 13:29, Ethan Jewett > wrote: > >>>>>>>> > > >>>>>>>> >> I hope it's not me. [Shakes in boots.] :-) > >>>>>>>> >> > >>>>>>>> >> On Fri, Nov 5, 2010 at 12:16 PM, Richard Hirsch < > hirsch.dick@gmail.com > >>>>>>>> >> >wrote: > >>>>>>>> >> > >>>>>>>> >> > I can look at the DB when I get home and see who the culpri= t > is. > >>>>>>>> >> > > >>>>>>>> >> > D. > >>>>>>>> >> > > >>>>>>>> >> > On Fri, Nov 5, 2010 at 11:44 AM, Anne Kathrine Petter=F8e > >>>>>>>> >> > wrote: > >>>>>>>> >> > > Do we know who has set up an action that would create the > problem? > >>>>>>>> >> > > > >>>>>>>> >> > > /Anne > >>>>>>>> >> > > > >>>>>>>> >> > > On 5 November 2010 10:07, Ethan Jewett > wrote: > >>>>>>>> >> > > > >>>>>>>> >> > >> Yup, that would explain it. When you sent the stack trac= e > before, > >>>>>>>> was > >>>>>>>> >> > that > >>>>>>>> >> > >> the only one that you saw in the Stax environment or whe= re > there > >>>>>>>> >> others? > >>>>>>>> >> > >> > >>>>>>>> >> > >> Ethan > >>>>>>>> >> > >> > >>>>>>>> >> > >> On Fri, Nov 5, 2010 at 9:34 AM, Richard Hirsch < > >>>>>>>> hirsch.dick@gmail.com > >>>>>>>> >> > >> >wrote: > >>>>> -- > >>>>> Twitter: http://twitter.com/vdichev > >>>>> Blog: http://speaking-my-language.blogspot.com > >>>>> > >>>> > >>> > >>> > >>> > >>> -- > >>> Twitter: http://twitter.com/vdichev > >>> Blog: http://speaking-my-language.blogspot.com > >>> > >> > > > --20cf300faf4b71a4a30494891563--