Fórum
Problems after upgrading to 6.2
Juha Anttila, modificado 10 Anos atrás.
Problems after upgrading to 6.2
New Member Postagens: 14 Data de Entrada: 19/10/12 Postagens Recentes
Hello,
I upgraded Liferay from version 5.2.3 -> 6.0.6 -> 6.1.2 -> 6.2. Two problems have come up :
1) If I try to configure LDAP connection i get
2) I have set one of my pages to use themeX and if i try to set another page to use themeY, I get :
Any help would be appreciated!
I upgraded Liferay from version 5.2.3 -> 6.0.6 -> 6.1.2 -> 6.2. Two problems have come up :
1) If I try to configure LDAP connection i get
09:18:44,374 INFO [stdout] (http--0.0.0.0-8080-5) 09:18:44,372 WARN [http--0.0.0.0-8080-5][PortletRequestProcessor:157] This URL can only be invoked using POST: /group/control_panel/manage?p_auth=qcz3mOVK&p_p_id=130&p_p_lifecycle=1&p_p_state=maximized&p_p_mode=view&refererPlid=21246&controlPanelCategory=configuration&_130_struts_action=%2Fportal_settings%2Fedit_company
09:18:44,382 WARN [org.apache.struts.action.RequestProcessor] (http--0.0.0.0-8080-5) Unhandled Exception thrown: class com.liferay.portal.security.auth.PrincipalException
09:18:44,385 INFO [stdout] (http--0.0.0.0-8080-5) 09:18:44,384 ERROR [http--0.0.0.0-8080-5][render_portlet_jsp:132] null
09:18:44,385 INFO [stdout] (http--0.0.0.0-8080-5) com.liferay.portal.security.auth.PrincipalException: /group/control_panel/manage?p_auth=qcz3mOVK&p_p_id=130&p_p_lifecycle=1&p_p_state=maximized&p_p_mode=view&refererPlid=21246&controlPanelCategory=configuration&_130_struts_action=%2Fportal_settings%2Fedit_company
09:18:44,386 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portal.struts.PortletRequestProcessor.process(PortletRequestProcessor.java:162)
09:18:44,386 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portlet.StrutsPortlet.processAction(StrutsPortlet.java:216)
09:18:44,386 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portlet.FilterChainImpl.doFilter(FilterChainImpl.java:71)
09:18:44,387 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portal.kernel.portlet.PortletFilterUtil.doFilter(PortletFilterUtil.java:48)
09:18:44,387 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:618)
09:18:44,387 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portlet.InvokerPortletImpl.invokeAction(InvokerPortletImpl.java:649)
09:18:44,388 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portlet.InvokerPortletImpl.processAction(InvokerPortletImpl.java:312)
09:18:44,388 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portlet.PortletContainerImpl._doProcessAction(PortletContainerImpl.java:402)
09:18:44,388 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portlet.PortletContainerImpl.processAction(PortletContainerImpl.java:110)
09:18:44,389 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portlet.SecurityPortletContainerWrapper.processAction(SecurityPortletContainerWrapper.java:109)
09:18:44,389 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portlet.RestrictPortletContainerWrapper.processAction(RestrictPortletContainerWrapper.java:75)
09:18:44,390 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portal.kernel.portlet.PortletContainerUtil.processAction(PortletContainerUtil.java:115)
09:18:44,390 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portal.action.LayoutAction.processLayout(LayoutAction.java:356)
09:18:44,390 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portal.action.LayoutAction.doExecute(LayoutAction.java:178)
09:18:44,391 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portal.action.LayoutAction.execute(LayoutAction.java:79)
09:18:44,391 INFO [stdout] (http--0.0.0.0-8080-5) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
09:18:44,391 INFO [stdout] (http--0.0.0.0-8080-5) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
09:18:44,392 INFO [stdout] (http--0.0.0.0-8080-5) at com.liferay.portal.struts.PortalRequestProcessor.process(PortalRequestProcessor.java:173)
09:18:44,392 INFO [stdout] (http--0.0.0.0-8080-5) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
09:18:44,393 INFO [stdout] (http--0.0.0.0-8080-5) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
09:19:55,813 INFO [org.jabsorb.serializer.impl.BeanSerializer] (http--0.0.0.0-8080-4) analyzing com.liferay.portal.kernel.util.TreeNodeView
09:20:15,008 INFO [org.apache.jackrabbit.core.TransientRepository] (http--0.0.0.0-8080-5) Session closed
2) I have set one of my pages to use themeX and if i try to set another page to use themeY, I get :
09:20:15,052 WARN [org.hibernate.util.JDBCExceptionReporter] (http--0.0.0.0-8080-5) SQL Error: 1062, SQLState: 23000
09:20:15,052 ERROR [org.hibernate.util.JDBCExceptionReporter] (http--0.0.0.0-8080-5) Duplicate entry '10102-0-' for key 'IX_BC2C4231'
09:20:15,058 INFO [stdout] (http--0.0.0.0-8080-5) 09:20:15,054 ERROR [http--0.0.0.0-8080-5][DefaultTransactionExecutor:93] Application exception overridden by commit exception
09:20:15,058 INFO [stdout] (http--0.0.0.0-8080-5) org.springframework.dao.DataIntegrityViolationException: Could not execute JDBC batch update; SQL [update Layout set uuid_=?, groupId=?, companyId=?, userId=?, userName=?, createDate=?, modifiedDate=?, privateLayout=?, layoutId=?, parentLayoutId=?, name=?, title=?, description=?, keywords=?, robots=?, type_=?, typeSettings=?, hidden_=?, friendlyURL=?, iconImage=?, iconImageId=?, themeId=?, colorSchemeId=?, wapThemeId=?, wapColorSchemeId=?, css=?, priority=?, layoutPrototypeUuid=?, layoutPrototypeLinkEnabled=?, sourcePrototypeLayoutUuid=? where plid=?]; constraint [null]; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch updateAny help would be appreciated!
Juha Anttila, modificado 10 Anos atrás.
RE: Problems after upgrading to 6.2
New Member Postagens: 14 Data de Entrada: 19/10/12 Postagens Recentes
The solution to the LDAP problem was found from this forum post. On my laptop (localhost) it didn't matter what was in the virtual host field, but the Liferay we run at our remote test server this needed to be set correctly.
Juha Anttila, modificado 10 Anos atrás.
RE: Problems after upgrading to 6.2
New Member Postagens: 14 Data de Entrada: 19/10/12 Postagens Recentes
For the theme problem I took an SQL dump from the lportal database and searched for the key in error message. It's found in Layout table :
and my boss knew that the "10102-0-" in error message meant that the friendlyURL was null in the key. It seems that this theme problem can be worked around by giving the page that needs explicitly set theme a friendly url.
I'm not still sure if this error means that something went wrong in the upgrade process!?!
CREATE TABLE `Layout` (
`plid` bigint(20) NOT NULL,
`groupId` bigint(20) DEFAULT NULL,
`companyId` bigint(20) DEFAULT NULL,
`privateLayout` tinyint(4) DEFAULT NULL,
`layoutId` bigint(20) DEFAULT NULL,
`parentLayoutId` bigint(20) DEFAULT NULL,
`name` longtext,
`title` longtext,
`description` longtext,
`type_` varchar(75) DEFAULT NULL,
`typeSettings` longtext,
`hidden_` tinyint(4) DEFAULT NULL,
`friendlyURL` varchar(100) DEFAULT NULL,
`iconImage` tinyint(4) DEFAULT NULL,
`iconImageId` bigint(20) DEFAULT NULL,
`themeId` varchar(75) DEFAULT NULL,
`colorSchemeId` varchar(75) DEFAULT NULL,
`wapThemeId` varchar(75) DEFAULT NULL,
`wapColorSchemeId` varchar(75) DEFAULT NULL,
`css` longtext,
`priority` int(11) DEFAULT NULL,
`uuid_` varchar(75) DEFAULT NULL,
`createDate` datetime DEFAULT NULL,
`modifiedDate` datetime DEFAULT NULL,
`keywords` longtext,
`robots` longtext,
`layoutPrototypeUuid` varchar(75) DEFAULT NULL,
`layoutPrototypeLinkEnabled` tinyint(4) DEFAULT NULL,
`sourcePrototypeLayoutUuid` varchar(75) DEFAULT NULL,
`userId` bigint(20) DEFAULT NULL,
`userName` varchar(75) DEFAULT NULL,
PRIMARY KEY (`plid`),
UNIQUE KEY `IX_BC2C4231` (`groupId`,`privateLayout`,`friendlyURL`),
UNIQUE KEY `IX_7162C27C` (`groupId`,`privateLayout`,`layoutId`),
UNIQUE KEY `IX_E118C537` (`uuid_`,`groupId`,`privateLayout`),
KEY `IX_C7FBC998` (`companyId`),
KEY `IX_C099D61A` (`groupId`),
KEY `IX_705F5AA3` (`groupId`,`privateLayout`),
KEY `IX_6DE88B06` (`groupId`,`privateLayout`,`parentLayoutId`),
KEY `IX_23922F7D` (`iconImageId`),
KEY `IX_1A1B61D2` (`groupId`,`privateLayout`,`type_`),
KEY `IX_D0822724` (`uuid_`),
KEY `IX_8CE8C0D9` (`groupId`,`privateLayout`,`sourcePrototypeLayoutUuid`),
KEY `IX_B529BFD3` (`layoutPrototypeUuid`),
KEY `IX_39A18ECC` (`sourcePrototypeLayoutUuid`),
KEY `IX_2CE4BE84` (`uuid_`,`companyId`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE utf8mb4_general_ci; and my boss knew that the "10102-0-" in error message meant that the friendlyURL was null in the key. It seems that this theme problem can be worked around by giving the page that needs explicitly set theme a friendly url.
I'm not still sure if this error means that something went wrong in the upgrade process!?!