Weblog update ping results are not parsed properly
--------------------------------------------------
Key: ROL-1585
URL:
http://opensource.atlassian.com/projects/roller/browse/ROL-1585
Project: Roller
Issue Type: Bug
Affects Versions: 4.0
Reporter: Anil Gangolli
Assignee: Anil Gangolli
Priority: Minor
There is a minor issue with the ping response parsing due to the XML rpc
client upgrade; the old client used to return HashTable; the new client returns
a HashMap. I'm updating to code to expect any Map type.
If you have DEBUG logging set you'll see messages like this:
DEBUG 2007-10-23 15:54:01,114 WeblogUpdatePinger:parseResult - Invalid ping
result of type: java.util.HashMap; proceeding with stand-in representative.
This is preventing proper detection of error results when they occur. When
errors are detected, the automatic ping processing code will retry failed pings
a configured number of times (default 3) at subsequent ping queue processing
intervals; with the current parsing issue retrials never occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/roller/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
