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}
