You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@roller.apache.org by Eric Wittle <er...@wittle.net> on 2008/02/26 23:50:58 UTC

Attempting planet startup debugging

OK, in the absence of more specific suggestions, I tried to turn on  
debug logging for most of the interesting classes I could find in  
roller-planet-business.jar. Specifically, I added the following to  
both roller-custom.properties and planet-custom.properties:

# Planet Debugging
log4j.category.org.apache.roller.planet.business.Manager=DEBUG
log4j.category.org.apache.roller.planet.business.PlanetFactory=DEBUG
log4j.category.org.apache.roller.planet.business.PlanetManager=DEBUG
log4j.category.org.apache.roller.planet.business.PlanetProvider=DEBUG
log4j 
.category.org.apache.roller.planet.business.startup.PlanetStartup=DEBUG
log4j 
.category 
.org 
.apache.roller.weblogger.ui.rendering.servlets.PlanetFeedServlet=DEBUG

I then cleaned out the log files and restarted. No error message or  
additional debug messages were apparent. When I browsed to the planet  
RSS feed URL, I got the same exception, and maybe one debug statement.  
The relevant snippet of the log is:

INFO  2008-02-26 17:44:14,288 PlanetFeedServlet:init - Initializing  
PlanetRssServlet
INFO  2008-02-26 17:44:14,289 PlanetCache:<init> - Planet cache =  
{id=cache.planet, enabled=true, timeout=1800, size=10}
INFO  2008-02-26 17:44:14,293 PreviewResourceServlet:init -  
Initializing PreviewResourceServlet
INFO  2008-02-26 17:44:14,294 PreviewThemeImageServlet:init -  
Initializing PreviewThemeImageServlet
INFO  2008-02-26 17:44:14,298 PreviewServlet:init - Initializing  
PreviewServlet
DEBUG 2008-02-26 17:44:20,433 PlanetFeedServlet:doGet - Entering
ERROR 2008-02-26 17:44:20,438 StandardWrapperValve:invoke -  
Servlet.service() for servlet PlanetFeedServlet threw exception
java.lang.IllegalStateException: Roller Planet has not been  
bootstrapped yet

So I'm still at a loss about what to look at next. Exactly what class  
is responsible for "bootstrapping" roller planet, and should I expect  
that debug logging will be helpful in telling me what is wrong?

I'm still betting it is data in my Roller database. Are there log  
levels that will let me see the SQL queries it is generating? I  
suppose I could turn on SQL logging in MySQL...

-Eric

Re: Attempting planet startup debugging

Posted by Allen Gilliland <Al...@Sun.COM>.
bootstrapping the planet backend happens in the 
RollerContext.contextInitialized method, just like with the weblogger 
backend.  Both of the planet and weblogger backends run through the same 
steps ... prepare (test for core services like db connection), bootstrap 
(wire up backend classes), and initialize (a chance for objects to do 
initialization work that must happen after bootstrapping).

I'm not sure exactly what your problem is, but the planet backend 
provides INFO level logging about its bootstrapping progress, so if you 
think it's not bootstrapping properly it should show you without having 
to mess with DEBUG logging.

-- Allen


Eric Wittle wrote:
> OK, in the absence of more specific suggestions, I tried to turn on 
> debug logging for most of the interesting classes I could find in 
> roller-planet-business.jar. Specifically, I added the following to both 
> roller-custom.properties and planet-custom.properties:
> 
> # Planet Debugging
> log4j.category.org.apache.roller.planet.business.Manager=DEBUG
> log4j.category.org.apache.roller.planet.business.PlanetFactory=DEBUG
> log4j.category.org.apache.roller.planet.business.PlanetManager=DEBUG
> log4j.category.org.apache.roller.planet.business.PlanetProvider=DEBUG
> log4j.category.org.apache.roller.planet.business.startup.PlanetStartup=DEBUG 
> 
> log4j.category.org.apache.roller.weblogger.ui.rendering.servlets.PlanetFeedServlet=DEBUG 
> 
> 
> I then cleaned out the log files and restarted. No error message or 
> additional debug messages were apparent. When I browsed to the planet 
> RSS feed URL, I got the same exception, and maybe one debug statement. 
> The relevant snippet of the log is:
> 
> INFO  2008-02-26 17:44:14,288 PlanetFeedServlet:init - Initializing 
> PlanetRssServlet
> INFO  2008-02-26 17:44:14,289 PlanetCache:<init> - Planet cache = 
> {id=cache.planet, enabled=true, timeout=1800, size=10}
> INFO  2008-02-26 17:44:14,293 PreviewResourceServlet:init - Initializing 
> PreviewResourceServlet
> INFO  2008-02-26 17:44:14,294 PreviewThemeImageServlet:init - 
> Initializing PreviewThemeImageServlet
> INFO  2008-02-26 17:44:14,298 PreviewServlet:init - Initializing 
> PreviewServlet
> DEBUG 2008-02-26 17:44:20,433 PlanetFeedServlet:doGet - Entering
> ERROR 2008-02-26 17:44:20,438 StandardWrapperValve:invoke - 
> Servlet.service() for servlet PlanetFeedServlet threw exception
> java.lang.IllegalStateException: Roller Planet has not been bootstrapped 
> yet
> 
> So I'm still at a loss about what to look at next. Exactly what class is 
> responsible for "bootstrapping" roller planet, and should I expect that 
> debug logging will be helpful in telling me what is wrong?
> 
> I'm still betting it is data in my Roller database. Are there log levels 
> that will let me see the SQL queries it is generating? I suppose I could 
> turn on SQL logging in MySQL...
> 
> -Eric
>