Foros de discusión
Sitemap.xml - error 500
Michele Giacobazzi, modificado hace 10 años.
Sitemap.xml - error 500
Junior Member Mensajes: 40 Fecha de incorporación: 9/09/11 Mensajes recientes
Hello. I'm using Liferay 6.1.1 and I'm hosting different portal instance on the same tomcat intallation.
If I look for the sitemap.xml file (ex: liferay.com/sitemap.xml) a server error is issued:
If i access the sitemap from the control panel the URL is:
https://www.example.com/sitemap.xml?groupId=10143&privateLayout=false
How can i avoid the server error on the call? I can accept a 404, but not a 500!
If I look for the sitemap.xml file (ex: liferay.com/sitemap.xml) a server error is issued:
17:34:12,839 ERROR [ajp-bio-8009-exec-97020][status_jsp:665] com.liferay.portal.LayoutSetVirtualHostException: Virtual host is associated with company 12149
com.liferay.portal.LayoutSetVirtualHostException: Virtual host is associated with company 12149
at com.liferay.portal.service.impl.LayoutSetLocalServiceImpl.getLayoutSet(LayoutSetLocalServiceImpl.java:210)
If i access the sitemap from the control panel the URL is:
https://www.example.com/sitemap.xml?groupId=10143&privateLayout=false
How can i avoid the server error on the call? I can accept a 404, but not a 500!
Andrew Jardine, modificado hace 8 años.
RE: Sitemap.xml - error 500
Liferay Legend Mensajes: 2416 Fecha de incorporación: 22/12/10 Mensajes recientes
Old thread but for future reference:
https://issues.liferay.com/browse/LPS-29716
It seems like as long as the groupId is in the request though it works so if you can't upgrade, either a proxy pass that does this, or a StrutsHook (for the path /layouts_admin/sitemap) could be used to patch the issue.
Also refer to this commit: https://github.com/liferay/liferay-portal/commit/a8e305adc52280a4b14bd5743d966948cc92bff8
https://issues.liferay.com/browse/LPS-29716
It seems like as long as the groupId is in the request though it works so if you can't upgrade, either a proxy pass that does this, or a StrutsHook (for the path /layouts_admin/sitemap) could be used to patch the issue.
Also refer to this commit: https://github.com/liferay/liferay-portal/commit/a8e305adc52280a4b14bd5743d966948cc92bff8