roller-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anil Gangolli <a...@busybuddha.org>
Subject Re: Upgrade from 4.0 to 4.0.1 fails with glassfish and Derby
Date Sat, 17 Jan 2009 16:16:23 GMT

Also, as a practical matter, if you need to workaround this, you can 
manually

update roller_properties set value = '401' where 
name='roller.database.version';

(and commit).  Then restart Roller.

--a.




Anil Gangolli wrote:
>
>
> I'm suspecting a problem in the upgrade code.  I'll try to see if I 
> can reproduce this.
>
> In the meantime, can you look at your roller_properties table in your 
> database directly and see if
>
> select value from roller_properties where name='roller.database.version';
>
> returns 401 or 400?
>
> --a.
>
>
>
>
>
>
>
> Stephan M├╝hlstrasser wrote:
>> Am Samstag, den 17.01.2009, 00:36 +0100 schrieb Stephan M├╝hlstrasser:
>>  
>>> Ah, thank you, I see my mistake. I followed the instructions from 
>>> the Wiki to get the sources from SVN, and I didn't think about the 
>>> fact that I would get something later than 4.0.1.
>>>
>>> I did this:
>>>
>>> svn checkout https://svn.apache.org/repos/asf/roller/trunk roller_trunk
>>>
>>> I will now try to check out with the roller_4.0.1 tag, and see 
>>> whether that fixes my problem.
>>>
>>> Thanks
>>> Stephan
>>>
>>>     
>>
>> There seems to be a general problem. After I had the same problem again
>> with a Roller 4.0.1 built from source, I tried the binary download from
>> here:
>>
>> http://apache.speedbone.de/roller/roller-4/v4.0.1/bin/apache-roller-4.0.1.zip 
>>
>>
>> This is what I did:
>>
>> - again contents of my roller-custom.properties file:
>>
>> installation.type=auto
>> database.configurationType=jndi
>> database.jndi.name=jdbc/rollerdb
>> mail.configurationType=properties
>> mail.hostname=<removed>
>> mail.username=<removed>
>> mail.password=<removed>
>>
>> - restored my original Roller 4.0 Derby database
>> - unzipped apache-roller-4.0.1.zip
>> - created a war file by going to the unzipped directory to
>> apache-roller-4.0.1/webapp/roller and executing "jar cvf ../roller.war
>> *"
>> - undeployed my old roller web application from Glassfish
>> - deployed the new roller.war file
>> - pointed browser to the Roller context root, browser shows the
>> following text:
>>
>> Database tables need to be upgraded
>> Roller is able to connect to your database of type [Apache Derby] and
>> found tables, but the tables need to be upgraded.
>> Would you like Roller to upgrade the tables for you?
>>
>> - pushed the "Yes - upgrade tables now" button
>> - browser displays the following:
>>
>> Error upgrading tables
>> Error upgrading tables, possibly due to an error in the database
>> creation script or because you are using an unsupported database. You
>> will have to fix this problem and then restart or redeploy Roller before
>> you can proceed. Below are the success/error messages issued during the
>> upgrade process:
>>
>> Running database upgrade script: derby/400-to-401-migration.sql
>> -- No database changes in version 401, but we did record the new 
>> version number
>>
>> - in the roller.log file the last message is again that Roller wants to
>> upgrade the database, but there is no error message:
>>
>> INFO  2009-01-17 15:13:31,563 DatabaseProvider:successMessage - 
>> SUCCESS: Got parameters. Using configuration type JNDI_NAME
>> INFO  2009-01-17 15:13:31,566 DatabaseProvider:successMessage - -- 
>> Using JNDI datasource name: java:comp/env/jdbc/rollerdb
>> INFO  2009-01-17 15:13:31,590 DatabaseProvider:successMessage - 
>> SUCCESS: located JNDI DataSource [java:comp/env/jdbc/rollerdb]
>> INFO  2009-01-17 15:13:35,416 RollerContext:contextInitialized -
>> --------------------------------------------------------------
>> Roller Weblogger startup INCOMPLETE, user interaction required
>> --------------------------------------------------------------
>> INFO  2009-01-17 15:13:35,418 
>> RollerContext:initializeSecurityFeatures - Remember Me enabled: true
>> INFO  2009-01-17 15:13:35,419 
>> RollerContext:initializeSecurityFeatures - Password Encryption 
>> Algorithm set to 'SHA'
>> INFO  2009-01-17 15:13:35,419 RollerContext:setupVelocity - 
>> Initializing Velocity
>> INFO  2009-01-17 15:13:36,155 IPBanFilter:init - INIT IPBanFilter
>> INFO  2009-01-17 15:13:36,176 RequestMappingFilter:init - Request 
>> mapping filter initialized, 1 mappers configured.
>> WARN  2009-01-17 15:13:36,826 Settings:getLocale - Settings: Could 
>> not parse struts.locale setting, substituting default VM locale
>> INFO  2009-01-17 15:13:37,346 PageServlet:init - Initializing 
>> PageServlet
>> INFO  2009-01-17 15:13:37,349 WeblogPageCache:<init> - 
>> {id=cache.weblogpage, enabled=true, timeout=3600, size=400}
>> INFO  2009-01-17 15:13:37,353 CacheManager:<clinit> - Cache Manager 
>> Initialized.
>> INFO  2009-01-17 15:13:37,354 CacheManager:<clinit> - Cache Factory = 
>> org.apache.roller.weblogger.util.cache.ExpiringLRUCacheFactoryImpl
>> INFO  2009-01-17 15:13:37,381 SiteWideCache:<init> - 
>> {id=cache.sitewide, enabled=true, timeout=1800, size=50}
>> INFO  2009-01-17 15:13:37,382 PageServlet:init - Referrer processing 
>> enabled = true
>> INFO  2009-01-17 15:13:37,386 FeedServlet:init - Initializing 
>> FeedServlet
>> INFO  2009-01-17 15:13:37,389 WeblogFeedCache:<init> - 
>> {id=cache.weblogfeed, enabled=true, timeout=3600, size=200}
>> INFO  2009-01-17 15:13:37,392 SearchServlet:init - Initializing 
>> SearchServlet
>> INFO  2009-01-17 15:13:37,400 ResourceServlet:init - Initializing 
>> ResourceServlet
>> INFO  2009-01-17 15:13:37,404 CommentServlet:init - Initializing 
>> CommentServlet
>> INFO  2009-01-17 15:13:37,434 CommentValidationManager:<init> - 
>> Configured CommentValidator: Blacklist Comment Validator / 
>> org.apache.roller.weblogger.ui.rendering.plugins.comments.BlacklistCommentValidator

>>
>> INFO  2009-01-17 15:13:37,436 CommentValidationManager:<init> - 
>> Configured CommentValidator: Excess Links Comment Validator / 
>> org.apache.roller.weblogger.ui.rendering.plugins.comments.ExcessLinksCommentValidator

>>
>> INFO  2009-01-17 15:13:37,438 CommentValidationManager:<init> - 
>> Configured CommentValidator: Excess Size Comment Validator / 
>> org.apache.roller.weblogger.ui.rendering.plugins.comments.ExcessSizeCommentValidator

>>
>> INFO  2009-01-17 15:13:37,439 CommentValidationManager:<init> - 
>> Configured 3 CommentValidators
>> INFO  2009-01-17 15:13:37,440 CommentServlet:init - Comment 
>> Throttling DISABLED
>> INFO  2009-01-17 15:13:37,443 CommentValidationManager:<init> - 
>> Configured CommentValidator: Blacklist Comment Validator / 
>> org.apache.roller.weblogger.ui.rendering.plugins.comments.BlacklistCommentValidator

>>
>> INFO  2009-01-17 15:13:37,443 CommentValidationManager:<init> - 
>> Configured CommentValidator: Excess Links Comment Validator / 
>> org.apache.roller.weblogger.ui.rendering.plugins.comments.ExcessLinksCommentValidator

>>
>> INFO  2009-01-17 15:13:37,444 CommentValidationManager:<init> - 
>> Configured CommentValidator: Excess Size Comment Validator / 
>> org.apache.roller.weblogger.ui.rendering.plugins.comments.ExcessSizeCommentValidator

>>
>> INFO  2009-01-17 15:13:37,444 CommentValidationManager:<init> - 
>> Configured 3 CommentValidators
>> INFO  2009-01-17 15:13:37,448 RSDServlet:init - Initializing RSDServlet
>> INFO  2009-01-17 15:13:37,451 PlanetFeedServlet:init - Initializing 
>> PlanetRssServlet
>> INFO  2009-01-17 15:13:37,454 PlanetCache:<init> - Planet cache = 
>> {id=cache.planet, enabled=true, timeout=1800, size=10}
>> INFO  2009-01-17 15:13:37,458 PreviewResourceServlet:init - 
>> Initializing PreviewResourceServlet
>> INFO  2009-01-17 15:13:37,461 PreviewThemeImageServlet:init - 
>> Initializing PreviewThemeImageServlet
>> INFO  2009-01-17 15:13:37,471 PreviewServlet:init - Initializing 
>> PreviewServlet
>> INFO  2009-01-17 15:15:15,468 DatabaseInstaller:upgradeDatabase - 
>> Database is old, beginning upgrade to version 401
>>
>> - these are the Roller-related messages from Glassfish's server.log:
>>
>> [#|2009-01-17T15:13:27.330+0100|FINE|sun-appserver9.1|javax.enterprise.resource.jdo.sqlstore|_ThreadID=16;_ThreadName=Thread-66;ClassName=com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl;MethodName=processApplication;deploy;roller;_RequestID=610d98ca-d6ab-4a9d-9ff2-342a9e7e18a0;|ejb.DeploymentEventListenerImpl.processingevent|#]

>>
>>
>> [#|2009-01-17T15:13:27.921+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=16;_ThreadName=Thread-66;|deployed

>> with moduleid = roller|#]
>>
>> [#|2009-01-17T15:13:28.814+0100|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=17;_ThreadName=Thread-65;|PWC1412:

>> WebModule[/r] ServletContext.log():Loading Spring root 
>> WebApplicationContext|#]
>>
>> [#|2009-01-17T15:13:31.250+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=Thread-65;|Roller

>> Weblogger: Successfully loaded custom properties file from classpath|#]
>>
>> I can see no error messages...
>>
>> To exclude the possibility that my Roller 4.0 database is somehow
>> corrupted, I also tried this:
>>
>> - deployed binary Roller 4.0 distribution with a new Derby database
>> - let Roller initialize the database tables, created a user, a blog and
>> a test entry
>> - deployed binary Roller 4.0.1 distribution, confirmed to upgrade the
>> database tables, and got the same error message as with my real database
>>
>> It looks to me like there is a general issue. Did anybody successfully
>> upgrade a Roller 4.0 installation in Glassfish with a Derby database to
>> Roller 4.0.1?
>>
>> Regards
>> Stephan
>>
>>   
>
>


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