Return-Path: Delivered-To: apmail-roller-user-archive@www.apache.org Received: (qmail 83985 invoked from network); 23 Oct 2007 17:00:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Oct 2007 17:00:02 -0000 Received: (qmail 70828 invoked by uid 500); 23 Oct 2007 16:59:48 -0000 Delivered-To: apmail-roller-user-archive@roller.apache.org Received: (qmail 70802 invoked by uid 500); 23 Oct 2007 16:59:48 -0000 Mailing-List: contact user-help@roller.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@roller.apache.org Delivered-To: mailing list user@roller.apache.org Received: (qmail 70758 invoked by uid 99); 23 Oct 2007 16:59:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2007 09:59:48 -0700 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=SPF_PASS,URI_NOVOWEL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [207.212.50.58] (HELO busybuddha.org) (207.212.50.58) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2007 16:59:49 +0000 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by busybuddha.org (8.14.1/8.14.1) with ESMTP id l9NGlIcZ010162; Tue, 23 Oct 2007 09:47:19 -0700 Message-ID: <471E2832.3050002@busybuddha.org> Date: Tue, 23 Oct 2007 09:58:26 -0700 From: Anil Gangolli User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: user@roller.apache.org CC: dev@roller.apache.org Subject: Re: Ping does this work for anyone References: <3478d5270710230940j1427268dnbbc037c37e9350c8@mail.gmail.com> In-Reply-To: <3478d5270710230940j1427268dnbbc037c37e9350c8@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I think the XML RPC client was updated to a newer rev and it is confusing the Roller's ping response parsing code. As a result, we aren't able to see the actual ping response value. It is just assuming that the response was OK; probably it wasn't. --a. Steve wrote: > Hi > I am having problems with Ping. I have registered with feedburner.com and > entered the urls of the feeds I wanted burnt. I have done this in the past > with Wordpress, and when I post in Wordpress I generally get a notification > from google with in a few minutes of the new blog entry. > > With roller I get nothing. If I click the ping button on the page then I > get a message saying the Ping was OK. The Ping task is picking up the new > posts and the trace below is the debug from the trace for feedburner. Does > that look good or bad. Some parts seem to say it is bad. > > > > > DEBUG 2007-10-23 15:54:00,888 WebloggerConfig:getProperty - Fetching > property [pings.logOnly=false] > DEBUG 2007-10-23 15:54:00,889 WebloggerRuntimeConfig:getProperty - fetched > property [site.absoluteurl=http://www.xxxxxxxxxx.com/roller] > DEBUG 2007-10-23 15:54:00,890 WeblogUpdatePinger:sendPing - Executing ping > to 'http://ping.feedburner.com' for website ' > http://www.xxxxxxxxxx.com/roller/maglor' (Maglor) > DEBUG 2007-10-23 15:54:01,114 WeblogUpdatePinger:parseResult - Invalid ping > result of type: java.util.HashMap; proceeding with stand-in representative. > DEBUG 2007-10-23 15:54:01,115 WeblogUpdatePinger:sendPing - Ping result is: > PingResult{error=false, message='{message=Ok, flerror=false}'} > DEBUG 2007-10-23 15:54:01,115 PingQueueProcessor:processQueueEntry - > Processed ping: {42911f63-ab05-4980-8284-8943a16f745e, 2007-10-23 15:44:33.0, > 0} > DEBUG 2007-10-23 15:54:01,116 JPAPingQueueManagerImpl:removeQueueEntry - > Removing ping queue entry: {42911f63-ab05-4980-8284-8943a16f745e, 2007-10-23 > 15:44:33.0, 0} > > > >