This warning appears if the ping queue processor task runs before there have been any requests made to the server and you have not
set an explicit site URL in the configuration.
Due to a quirk/limitation of the Servlet API, the webapp is unable to determine the absolute context url unless it is set explicitly
in the configuration or until after the first request. It needs the full site url to determine the urls to put in outbound pings.
If it can't determine it, it logs this and skips one round of ping processing.
The ping queue processor task runs every five minutes by default. You'll see one of these each time the ping queue task runs until
at least one request has been received by Roller.
Most production environments will never see this. You might see this in trial and development if start the server and just let it
sit there for awhile. You shouldn't see them after you start doing stuff.
You don't have to fix anything, as things should be fine as soon as your server starts to see any activity. However, you can
address it by setting your site url explicitly in the static configuration (roller.properties/roller-custom.properties).
I'll add this to the FAQ.
----- Original Message -----
From: "Gili" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, July 18, 2005 1:24 PM
Subject: WARNING: Skipping current ping queue processing round because we
cannot yet determine the site's absolute context url
Hi,
I see this warning in my logs, any ideas what's causing it and how to fix it?
PingQueueProcessor:processQueue | WARNING: Skipping current ping queue processing round because we cannot yet determine the site's
absolute context url.
Thanks,
Gili
--
http://www.desktopbeautifier.com/
