We should probably take this onto the JIRA and track progress there, or at least switch to direct e-mail until we resolve it.

Here's my next suggestion. Edit the log4j.properties file in the WEB-INF/classes subdir of the Roller webapp. Change the logging level in log4j.category.org.apache.velocity=FATAL to WARN. Restart. See if we get more info.

--a.


Jon wrote:

Hi Anil, thanks for replying:

On Saturday 05 November 2005 5:08 am, Anil Gangolli wrote:
Jon wrote:
Hi, I've been trying to make Roller 1.2 work but I can get nothing
other the following exception when I request a page:

ERROR 2005-11-04 19:29:32,868 | NavigationBarTag:prepareContext |
org.roller.RollerException: ERROR creating Page Model
ERROR 2005-11-04 19:29:32,878 | NavigationBarTag:doEndTag |
EditorNavigationBarTag exception
org.roller.RollerException: Failure initializing ContextLoader.
      at
org.roller.presentation.tags.menu.NavigationBarTag.doEndTag(NavigationBar
Tag.java:158)

      at
org.roller.presentation.tags.HybridTag.doEndTag(HybridTag.java:64)
      at
org.apache.jsp.main_jsp._jspx_meth_roller_NavigationBar_0(main_jsp.java:5
56)

      at org.apache.jsp.main_jsp._jspService(main_jsp.java:181)
      at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
... (usual Tomcat stack trace follows.)
Is there a nested / root cause exception printed.? There's not enough
juicy info in the top level one.

No, there is no nested exception. I was hoping someone would know what
can cause this one.

Also, please  look for an ERROR in the roller.log just prior to this.

There are no other ERROR messages before the two lines above. The
previous line in the log is an INFO line about LoginServlet:init at the
end of the various filter/servlet init messages.

Will need more information to be able to diagnose it at all.

If you can tell me where to look or what to do to get more information
I'd be grateful!

Are there any other errors in the roller.log or in the tomcat logs?

No, none. Except that immediately after the one I listed out above,
there is another identical one thrown in error.jsp - evidently the
normal error page can't be rendered either. The unexpected exception
page and the dstest.jsp page mentioned in the install guide work OK,
presumably because they don't use Velocity.

Also, it may help if you start tomcat in a shell window and observe the output for
errors there.

That's what I did to get the error above (it appears both in catalina.out
and roller.log).

Any more suggestions for where to look?

Jon

Reply via email to