roller-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Broderick <>
Subject error on startup
Date Mon, 16 Jun 2008 17:09:10 GMT

I built and installed Roller 4.0 as an exploded .war in Jboss 4.2.2 under Linux. I am getting
the following exception:

INFO  2008-06-16 11:38:54,732 WebloggerFactory:bootstrap - Bootstrapping Roller Weblogger
business tier
INFO  2008-06-16 11:38:54,732 WebloggerFactory:bootstrap - Weblogger Provider =
INFO  2008-06-16 11:38:54,735 DatabaseProvider:successMessage - SUCCESS: Got parameters. Using
configuration type JNDI_NAME
INFO  2008-06-16 11:38:54,736 DatabaseProvider:successMessage - -- Using JNDI datasource name:
INFO  2008-06-16 11:38:54,737 DatabaseProvider:successMessage - SUCCESS: located JNDI DataSource
INFO  2008-06-16 11:38:54,740 JPAPersistenceStrategy:<init> - openjpa.Log: commons
INFO  2008-06-16 11:38:54,943 IndexManagerImpl:<init> - search enabled: true
INFO  2008-06-16 11:38:54,944 IndexManagerImpl:<init> - index dir: /opt/apps/3party/jboss/roller_data/search-index
INFO  2008-06-16 11:38:54,952 ReferrerQueueManagerImpl:<init> - Instantiating Referrer
Queue Manager
INFO  2008-06-16 11:38:54,953 ReferrerQueueManagerImpl:<init> - Asynchronous referrer
processing = false
INFO  2008-06-16 11:38:54,955 ThreadManagerImpl:<init> - Instantiating Thread Manager
INFO  2008-06-16 11:38:54,958 WebloggerFactory:bootstrap - Roller Weblogger business tier
successfully bootstrapped
INFO  2008-06-16 11:38:54,959 WebloggerFactory:bootstrap -    Version: 4.0
INFO  2008-06-16 11:38:54,960 WebloggerFactory:bootstrap -    Revision: ${svn.LastChangedRev}
INFO  2008-06-16 11:38:54,960 WebloggerImpl:initialize - Initializing Roller Weblogger business
FATAL 2008-06-16 11:38:55,680 JPAPropertiesManagerImpl:initialize - Failed to initialize runtime
configuration properties.Please check that the database h   as been upgraded!
<0.9.7-incubating fatal user error> org.apache.openjpa.persistence.ArgumentException:
The type "class org.apache.roller.weblogger.pojos.TaskLock" has not    been enhanced.
        at org.apache.openjpa.meta.ClassMetaData.resolveMeta(
        at org.apache.openjpa.meta.ClassMetaData.resolve(
        at org.apache.openjpa.meta.MetaDataRepository.processBuffer(
        at org.apache.openjpa.meta.MetaDataRepository.resolveMeta(
        at org.apache.openjpa.meta.MetaDataRepository.resolve(
        at org.apache.openjpa.meta.MetaDataRepository.getMetaData(
        at org.apache.openjpa.meta.MetaDataRepository.resolveAll(
        at org.apache.openjpa.meta.MetaDataRepository.getQueryMetaData(
        at org.apache.openjpa.persistence.EntityManagerImpl.createNamedQuery(
        at org.apache.openjpa.persistence.EntityManagerImpl.createNamedQuery(
        at org.apache.roller.weblogger.ui.core.RollerContext.contextInitialized(

It looks like it finds the DB configuration OK (using SQL Server 2005, BTW), but then JPAPropertiesManagerImpl
throws the error.

Can anyone provide any insight into what might be going on?

Thanks in advance,



The  information in this email or in any file attached
hereto is intended only for the personal and confiden-
tial  use  of  the individual or entity to which it is
addressed and may contain information that is  propri-
etary  and  confidential.  If you are not the intended
recipient of this message you are hereby notified that
any  review, dissemination, distribution or copying of
this message is strictly prohibited.  This  communica-
tion  is  for information purposes only and should not
be regarded as an offer to sell or as  a  solicitation
of an offer to buy any financial product. Email trans-
mission cannot be guaranteed to be  secure  or  error-
free. P6070214

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message