Document library NoSuchFileException after migration Liferay 5.2.3 to 6.0.5

[13年前 に thomas hyrien によって更新されました。]

Hi,

I have just migrate from 5.2.3 to 6.0.5
I have a problem with the document library. When I open a file I have a documentlibrary.NoSuchFileException.

In the logs I can see that the URL of the file is wrong. The "." have been replaced by ",".

09:48:12,338 INFO [PortalImpl:3812] Current URL /c/document_library/get_file?uuid=4c50e2c0-f8e4-4e5e-a5a8-0f14b11ac080&groupId=10136 generates exception: C:\dev\essais\liferay-portal-5.2.3\data\document_library\10112\10192\1\1,0
09:48:12,338 INFO [PortalImpl:3827] com.liferay.documentlibrary.NoSuchFileException: C:\dev\essais\liferay-portal-5.2.3\data\document_library\10112\10192\1\1,0
com.liferay.documentlibrary.NoSuchFileException: C:\dev\essais\liferay-portal-5.2.3\data\document_library\10112\10192\1\1,0

The last repository is "1,0" and would be "1.0"

Anyone has an idea?

[13年前 に thomas hyrien によって更新されました。]

In the table 'dlfileentry' in my MySQL database, if I update version from '1,0' to '1.0' it works.
Is there a solution to solve this problem during migration ?

[13年前 に Dennis Greiffenberg によって更新されました。]

Hi Thomas,

I'm also trying to upgrade from 5.2.3 to 6.0.5 on MySQL and I'm facing severe errors during the transition. Well, to be honest, the transition completely fails due to the following error:

Starting Liferay Portal Community Edition 6.0.5 CE (Bunyan / Build 6005 / August 16, 2010)
13:10:00,865 ERROR [JDBCExceptionReporter:101] Table 'tpliferay6.lock_' doesn't exist
13:10:01,974 INFO  [BaseDB:399] Database does not support case sensitive queries
13:10:01,982 INFO  [UpgradeProcess:108] Upgrading com.liferay.portal.upgrade.UpgradeProcess_6_0_0
13:10:01,983 INFO  [UpgradeProcess:108] Upgrading com.liferay.portal.upgrade.v6_0_0.UpgradeSchema
13:10:03,500 INFO  [UpgradeProcess:108] Upgrading com.liferay.portal.upgrade.v6_0_0.UpgradeAsset
13:10:04,044 ERROR [MainServlet:202] com.liferay.portal.kernel.events.ActionException: com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'tagId' in 'field list'
com.liferay.portal.kernel.events.ActionException: com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'tagId' in 'field list'
        at com.liferay.portal.events.StartupAction.run(StartupAction.java:53)    
        at com.liferay.portal.servlet.MainServlet.processStartupEvents(MainServlet.java:1166)
        at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:199)
        at javax.servlet.GenericServlet.init(GenericServlet.java:212)
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
        at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
        at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4187)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4496)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:637)
        at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:563)
        at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:498)
        at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
        at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
        at org.apache.catalina.core.StandardService.start(StandardService.java:519)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
        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 org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

Tomcat stops after that. If I restart tomcat I get a duplicate key error on the table "dlfileentry".

Did you run into similar errors or does that scenario not sound familiar at all to you?

Any help is greatly appreciated.

/Dennis

[13年前 に thomas hyrien によって更新されました。]

Hi Dennis,

Sorry but I didn't have your error during the transition.
Do you use the portal-legacy-5.2.properties file ?

[13年前 に Nicolas Grué によって更新されました。]

Hi all,

An issue is opened on JIRA for this.
http://issues.liferay.com/browse/LPS-13281

It seems to be related to the tags properties.

Please do not hesitate to add some comments there.

(EDIT: Dennis, I just noticed you were the original reporter, so forget my comment.)

[13年前 に Nicolas Grué によって更新されました。]

As for the original post from Thomas, it may be linked to this:
http://issues.liferay.com/browse/LPS-11363

the obvious workaround would be to call after the upgrade:
update DLFileEntry set version = replace(version, ',', '.');

but it's probably not that simple, because of frenchs settings on the jvm...

Since I'll probably hit the same problem, I'll bring you some news soon.

[13年前 に Tobias S. Käfer によって更新されました。]

The root of this issue is this one:
http://issues.liferay.com/browse/LPS-12109

I came across this one during my upgrading tests from 5.2.3 to 6.0.5

As you can see this is fixed in the trunk.

[11年前 に Hitoshi Ozawa によって更新されました。]

I think the default in 5.x was to store data in database whild 6.x stores them in file system.