Thank you, Dave.
Hibernate is certainly involved, albeit not at the configuration
level of which you speak.
Good advice, though, and thank you.
Earlier versions sometimes threw nonfatal Hibernate-related errors on
outward-facing multi-processing servers and less frequently on
development machines.
When I compiled from source specifically for and on the outward-
facing machines, and tuned Tomcat properly, errors there become rare
indeed.
Learning Hibernate well enough to remedy the current unhappiness is
on my morning to-do list.
Advice and counsel welcome.
Sought, in fact.
Thank you.
Respectfully,
George Frink
President,
Southern Connections Inc.
919 341 2999
[EMAIL PROTECTED]
On May 25, 2007, at 8:54 AM, Dave wrote:
On 5/25/07, George Frink <[EMAIL PROTECTED]> wrote:
--- ROOT CAUSE ---
org.hibernate.exception.SQLGrammarException: could not execute query
at org.hibernate.exception.SQLStateConverter.convert
(SQLStateConverter.java:65)
at org.hibernate.exception.JDBCExceptionHelper.convert
(JDBCExceptionHelper.java:43)
at org.hibernate.loader.Loader.doList(Loader.java:2148)
at org.hibernate.loader.Loader.listIgnoreQueryCache
(Loader.java:2029)
at org.hibernate.loader.Loader.list(Loader.java:2024)
at org.hibernate.loader.criteria.CriteriaLoader.list
(CriteriaLoader.java:94)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:
1552)
at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:
283)
at
org.apache.roller.business.hibernate.HibernatePingTargetManagerImpl.g
etC
ommonPingTargets(HibernatePingTargetManagerImpl.java:207)
That SQLGrammarException might indicate that you are not using he
right Hibernate Dialect for Roller. By default Roller is configured to
use MySQL4. If you want to run on MySQL5 you have to override the
'hibernate.dialect' property in your roller-custom.properties file
like so:
hibernate.dialect=org.hibernate.dialect.MySQL5Dialect
- Dave
