Cannot create XmlPullParser when importing LAR file in Weblogic Server 12c

• Type: Bug
• Status: Reopened
• Resolution: Unresolved
• Affects Version/s: 6.2.10 EE GA1
• Fix Version/s: None
• Component/s: Environments, Environments > App Servers, WCM, WCM > Export/Import
• Labels: None
• Fix Priority: 3
• Application Servers:
  Oracle Weblogic Server 12c (12.1.x)
• Similar Issues: Show 5 results ; ;

  LPS-45454	liferay on weblogic 12c does not start anymore
  LPS-20012	Cannot import .lar file when Categories is enabled
  LPS-39379	Cannot save changed pages settings when importing LAR files.
  LPS-27270	Cannot Import Community LAR when .png is placed in Document Library
  LPS-40196	Cannot click continue when Importing a site LAR in IE 10

Steps to reproduce
1. Install clean Liferay on Weblogic 12c
2. Login and export the default site's public pages
3. Create new site
4. Try to import the LAR form step 2

Expected behavior: import is successful
Actual behavior: import fails with:

Failed Details
An unexpected error occurred with the publication process. Please check your portal and publising configuration.
com.thoughtworks.xstream.io.StreamException: Cannot create XmlPullParser

The exception is

14:24:08,093 ERROR [liferay/background_task-1][BackgroundTaskMessageListener:133] Unable to execute background task
com.liferay.portal.kernel.lar.PortletDataException: com.thoughtworks.xstream.io.StreamException: Cannot create XmlPullParser
        at com.liferay.portal.kernel.lar.BasePortletDataHandler.importData(BasePortletDataHandler.java:337)
        at com.liferay.portal.lar.PortletImporter.importPortletData(PortletImporter.java:188)
        at com.liferay.portal.lar.PortletImporter.importPortletData(PortletImporter.java:1004)
        at com.liferay.portal.lar.PortletImporter.doImportPortletInfo(PortletImporter.java:565)
        at com.liferay.portal.lar.PortletImporter.importPortletInfo(PortletImporter.java:207)
        at com.liferay.portal.service.impl.LayoutLocalServiceImpl.importPortletInfo(LayoutLocalServiceImpl.java:1888)
        at com.liferay.portal.service.impl.LayoutLocalServiceImpl.importPortletInfo(LayoutLocalServiceImpl.java:1956)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:115)
        at com.liferay.portal.service.impl.LayoutLocalServiceVirtualLayoutsAdvice.invoke(LayoutLocalServiceVirtualLayoutsAdvice.java:179)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.service.impl.LayoutLocalServiceStagingAdvice.invoke(LayoutLocalServiceStagingAdvice.java:141)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.transaction.DefaultTransactionExecutor.execute(DefaultTransactionExecutor.java:62)
        at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:51)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:56)
        at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:111)
        at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:175)
        at com.sun.proxy.$Proxy102.importPortletInfo(Unknown Source)
        at com.liferay.portal.service.LayoutLocalServiceUtil.importPortletInfo(LayoutLocalServiceUtil.java:1385)
        at com.liferay.portal.lar.backgroundtask.PortletImportBackgroundTaskExecutor.execute(PortletImportBackgroundTaskExecutor.java:61)
        at com.liferay.portal.kernel.backgroundtask.SerialBackgroundTaskExecutor.execute(SerialBackgroundTaskExecutor.java:56)
        at com.liferay.portal.backgroundtask.messaging.BackgroundTaskMessageListener.doReceive(BackgroundTaskMessageListener.java:108)
        at com.liferay.portal.kernel.messaging.BaseMessageListener.receive(BaseMessageListener.java:26)
        at com.liferay.portal.kernel.messaging.InvokerMessageListener.receive(InvokerMessageListener.java:72)
        at com.liferay.portal.kernel.messaging.ParallelDestination$1.run(ParallelDestination.java:69)
        at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask._runTask(ThreadPoolExecutor.java:682)
        at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask.run(ThreadPoolExecutor.java:593)
        at java.lang.Thread.run(Thread.java:744)
Caused by: com.thoughtworks.xstream.io.StreamException: Cannot create XmlPullParser
        at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:56)
        at com.thoughtworks.xstream.XStream.fromXML(XStream.java:913)
        at com.thoughtworks.xstream.XStream.fromXML(XStream.java:904)
        at com.liferay.portal.lar.PortletDataContextImpl.fromXML(PortletDataContextImpl.java:798)
        at com.liferay.portal.lar.PortletDataContextImpl.getZipEntryAsObject(PortletDataContextImpl.java:1323)
        at com.liferay.portal.kernel.lar.StagedModelDataHandlerUtil._getStagedModel(StagedModelDataHandlerUtil.java:327)
        at com.liferay.portal.kernel.lar.StagedModelDataHandlerUtil.importStagedModel(StagedModelDataHandlerUtil.java:305)
        at com.liferay.portlet.journal.lar.JournalPortletDataHandler.doImportData(JournalPortletDataHandler.java:237)
        at com.liferay.portal.kernel.lar.BasePortletDataHandler.importData(BasePortletDataHandler.java:330)
        ... 50 more

[Michael Saechang]

Hi Milen, I have a question regarding your environments. Is it specific to your environment or is this not a environment specific issue?

[Milen Dyankov]

It was reproduced on 2 separate environments - my laptop and customer's server.
It does not happen on Tomcat and seams to be related to Weblogic's class loading.
A workaround is to change the Weblogic's classpath to load xstream.jar and xpp3.jar before weblogic.jar

[Milen Dyankov]

Got information that the issue is not reproducible on WebLogic 10.3.6 so it may be only related to WebLogic 12c

[Michael Saechang]

Thanks Milen for the information - the ticket has been updated and has been pushed into verified state.

[Mihai Trandafir]

Hello, Michael,
I have 2 environments both with Weblogic 12.1.2:
Windows 7 using either JDK6u45 or JDK7u45 - The problem is reproducible
Solaris 5.11 (11.1) using JDK6u45 - The problem is NOT reproducible
Thank you.

[Igor Spasic]

Currently can't test this as import UI is broken.

[Igor Spasic]

Can not reproduce on Windows 7 and Weblogic 12c.
Site gets imported.

[Laszlo Csontos]

Hi BZ,

I've just tested with 6.2.10 on Weblogic 12.1.1, PostgreSQL 9, Linux and wasn't able to reproduce this issue.

Installed patches:

Currently installed patches: administration-2-6210, asset-framework-1-6210, collaboration-2-6210, development-1-6210, document-management-2-6210, dynamic-data-lists-1-6210, platform-2-6210, search-2-6210, user-interface-2-6210, wcm-core-2-6210, web-content-2-6210

Cheers,
Laci

[Milen Dyankov]

This is what patching-tool info says on my machine where I can reproduce this:

Product information:
 * installation type: binary
 * build number: 6210
 * patching-tool version: 12
 * plugins: no plugins detected

Currently installed patches: administration-2-6210, asset-framework-1-6210, collaboration-2-6210, development-1-6210, document-management-2-6210, dynamic-data-lists-1-6210, platform-2-6210, search-2-6210, user-interface-2-6210, wcm-core-2-6210, web-content-2-6210

Available patches: development-1-6210, dynamic-data-lists-1-6210, platform-2-6210, document-management-2-6210, asset-framework-1-6210, web-content-2-6210, user-interface-2-6210, collaboration-2-6210, wcm-core-2-6210, administration-2-6210, search-2-6210

Detailed patch list: 
  [*I] development-1-6210 :: Installed; Will be installed. :: Built for Liferay
  [*I] dynamic-data-lists-1-6210 :: Installed; Will be installed. :: Built for Liferay
  [*I] platform-2-6210 :: Installed; Will be installed. :: Built for Liferay
  [*I] document-management-2-6210 :: Installed; Will be installed. :: Built for Liferay
  [*I] asset-framework-1-6210 :: Installed; Will be installed. :: Built for Liferay
  [*I] web-content-2-6210 :: Installed; Will be installed. :: Built for Liferay
  [*I] user-interface-2-6210 :: Installed; Will be installed. :: Built for Liferay
  [*I] collaboration-2-6210 :: Installed; Will be installed. :: Built for Liferay
  [*I] wcm-core-2-6210 :: Installed; Will be installed. :: Built for Liferay
  [*I] administration-2-6210 :: Installed; Will be installed. :: Built for Liferay
  [*I] search-2-6210 :: Installed; Will be installed. :: Built for Liferay

Hopefully this will help you figure out how it was fixed as it is definitively an issue on clean 6.2 EE SP1 downloaded from customer portal.

[Milen Dyankov]

Sorry for reopening but you stated you tested on WebLogic 12.1.1. Can you please check on 12.1.2 version as this seems to be the version that everyone confirming the issue is using.

[Adorjan Nagy]

Hi guys,

By adding the <package-name>org.xmlpull.*</package-name> into the <prefer-application-packages> block of the weblogic.xml, and redeploying the application, the pages are imported successfully in step #4.

Regards,
Adorjan