Hi, On Sun, Jul 15, 2012 at 11:56 AM, coldserenity <rmunt...@softserveinc.com>wrote:
> Hi again, > > I have tried upgrading with the most recent release (4.1.3) and seem to > have a successful upgrade. > However there are issues in the logs (full stack attached [1]), which > make > me think there may be issues with the installation in the end. > > So my DB name is "xwiki_utf8_innodb_413". > > 1. 2012-07-14 23:56:15,392 [http://localhost/xwiki/bin/view/Main/WebHome > ] > WARN o.i.c.InfinispanConfiguration - ISPN000139: Infinispan configuration > schema could not be resolved locally nor fetched from URL. Local path=null, > schema path=schema/infinispan-config-5.1.xsd, schema > URL=http://www.infinispan.org/schemas/infinispan-config-5.1.xsd > I believe schema will be created automatically and this error can be > ignored, correct? > > 2. 2012-07-14 23:56:18,251 [http://localhost/xwiki/bin/view/Main/WebHome > ] > WARN h.R40001XWIKI7540DataMigration - Skipping database [xwiki] because it > uses a custom annotation class. Comments and anotations will remain > separated > This one is really weird because my db name is "xwiki_utf8_innodb_413" > (and as you'll see in the logs the rest of upgrade items refer to name > "xwiki_utf8_innodb_413" As far as I know, the main wiki will always be named "xwiki", no matter what actual database it is stored in (as specified in xwiki.cfg), so that might be the reason for the string "xwiki" being used instead of "xwiki_utf8_innodb_413". > . More over I'd really like to use merged comments > and annotations feature. > What should I fix in order to merge comments and annotations? > This could be a bug [1] that I have unfortunately introduced in 4.1.3 while trying to fix a corner case. There are 2 possibilities here: 1) You are indeed using a different annotation class for your existing annotations. Please check that in AnnotationsCode.AnnotationConfig you are using AnnotationCode.AnnotationClass as the current annotation class. If you are using a custom annotation class, the migration can not migrate custom annotations to comments and it can not execute, so you`ll have to use annotations and comments separately. 2) You are using HSQLDB. In 4.1.3, the way the "fix" was implemented is not working as intended for HSQLDB. It seems to work ok for MySQL though. It should be properly fixed for 4.1.4 or 4.2. Please hang tight for the next release. In this case, you might need to force the migration to run "again" (since last time it was skipped unintentionally) by lowering the database version back from 40001 to 40000 (previous version). Thanks, Eduard ---------- [1] http://jira.xwiki.org/browse/XWIKI-8062 > > 3. Then there's a bunch of info messages following next pattern > 2012-07-14 23:56:35,897 [http://localhost/xwiki/bin/view/Main/WebHome] > INFO > c.x.x.s.m.liquibase - Change set > liquibase.xml::R40000-000::sdumitriu failed, this error could be safely > ignored until something worse happens. Error: Error executing SQL ALTER > TABLE `$table_name$` DROP FOREIGN KEY `$FOREING_KEY_ID$`: Error on rename > of > './xwiki_utf8_innodb_413/$table_name$' to > './xwiki_utf8_innodb_413/#sql2-dfb-c08f' (errno: 152) > Where $table_name$ = {xwikiintegers, xwikistrings, xwikifloats, > xwikidoubles, xwikilistitems, xwikidates, xwikilargestrings, xwikilists, > xwikilongs, feeds_feedentrytags, feeds_aggregatorurlgroups} > Even though the message says "safely ignore", I tend not to trust it when I > see words "failed" and "something worse might happen", because in IT it > does > happen. > So again how can I fix this message? > > 4. And finally there's a bunch of deprecated methods used in the end: > method [com.xpn.xwiki.api.Util.parseInt] in unknown namespace@68,26 > getter [com.xpn.xwiki.api.Util.getArrayList] in unknown namespace@788,35 > method [com.xpn.xwiki.api.Util.parseInt] in unknown namespace@68,26 > getter [com.xpn.xwiki.api.Util.getArrayList] in unknown namespace@788,35 > Can they be fixed? > > 5. Also one more question: after this serious migration, is there a way > to > find out that my database and application has a valid state? (I mean some > other way than just start using and find an error after 2-3 weeks of adding > pages, to find out that it wont be able to either downgrade or fix the > issue) > > > [1] Full upgrade logs attached: > http://xwiki.475771.n2.nabble.com/file/n7580357/db-migration.log > db-migration.log<http://xwiki.475771.n2.nabble.com/file/n7580357/db-migration.log%0Adb-migration.log> > > -- > View this message in context: > http://xwiki.475771.n2.nabble.com/Possible-upgrade-3-5-1-to-4-0-issue-tp7528896p7580357.html > Sent from the XWiki- Users mailing list archive at Nabble.com. > _______________________________________________ > users mailing list > users@xwiki.org > http://lists.xwiki.org/mailman/listinfo/users > _______________________________________________ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
