Import Layouts fails for JRockit / JDK7

Description

Calling LayoutLocalServiceUtil.importLayouts fails with a NullPointerException.
Also Importing Layouts from a Prototype by the Backend (for example create Organization Layoutset) fails.

StackTrace

Steps to reproduce it:
In Weblogic (10.3.5) + JRockit (R28) OR in Sun JDK 7 can be reproduced following these steps:
In LAR Import/export
1.- Navigate to Control panel > Site pages
2.- Export the pages for the site
3.- Import them again

OR in Site creation from a Site template

1.- In a clean database schema (there could be a the marge-fail-count property set to 4 in the databse which could not make the exception not to appear)
1.- Navigate to control panel > Sites
2.- Click on Add and create a site from the Intranet template
3.- Go to control panel > Site pages

Expected behaviour:
There should appear 4 pages

Observed behaviour:
None pages appear and the exception is written to the log.

Environment

With JRockit: Welogic 10.3.5 + Oracle JRockit(R) (build R28.2.2-7-148152-1.6.0_29-20111221-2104-linux-x86_64, compiled mode)

Attachments

1

Activity

Show:

Paul Piao September 10, 2012 at 8:08 PM
Edited

PASSED Manual Testing following the steps in the description.

Reproduce on:
WebLogic 10.3.5 + Oracle JRockit. JDK 7.0. Portal 6.2.x GIT ID: da31ad5fbae2424b85673732caec36146fc9c4ed.

Import jar throw error message to console, and none pages appear.

Fixed on:
WebLogic 10.3.5 + Oracle JRockit. JDK 7.0. Portal 6.2.x GIT ID: cbf85cbae56b1341a550f6e5f0d9f44b82c538ea.
WebLogic 10.3.5 + Oracle JRockit. JDK 7.0. Portal 6.1.x EE GIT ID: 79afed965e35b5a8e44d89e38952cdf5334c1ffb.

The console doesn't throw error messages and 4 pages appear.

Michael Saechang July 18, 2012 at 5:26 PM

Committed on:
Portal 6.1.x CE GIT ID: 025cccd8d858095bd0f33b3241fef55fe59a9e4b.
Portal 6.2.x GIT ID: b0385e9dfc505eb2c07b5b46c55b872d480cb730.

Gus Heck July 18, 2012 at 11:25 AM

You probably want to test to see if you've fixed the other Jdk7 bugs listed here:

Sergio Sánchez July 17, 2012 at 2:10 AM
Edited

If in the lib folder the xstream.jar is deleted and xstream-1.4.2.jar a new exception is written to the log. This exception appears even in Tomcat+JDK6+Liferay trunk.

It seems that thae JAR for the XmlPull API is needed (kxml2-2.3.0.jar). It is distributed with the xstream package.

Sergio Sánchez July 13, 2012 at 5:35 AM

Hi Gus, it's marked that way for an internal procedure.

Fixed

Details

Assignee

Reporter

Branch Version/s

6.1.x
6.0.x

Backported to Branch

Committed

Git Pull Request

Components

Priority

Zendesk Support

Created January 7, 2012 at 7:06 AM
Updated June 24, 2023 at 3:40 PM
Resolved March 3, 2015 at 2:30 PM
Loading...