OOB 6.2 EE : Facing issue while Export page and Site setting.

[Sagar A Vyas, modificado 10 Anos atrás.]

Hi Team,

There is no customization , its just oob.

We are seeing following error on our development server [Linux os] of Liferay 6.2 EE edition and wanted to reach out to you to see if there is any recommended solution or patch for it. As we are in the process of procuring the support.

Liferay edition: liferay-portal-6.2.10.1-ee-ga1
Server: Amazon Linux AMI
Database: MySQL 5.6.13
Screen Message: Your request completed successfully.
Error log: Catalina.out logs java.lang.NullPointerException every time an operation is done on the control panel.
Functions leading to error:
1. LAR file export for the site using control panel
2. Virtual host configuration under Site settings page
3. Other control panel functions may be behaving the same but have not checked.

Exception trace:

5:16:26,832 ERROR [http-bio-8080-exec-19][IncludeTag:129] Current URL /group/control_panel/manage?p_p_auth=pC7mC1Vk&p_p_id=156&p_p_lifecycle=0&p_p_state=pop_up&p_p_mode=view&doAsGroupId=10614&refererPlid=11381&controlPanelCategory=current_site.content&_156_rootNodeName=Public+Pages&_156_groupId=10614&_156_cmd=export&_156_struts_action=%2Fgroup_pages%2Fexport_layouts&_156_liveGroupId=10614&_156_privateLayout=false generates exception: null
java.lang.NullPointerException
        at com.liferay.portal.model.impl.PortletImpl.getPortletDataHandlerInstance(PortletImpl.java:1306)
        at com.liferay.portal.lar.LayoutExporter.getDataSiteLevelPortlets(LayoutExporter.java:122)
        at org.apache.jsp.html.portlet.layouts_005fadmin.export_005flayouts_jsp._jspService(export_005flayouts_jsp.java:1665)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
        at com.liferay.portal.servlet.DirectRequestDispatcher.include(DirectRequestDispatcher.java:57)
        at com.liferay.portal.servlet.ClassLoaderRequestDispatcherWrapper.doDispatch(ClassLoaderRequestDispatcherWrapper.java:78)
        at com.liferay.portal.servlet.ClassLoaderRequestDispatcherWrapper.include(ClassLoaderRequestDispatcherWrapper.java:53)
        at com.liferay.taglib.util.IncludeTag.include(IncludeTag.java:295)
        at com.liferay.taglib.util.IncludeTag.doInclude(IncludeTag.java:192)
        at com.liferay.taglib.util.IncludeTag.doEndTag(IncludeTag.java:83)
        at org.apache.jsp.html.common.themes.portlet_jsp._jspService(portlet_jsp.java:3141)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
        at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

Is this known issue ? any pointer would be appreciated.

Thanks,
Sagar Vyas

[Eric COQUELIN, modificado 10 Anos atrás.]

I have exactly the same issue. Can't understand why.

Looking forward some responses.

Thank you

[Sagar A Vyas, modificado 10 Anos atrás.]

Hello Eric,

I guess by increasing the size of heap on server resolve our problem.

You can try with the same,hope you will get it right way.

Thanks,
Sagar Vyas

[Roshan Qureshi, modificado 10 Anos atrás.]

Hi Sagar,

Can you provide your memory settings here?

Thanks,
Roshan Qureshi

[Sagar A Vyas, modificado 10 Anos atrás.]

Roshan Qureshi:

Hi Sagar,

Can you provide your memory settings here?

Thanks,
Roshan Qureshi

Roshan,

Actually problem was not related memory in this case,

We have multiple webapps are deployed on server when you export it will keep a track on page id plus portlet id on that page.

When we are trying to import lar any how it was trying to look pid with given portlet because of that it was throwing error.

I will give you detail if you require.

Thanks,
Sagar Vyas

[srujana k, modificado 9 Anos atrás.]

Sagar A Vyas:

Roshan,

Actually problem was not related memory in this case,

We have multiple webapps are deployed on server when you export it will keep a track on page id plus portlet id on that page.

When we are trying to import lar any how it was trying to look pid with given portlet because of that it was throwing error.

I will give you detail if you require.

Thanks,
Sagar Vyas

Hi Sagar,
Could you please share the details, I've the same issue.

Thank you.

[Nrupay N Shah, modificado 9 Anos atrás.]

Hi Sagar,

Will you please share some details regarding solution of it as I am facing same issue?
It will be very appriciated.

Thanks & Regards,
Nrupay Shah

[Sagar A Vyas, modificado 9 Anos atrás.]

Nrupay N Shah:

Hi Sagar,

Will you please share some details regarding solution of it as I am facing same issue?
It will be very appriciated.

Thanks & Regards,
Nrupay Shah

Hi Nrupay,

As of now I know only following

We have multiple webapps are deployed on server when you export it will keep a track on page id plus portlet id on that page.

When we are trying to import lar any how it was trying to look pid with given portlet because of that it was throwing error.

But if you want more information , certainly I will try to get it from my team and get back to you.

Thanks,
Sagar Vyas

[Hemen Punjani, modificado 8 Anos atrás.]

Hi,

I had faced same issue on dev server and found the solution :

Error clearly shows there is some issue with some portlet instantiate.
It was crashing at method getPortletDataHandlerPortlets in LayoutExporter.java, there is no debug/info statements in this method.

1. Create Groovy script (PFA-Groovy Script) and find out which portlet is having problem in instantiate and undeploy that portlet. (In my case that portlet was not in use, if its in use then we should undeploy and deploy it again).
2. Reindex and restart the server.

Then It works fine.

Thanks,
Hemen

[Anoop Shukla, modificado 9 Anos atrás.]

Sagar A Vyas:

Roshan Qureshi:

Hi Sagar,

Can you provide your memory settings here?

Thanks,
Roshan Qureshi

Roshan,

Actually problem was not related memory in this case,

We have multiple webapps are deployed on server when you export it will keep a track on page id plus portlet id on that page.

When we are trying to import lar any how it was trying to look pid with given portlet because of that it was throwing error.

I will give you detail if you require.

Thanks,
Sagar Vyas

Hi Sagar,

Can you please share the solution to this issue? For me this is happening only on Linux server. On windows the same code runs fine.

I am getting the issue while deleting a group from Control Panel.

10:50:59,270 ERROR [MO ACL Synchronizer Thread][MOAuth:206] Error occured deleting user group testGroup
java.lang.NullPointerException
at com.liferay.portal.model.impl.PortletImpl.getPortletDataHandlerInstance(PortletImpl.java:1306)
at com.liferay.portal.service.impl.GroupLocalServiceImpl.deletePortletData(GroupLocalServiceImpl.java:3677)
at com.liferay.portal.service.impl.GroupLocalServiceImpl.deleteGroup(GroupLocalServiceImpl.java:851)
at sun.reflect.GeneratedMethodAccessor1043.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:115)
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.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:175)
at com.sun.proxy.$Proxy29.deleteGroup(Unknown Source)
at com.liferay.portal.service.impl.UserGroupLocalServiceImpl.deleteUserGroup(UserGroupLocalServiceImpl.java:381)
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:601)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:115)
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.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:175)
at com.sun.proxy.$Proxy107.deleteUserGroup(Unknown Source)
at com.liferay.portal.service.impl.UserGroupLocalServiceImpl.deleteUserGroup(UserGroupLocalServiceImpl.java:343)
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:601)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:115)
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.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:175)
at com.sun.proxy.$Proxy107.deleteUserGroup(Unknown Source)
at com.liferay.portal.service.UserGroupLocalServiceUtil.deleteUserGroup(UserGroupLocalServiceUtil.java:80)