[RESOLVED] upgrade liferay 6.0.5 vers 6.1.0

[benjamin garcia, modifié il y a 11 années.]

Bonjour,

Je suis en train de passer liferay en 6.1.1 depuis une version 6.0.5.
Voyant des erreurs lors de la migration, je suis revenu en arrière afin de procéder en deux étapes :

• 6.0.5 vers 6.1.0
• 6.1.0 vers 6.1.1

Malheureusement, dès la première migration je me retrouve avec cette erreur :

08:23:00,719 ERROR [pool-2-thread-1][PortalInstances:468] com.liferay.portal.kernel.events.ActionException: com.liferay.portlet.dynamicdatamapping.StructureNameException
com.liferay.portal.kernel.events.ActionException: com.liferay.portlet.dynamicdatamapping.StructureNameException
	at com.liferay.portal.events.AddDefaultDocumentLibraryStructuresAction.run(AddDefaultDocumentLibraryStructuresAction.java:64)
	at com.liferay.portal.events.AddDefaultDataAction.run(AddDefaultDataAction.java:30)
	at com.liferay.portal.events.EventsProcessorImpl.processEvent(EventsProcessorImpl.java:106)
	at com.liferay.portal.events.EventsProcessorImpl.process(EventsProcessorImpl.java:58)
	at com.liferay.portal.events.EventsProcessorUtil.process(EventsProcessorUtil.java:53)
	at com.liferay.portal.util.PortalInstances._initCompany(PortalInstances.java:462)
	at com.liferay.portal.util.PortalInstances.initCompany(PortalInstances.java:92)
	at com.liferay.portal.servlet.MainServlet.initCompanies(MainServlet.java:798)
	at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:355)
	at javax.servlet.GenericServlet.init(GenericServlet.java:160)
	at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
	at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
	at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5015)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5302)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
	at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1099)
	at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1621)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: com.liferay.portlet.dynamicdatamapping.StructureNameException
	at com.liferay.portlet.dynamicdatamapping.service.impl.DDMStructureLocalServiceImpl.validateLanguages(DDMStructureLocalServiceImpl.java:681)
	at com.liferay.portlet.dynamicdatamapping.service.impl.DDMStructureLocalServiceImpl.validate(DDMStructureLocalServiceImpl.java:648)
	at com.liferay.portlet.dynamicdatamapping.service.impl.DDMStructureLocalServiceImpl.validate(DDMStructureLocalServiceImpl.java:624)
	at com.liferay.portlet.dynamicdatamapping.service.impl.DDMStructureLocalServiceImpl.addStructure(DDMStructureLocalServiceImpl.java:92)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:122)
	at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:71)
	at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
	at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:211)
	at $Proxy200.addStructure(Unknown Source)
	at com.liferay.portlet.dynamicdatamapping.service.DDMStructureLocalServiceUtil.addStructure(DDMStructureLocalServiceUtil.java:296)
	at com.liferay.portal.events.AddDefaultDocumentLibraryStructuresAction.addDLRawMetadataStructures(AddDefaultDocumentLibraryStructuresAction.java:190)
	at com.liferay.portal.events.AddDefaultDocumentLibraryStructuresAction.doRun(AddDefaultDocumentLibraryStructuresAction.java:276)
	at com.liferay.portal.events.AddDefaultDocumentLibraryStructuresAction.run(AddDefaultDocumentLibraryStructuresAction.java:61)
        ... 26 more

Hormis cette erreur, les themes et hook fonctionnent mais pas les portlets. Quelqu'un aurait-il une idée?

Merci d'avance,

Benjamin

[Juan Gonzalez P, modifié il y a 11 années.]

It's this issue: LPS-29349 Startup exception when en_US not present:

Seems it's not yet resolved properly.

[benjamin garcia, modifié il y a 11 années.]

Ok, thank you.

So, If I understand my portlets problems are not the same point.

Thank you.

I put it resolve when LPS-29349 will be closed.

Benjamin

[Abhed Dekavadiya, modifié il y a 11 années.]

Hi Benjamin,

Did you resolved this issue? I am also facing the same issue.
I tried adding 'en_US' in locale, but still the same error.

kind regards,
Abhed

[Juan Gonzalez P, modifié il y a 11 années.]

Unless you patch your Liferay version issue will remain.

You can download a patched version here:

https://www.lcepatchers.org/nightly-build

After that you can save your locale in portal configuration and issue should be solved.

[Abhed Dekavadiya, modifié il y a 11 années.]

Hi Juan,

Thanks for your reply. I recently joined the CE patchers community, though haven't contributed anything yet.
From the link: https://www.lcepatchers.org/downloads, I saw your name as author of bug fixes. I downloaded the tomcat-bundle with patches for listed bugs.
I really appreciate the effort spent on helping the community !

I need your suggestion here, "Is this patch-fixed tomcat bundle authorized by Liferay?". I am not doubting anything here, but wondering if I can use this for my client's production environment ?
In other case, I would prefer to apply patch on liferay's tomcat bundle for the only bugs which I am facing right now.
How can I view the modified files for code fix for defect LPS-29349 ? I think that Liferay JIRA is not integrated with git, I couldn't find any link in fish-eye options.

Thanks in advance!

regards,
Abhed

[Juan Gonzalez P, modifié il y a 11 années.]

Hi Adhed,

Abhed Dekavadiya:

I need your suggestion here, "Is this patch-fixed tomcat bundle authorized by Liferay?".

No, it isn't. This is only one of other great community initiatives. But is made by Liferay freaks with many experiencie in this .

Abhed Dekavadiya:

I am not doubting anything here, but wondering if I can use this for my client's production environment ?

Well, I am using this in production since september, and no problem. Don't know about anybody complaining about an issue neither. But, perhaps you'd like to test something.

Abhed Dekavadiya:

In other case, I would prefer to apply patch on liferay's tomcat bundle for the only bugs which I am facing right now.
How can I view the modified files for code fix for defect LPS-29349 ? I think that Liferay JIRA is not integrated with git, I couldn't find any link in fish-eye options.
Abhed

Here you are:

https://github.com/brianchandotcom/liferay-portal/commit/d33de6e67e1146372bbde84e7cac7d262037b378

https://github.com/brianchandotcom/liferay-portal/commit/93ae637ba9ba933a31aba721f886f5238c818399

[Abhed Dekavadiya, modifié il y a 11 années.]

Thanks Juan, Now I am also using the patched version on production.

[Roshan Qureshi, modifié il y a 10 années.]

Hi Everybody,

I had a similar issue. Following are the steps worked for me to resolve the issue.

http://roshanqureshi.blogspot.com/2014/03/structurenameexception-while-importing.html

Hope this will help..!

Regards,
Roshan Qureshi