Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

6.1 - Reindex.on.upgrade fails to work

Description

Upgrade does not (re)index automatically even though portal.properties says it should.

Steps taken:
1. Configure portal-ext.properties to use postgres instead of mysql
2. Start tomcat 6.0.29 + postgres 9 (version 8.4 or 9.0 doesn't matter) for Liferay 6.0.6
3. Verify that Liferay uploads correctly
4. Go to the Control Panel> Organization
5. Add an Organization with a blank page
6. Stop Liferay 6.0.6
7. In the bundle tomcat 7.0.21 + postgres 9.0, configure portal-ext.properties to use the same DB as 6.0.6 and the liferay.home folder points to the same 6.0.6's
8. Start Liferay 6.1.x
9. Go to the Control Panel> Users and Organizations
10. The Organization does not display there.
11. Go to the Control Panel> Sites
12. Because in 6.1.x, Org and Sites have the same back end, Organizations should display there.
13. The expectation is that the user should find the Organization in 3 places: Sites, Users and Organizations, and Liferay.com (Sites) drop down (top left on the panel.)
14. Instead, the user must manually re-index on Control Panel> Server Administration

Environment

Tomcat 7.0.21 + Postgresql 9.0. 6.1.x Revision 89037.

Activity

Show:

Mark Jin June 18, 2012 at 2:40 AM

FAILED Manual Testing following the steps in the description.

Fixed on:
Tomcat 6.0 + MySQL 5. Portal 6.0.x GIT ID: cd9d66c5d0e64ae2616c3e111690d23f856dd964.
Tomcat 7.0 + MySQL 5. Portal 6.1.x CE GIT ID: 46eef720b35516daf06d08b55cd2c7220211706d.
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 94f8f37a1fe7df90fe4603c7e072ffe80f96c05d.

Failed on:
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 895007003b1534d7a606823ebeeea1f9ad74d4fb.

Tomcat throw
09:37:31,820 ERROR [LuceneIndexer:135] Error encountered while reindexing
com.liferay.portal.kernel.search.SearchException: com.liferay.portal.kernel.exception.SystemExceptio
n: com.liferay.portal.kernel.dao.orm.ORMException: com.liferay.portal.kernel.dao.orm.ORMException: o
rg.hibernate.exception.SQLGrammarException: could not execute query
at com.liferay.portal.kernel.search.BaseIndexer.reindex(BaseIndexer.java:370)
at com.liferay.portal.search.lucene.LuceneIndexer.reindex(LuceneIndexer.java:158)
at com.liferay.portal.search.lucene.LuceneIndexer.doReIndex(LuceneIndexer.java:124)
at com.liferay.portal.search.lucene.LuceneIndexer.reindex(LuceneIndexer.java:64)
at com.liferay.portal.search.lucene.LuceneIndexer.run(LuceneIndexer.java:72)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask._runTask(ThreadPoolExe
cutor.java:673)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask.run(ThreadPoolExecutor
.java:584)
at java.lang.Thread.run(Thread.java:662)

Rubén Martínez Candela February 24, 2012 at 4:48 AM

I reproduced the same exception on:
Tomcat 7.0.22 + MySQL 5.0.77 6.1.x

Im upgrading from LR 6.0.6 to 6.1.0 and i follow the steps from here: http://www.liferay.com/es/documentation/liferay-portal/6.1/user-guide/-/ai/upgrading-lifer-5

Mark Jin September 21, 2011 at 10:22 PM
Edited

FAILED Manual Testing following steps in description.

Reproduced on:
Tomcat 7.0.21 + MySQL 5.5. 6.1.x Revision 89010.

Fixed:
Tomcat 7.0.21 + MySQL 5.5. 6.1.x Revision 89513.

Failed on:
Tomcat 6.0.33 + MySQL 5.5. 6.0.x Revision 89513.
Tomcat throw error message.

05:36:12,634 ERROR [MainServlet:201] com.liferay.portal.kernel.events.ActionException: com.liferay.p
ortal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: java.io.S
treamCorruptedException: invalid stream header: BB656430
com.liferay.portal.kernel.events.ActionException: com.liferay.portal.kernel.upgrade.UpgradeException
: com.liferay.portal.kernel.upgrade.UpgradeException: java.io.StreamCorruptedException: invalid stre
am header: BB656430
at com.liferay.portal.events.StartupAction.run(StartupAction.java:57)
at com.liferay.portal.servlet.MainServlet.processStartupEvents(MainServlet.java:1193)
at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:198)

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Branch Version/s

6.1.x
6.0.x

Backported to Branch

Committed

Fix Priority

4

Git Pull Request

Components

Fix versions

Affects versions

Priority

Zendesk Support

Created September 14, 2011 at 12:58 PM
Updated June 24, 2023 at 3:45 PM
Resolved July 8, 2012 at 6:04 PM