Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Vasu Kumar Piduru
Liferay migration from 6.0.6 to 6.1.2 GA3 - Document library issue
March 17, 2014 9:29 AM
Answer

Vasu Kumar Piduru

Rank: New Member

Posts: 23

Join Date: October 5, 2009

Recent Posts

Hi All,

The migration from 6.0.6 to 6.1.2 was successful, after migration the old documents from 6.0.6 are available in the document library portlet but they are not downloadable. I have check in the data/document_library folder for the entries, could not find any entries copied from the old (6.0.6) to new.

finally we are not able to download the old documents from 6.0.6.

Any help on this or similar issues please point me.
Jens Hamisch
RE: Liferay migration from 6.0.6 to 6.1.2 GA3 - Document library issue
March 19, 2014 2:58 PM
Answer

Jens Hamisch

Rank: Junior Member

Posts: 26

Join Date: June 7, 2012

Recent Posts

Hi,


I also seem to be running into a document_library migration problem.
I'm trying to migrate from 6.1.0 CE GA1 to 6.1.2 CE GA3.
I've got liferay running in a JBoss environment.

The migration fails and the JBoss application server becomes stopped.
In the logfiles, the following is displayed:


 119:20:45,607 INFO  [stdout] (MSC service thread 1-4) 19:20:45,607 INFO  [MSC service thread 1-4][VerifyProcess:55] Verifying com.liferay.portal.verify.VerifyDocumentLibrary
 219:20:45,679 INFO  [org.apache.jackrabbit.core.config.RepositoryConfig] (MSC service thread 1-4) Creating repository directory /var/jboss/standalone/data/jackrabbit/home
 319:20:45,712 WARN  [org.apache.jackrabbit.core.config.ConfigurationErrorHandler] (MSC service thread 1-4) Warning parsing the configuration at line 41 using system id file:/var/jboss/standalone/data/jackrabbit/repository.xml: org.xml.sax.SAXParseException: The content of element type "Workspace" must match "(FileSystem,PersistenceManager,SearchIndex?,ISMLocking?,WorkspaceSecurity?,Import?)".
 419:20:45,712 WARN  [org.apache.jackrabbit.core.config.ConfigurationErrorHandler] (MSC service thread 1-4) Warning parsing the configuration at line 61 using system id file:/var/jboss/standalone/data/jackrabbit/repository.xml: org.xml.sax.SAXParseException: The content of element type "Versioning" must match "(FileSystem,PersistenceManager,ISMLocking?)".
 519:20:45,895 INFO  [org.apache.jackrabbit.core.RepositoryImpl] (MSC service thread 1-4) Starting repository...
 619:20:45,906 WARN  [org.apache.jackrabbit.core.util.db.ConnectionFactory] (MSC service thread 1-4) Failed to guess validation query for URL jdbc:postgresql://localhost:5432/jcr
 719:20:46,103 ERROR [org.apache.jackrabbit.core.util.db.DbUtility] (MSC service thread 1-4) failed to close Statement
 819:20:46,103 ERROR [org.apache.jackrabbit.core.util.db.DbUtility] (MSC service thread 1-4)        Reason: Already closed
 919:20:46,103 ERROR [org.apache.jackrabbit.core.util.db.DbUtility] (MSC service thread 1-4)    State/Code: null/0
1019:20:46,104 ERROR [org.apache.jackrabbit.core.util.db.DbUtility] (MSC service thread 1-4) failed to close Connection
1119:20:46,104 ERROR [org.apache.jackrabbit.core.util.db.DbUtility] (MSC service thread 1-4)        Reason: Connection is closed.
1219:20:46,104 ERROR [org.apache.jackrabbit.core.util.db.DbUtility] (MSC service thread 1-4)    State/Code: null/0
1319:20:46,185 INFO  [org.apache.jackrabbit.core.journal.DatabaseJournal] (MSC service thread 1-4) Initialized local revision to 7646
1419:20:46,185 INFO  [org.apache.jackrabbit.core.journal.DatabaseJournal] (MSC service thread 1-4) Cluster revision janitor thread not started
1519:20:46,185 INFO  [org.apache.jackrabbit.core.journal.DatabaseJournal] (MSC service thread 1-4) DatabaseJournal initialized.
1619:20:46,297 INFO  [org.apache.jackrabbit.core.RepositoryImpl] (MSC service thread 1-4) initializing workspace 'liferay'...
1719:20:46,421 INFO  [org.apache.jackrabbit.core.RepositoryImpl] (MSC service thread 1-4) workspace 'liferay' initialized
1819:20:46,455 INFO  [org.apache.jackrabbit.core.RepositoryImpl] (MSC service thread 1-4) Repository started
1919:20:46,455 INFO  [org.apache.jackrabbit.core.TransientRepository] (MSC service thread 1-4) Transient repository initialized
2019:20:46,459 INFO  [org.apache.jackrabbit.core.security.simple.SimpleSecurityManager] (MSC service thread 1-4) init: using Repository LoginModule configuration for Jackrabbit
2119:20:46,463 INFO  [org.apache.jackrabbit.core.RepositoryImpl] (MSC service thread 1-4) SecurityManager = class org.apache.jackrabbit.core.security.simple.SimpleSecurityManager
2219:20:46,499 INFO  [org.apache.jackrabbit.core.TransientRepository] (MSC service thread 1-4) Session opened
2319:20:46,615 INFO  [stdout] (MSC service thread 1-4) 19:20:46,612 ERROR [MSC service thread 1-4][MainServlet:217] com.liferay.portal.kernel.events.ActionException: com.liferay.portal.verify.VerifyException: com.liferay.portal.verify.VerifyException: com.liferay.portlet.documentlibrary.NoSuchFileException: {fileName=1, versionLabel=1.0}
2419:20:46,615 INFO  [stdout] (MSC service thread 1-4) com.liferay.portal.kernel.events.ActionException: com.liferay.portal.verify.VerifyException: com.liferay.portal.verify.VerifyException: com.liferay.portlet.documentlibrary.NoSuchFileException: {fileName=1, versionLabel=1.0}
2519:20:46,616 INFO  [stdout] (MSC service thread 1-4)    at com.liferay.portal.events.StartupAction.run(StartupAction.java:56)
2619:20:46,616 INFO  [stdout] (MSC service thread 1-4)    at com.liferay.portal.servlet.MainServlet.processStartupEvents(MainServlet.java:1300)
2719:20:46,616 INFO  [stdout] (MSC service thread 1-4)    at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:214)



There are 2 warnings regarding the repository.xml file, which seem to be misleading somehow.
The required parameters are available in my repository.xml, I'm only missing optional ones ... or do I misinterpret the "?" in the warning.
My repository.xml is as follows:

 1<!DOCTYPE Repository
 2              PUBLIC "-//The Apache Software Foundation//DTD Jackrabbit 2.0//EN"
 3              "http://jackrabbit.apache.org/dtd/repository-2.0.dtd">
 4
 5<Repository>
 6        <FileSystem class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
 7                <param name="driver" value="org.postgresql.Driver"/>
 8                <param name="url" value="jdbc:postgresql://localhost:5432/jcr" />
 9                <param name="user" value="xxxx" />
10                <param name="password" value="xxxx" />
11                <param name="schema" value="postgresql"/>
12                <param name="schemaObjectPrefix" value="J_R_FS_"/>
13        </FileSystem>
14
15        <Security appName="Jackrabbit">
16                <AccessManager class="org.apache.jackrabbit.core.security.simple.SimpleAccessManager" />
17                <LoginModule class="org.apache.jackrabbit.core.security.simple.SimpleLoginModule">
18                        <param name="anonymousId" value="anonymous" />
19                </LoginModule>
20        </Security>
21
22        <Workspaces rootPath="${rep.home}/workspaces" defaultWorkspace="liferay" />
23        <Workspace name="${wsp.name}">
24                <PersistenceManager class="org.apache.jackrabbit.core.persistence.pool.PostgreSQLPersistenceManager">
25                        <param name="driver" value="org.postgresql.Driver"/>
26                        <param name="url" value="jdbc:postgresql://localhost:5432/jcr" />
27                        <param name="user" value="xxxx" />
28                        <param name="password" value="xxxx" />
29                        <param name="schema" value="postgresql"/>
30                        <param name="schemaObjectPrefix" value="J_PM_${wsp.name}_" />
31                        <param name="externalBLOBs" value="false" />
32                </PersistenceManager>
33                <FileSystem class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
34                        <param name="driver" value="org.postgresql.Driver"/>
35                        <param name="url" value="jdbc:postgresql://localhost:5432/jcr" />
36                        <param name="user" value="xxxx" />
37                        <param name="password" value="xxxx" />
38                        <param name="schema" value="postgresql"/>
39                        <param name="schemaObjectPrefix" value="J_FS_${wsp.name}_"/>
40                </FileSystem>
41        </Workspace>
42
43        <Versioning rootPath="${rep.home}/version">
44                <PersistenceManager class="org.apache.jackrabbit.core.persistence.pool.PostgreSQLPersistenceManager">
45                        <param name="driver" value="org.postgresql.Driver"/>
46                        <param name="url" value="jdbc:postgresql://localhost:5432/jcr" />
47                        <param name="user" value="xxxx" />
48                        <param name="password" value="xxxx" />
49                        <param name="schema" value="postgresql"/>
50                        <param name="schemaObjectPrefix" value="J_V_PM_" />
51                        <param name="externalBLOBs" value="false" />
52                </PersistenceManager>
53                <FileSystem class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
54                        <param name="driver" value="org.postgresql.Driver"/>
55                        <param name="url" value="jdbc:postgresql://localhost:5432/jcr" />
56                        <param name="user" value="xxxx" />
57                        <param name="password" value="xxxx" />
58                        <param name="schema" value="postgresql"/>
59                        <param name="schemaObjectPrefix" value="J_V_FS_"/>
60                </FileSystem>
61        </Versioning>
62
63        <Cluster id="node_1" syncDelay="5">
64                <Journal class="org.apache.jackrabbit.core.journal.DatabaseJournal">
65                        <param name="revision" value="${rep.home}/revision"/>
66                        <param name="driver" value="org.postgresql.Driver"/>
67                        <param name="url" value="jdbc:postgresql://localhost:5432/jcr" />
68                        <param name="user" value="xxxx" />
69                        <param name="password" value="xxxx" />
70                        <param name="schema" value="postgresql"/>
71                        <param name="schemaObjectPrefix" value="J_C_"/>
72                </Journal>
73        </Cluster>
74</Repository>


The Jackrabbit repository is stored in a postgres database.
Would it be necessary to export and reimport the JCR?
If yes: Which version of jackrabbit is bundled with liferay 6.1.2 CE GA3?
(IMHO JCR 1.6.0 is bundled with 6.1.0 CE GA1).
I'm using the jackrabbit 2.0 DTD without being sure, that this is the correct version.
I'm doing so, because 2.0 is the highest version number of a file found in some of the jackrabbit JARS included in the liferay bundle.

Thanks
Jens
Jeffrey Paul Handa
RE: Liferay migration from 6.0.6 to 6.1.2 GA3 - Document library issue
March 19, 2014 4:08 PM
Answer

Jeffrey Paul Handa

LIFERAY STAFF

Rank: Expert

Posts: 464

Join Date: December 1, 2008

Recent Posts

Did you upgrade the system in place or move to a new server? The Liferay upgrade process won't migrate any files from one location to another so if you've changed the location of the Liferay home directory you'll need to manually move the data.
Jens Hamisch
RE: Liferay migration from 6.0.6 to 6.1.2 GA3 - Document library issue
March 19, 2014 6:51 PM
Answer

Jens Hamisch

Rank: Junior Member

Posts: 26

Join Date: June 7, 2012

Recent Posts

Hi Jeffrey,


I've moved to another server.
The entire document_library (jackrabbit) is stored in the database.

So I've copied over:
* The liferay database
* The liferay configuration (portal-ext.properties)
* The jackrabit database
* The jackrabbit repository configuration (repository.xml)

Databases were copied over using a SQL-Dump

On both servers the database is located on the same server and is accessed by liferay and jackrabbit using the localhost address.
Also users and passwords do match. So the configuration IMHO should be valid w/o a change for both of them.
However because of warnings during liferay startup I had to
* add the <DOCTYPE ... /> entity to repository.xml
* Cange class names in repository.xml:
<AccessManager class="org.apache.jackrabbit.core.security.simple.SimpleAccessManager" />
<LoginModule class="org.apache.jackrabbit.core.security.simple.SimpleLoginModule">

So the Jackrabbit version bundled with 6.1.2 definitely behaves different to 6.1.0.
Do I miss something else?

I've done the same procedure before for two 6.1.0 environments (development and productive server) which worked out fine.
The difference at this time is, that I'm trying to migrate from 6.1.0 to 6.1.2.

The following directory listing shows the data/jackrabbit directory:

1data/jackrabbit/
2data/jackrabbit/repository.xml
3data/jackrabbit/home
4data/jackrabbit/home/revision
5data/jackrabbit/home/workspaces
6data/jackrabbit/home/workspaces/liferay
7data/jackrabbit/home/workspaces/liferay/workspace.xml


It turns out, that the entire data/jackrabbit/home tree has been built by jackrabbit itsself when the JBoss/Liferay server started.
I've compared the workspace.xml file with the one on the running 6.1.0 server and found both of them to be identical.
Could it be the case, that the liferay migration procedure cannot handle jackrabbit repositories stored in a database?
May there have been some database scheme change, which need to be migrated?
Do I need to migrate the JCR manually?
If yes my approach would be to export the JCR to XML (using jackrabbit 1.6.0) and to reimport the XML to the database on the LR 6.1.2 server.
However in this case I'm afraight that matching the jackrabbit version bundled with LR 6.1.2 exactly will be essential.

Or does the error message finally point to something else but jackrabbit and I'm misleaded because it appears right after the JCR initialization?
(There might be a chance fo this also, because of the correct initialization of the workspace.xml and the success-entries in the log file)


Kind regards,
Jens
Jeffrey Paul Handa
RE: Liferay migration from 6.0.6 to 6.1.2 GA3 - Document library issue
March 20, 2014 9:16 AM
Answer

Jeffrey Paul Handa

LIFERAY STAFF

Rank: Expert

Posts: 464

Join Date: December 1, 2008

Recent Posts

Hi Jens,

I don't have much experience with Jackrabbit so I am afraid I can't provide too much help. However, to your question about Jackrabbit version, you can refer to the versions.html file that is included in Liferay bundles or in the source code (lib/versions.html). For 6.1.0 (https://github.com/liferay/liferay-portal/blob/6.1.0-ga1/lib/versions.html) it looks like it was v2.1.2 and for 6.1.2 (https://github.com/liferay/liferay-portal/blob/6.1.0-ga1/lib/versions.html) it looks like it was v2.1.6. As far as I know, I don't think there is any specific upgrade process for Jackrabbit.

One thing to try would be to not over the repository.xml from the old server but rather edit the new repository.xml with the correct db name and credentials and then try running the upgrade. Also, be sure that you restore the original 6.1.0 db whenever the upgrade fails and don't try to run the upgrade against a db from a failed upgrade attempt.
Jens Hamisch
RE: Liferay migration from 6.0.6 to 6.1.2 GA3 - Document library issue
March 20, 2014 9:37 AM
Answer

Jens Hamisch

Rank: Junior Member

Posts: 26

Join Date: June 7, 2012

Recent Posts

Hi Jeffrey,

thank you very much for the link to the version overviews.
I'll give both attempts a trial and let you know about the result.

Jens
Jens Hamisch
RE: Liferay migration from 6.0.6 to 6.1.2 GA3 - Document library issue
March 25, 2014 9:07 AM
Answer

Jens Hamisch

Rank: Junior Member

Posts: 26

Join Date: June 7, 2012

Recent Posts

Hi Jeffrey,


I tried it at no avail.

As a last trial I converted the database document store to a file system based one and started the upgrade again.
No chance.


I had a closer look at the error message:

 114:27:15,572 INFO  [org.apache.jackrabbit.core.security.simple.SimpleSecurityManager] (MSC service thread 1-11) init: using Repository LoginModule configuration for Jackrabbit
 214:27:15,575 INFO  [org.apache.jackrabbit.core.RepositoryImpl] (MSC service thread 1-11) SecurityManager = class org.apache.jackrabbit.core.security.simple.SimpleSecurityManager
 314:27:15,607 INFO  [org.apache.jackrabbit.core.TransientRepository] (MSC service thread 1-11) Session opened
 4
 5[b]I'd assume, that liferay has successfully opened the Jackrabbit session at this time.[/b]
 6
 714:27:15,695 INFO  [stdout] (MSC service thread 1-11) 14:27:15,692 ERROR [MSC service thread 1-11][MainServlet:217] com.liferay.portal.kernel.events.ActionException: com.liferay.portal.verify.VerifyException: com.liferay.portal.verify.VerifyException: com.liferay.portlet.documentlibrary.NoSuchFileException: {fileName=1, versionLabel=1.0}
 814:27:15,695 INFO  [stdout] (MSC service thread 1-11) com.liferay.portal.kernel.events.ActionException: com.liferay.portal.verify.VerifyException: com.liferay.portal.verify.VerifyException: com.liferay.portlet.documentlibrary.NoSuchFileException: {fileName=1, versionLabel=1.0}
 9
10[b]What is filename '1' version '1.0'[/b]
11
1214:27:15,696 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.events.StartupAction.run(StartupAction.java:56)
1314:27:15,696 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.servlet.MainServlet.processStartupEvents(MainServlet.java:1300)
1414:27:15,696 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:214)
1514:27:15,696 INFO  [stdout] (MSC service thread 1-11)   at javax.servlet.GenericServlet.init(GenericServlet.java:242)
1614:27:15,697 INFO  [stdout] (MSC service thread 1-11)   at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202)
1714:27:15,697 INFO  [stdout] (MSC service thread 1-11)   at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1102)
1814:27:15,697 INFO  [stdout] (MSC service thread 1-11)   at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3655)
1914:27:15,697 INFO  [stdout] (MSC service thread 1-11)   at org.apache.catalina.core.StandardContext.start(StandardContext.java:3873)
2014:27:15,697 INFO  [stdout] (MSC service thread 1-11)   at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90)
2114:27:15,698 INFO  [stdout] (MSC service thread 1-11)   at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
2214:27:15,698 INFO  [stdout] (MSC service thread 1-11)   at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
2314:27:15,698 INFO  [stdout] (MSC service thread 1-11)   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
2414:27:15,698 INFO  [stdout] (MSC service thread 1-11)   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
2514:27:15,699 INFO  [stdout] (MSC service thread 1-11)   at java.lang.Thread.run(Thread.java:662)
2614:27:15,699 INFO  [stdout] (MSC service thread 1-11) Caused by: com.liferay.portal.verify.VerifyException: com.liferay.portal.verify.VerifyException: com.liferay.portlet.documentlibrary.NoSuchFileException: {fileName=1, versionLabel=1.0}
2714:27:15,699 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:61)
2814:27:15,700 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyProcessUtil._verifyProcess(VerifyProcessUtil.java:110)
2914:27:15,700 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyProcessUtil._verifyProcess(VerifyProcessUtil.java:76)14:27:15,700 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyProcessUtil.verifyProcess(VerifyProcessUtil.java:46)
3014:27:15,700 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.events.StartupHelper.verifyProcess(StartupHelper.java:144)
3114:27:15,701 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.events.StartupHelperUtil.verifyProcess(StartupHelperUtil.java:65)
3214:27:15,701 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.tools.DBUpgrader.verify(DBUpgrader.java:246)
3314:27:15,701 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.events.StartupAction.doRun(StartupAction.java:161)
3414:27:15,701 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.events.StartupAction.run(StartupAction.java:50)
3514:27:15,701 INFO  [stdout] (MSC service thread 1-11)   ... 13 more
3614:27:15,702 INFO  [stdout] (MSC service thread 1-11) Caused by: com.liferay.portal.verify.VerifyException: com.liferay.portlet.documentlibrary.NoSuchFileException: {fileName=1, versionLabel=1.0}
3714:27:15,702 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:61)
3814:27:15,702 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:66)
3914:27:15,702 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyProcessSuite.doVerify(VerifyProcessSuite.java:41)
4014:27:15,703 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:58)
4114:27:15,703 INFO  [stdout] (MSC service thread 1-11)   ... 21 more
4214:27:15,703 INFO  [stdout] (MSC service thread 1-11) Caused by: com.liferay.portlet.documentlibrary.NoSuchFileException: {fileName=1, versionLabel=1.0}
4314:27:15,703 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portlet.documentlibrary.store.JCRStore.getFileContentNode(JCRStore.java:888)
4414:27:15,703 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portlet.documentlibrary.store.JCRStore.getFileAsStream(JCRStore.java:441)14:27:15,704 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portlet.documentlibrary.store.StoreProxyImpl.getFileAsStream(StoreProxyImpl.java:178)
4514:27:15,704 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portlet.documentlibrary.store.SafeFileNameStoreWrapper.getFileAsStream(SafeFileNameStoreWrapper.java:264)
4614:27:15,704 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portlet.documentlibrary.store.DLStoreImpl.getFileAsStream(DLStoreImpl.java:295)
4714:27:15,705 INFO  [stdout] (MSC service thread 1-11)   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
4814:27:15,705 INFO  [stdout] (MSC service thread 1-11)   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
4914:27:15,705 INFO  [stdout] (MSC service thread 1-11)   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)14:27:15,705 INFO  [stdout] (MSC service thread 1-11)   at java.lang.reflect.Method.invoke(Method.java:597)
5014:27:15,706 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.security.pacl.PortalSecurityManagerImpl$DoBeanLocatorImplPACL$1.invoke(PortalSecurityManagerImpl.java:475)
5114:27:15,706 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.security.pacl.PACLInvocationHandler.doInvoke(PACLInvocationHandler.java:62)
5214:27:15,706 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.security.pacl.PACLInvocationHandler.invoke(PACLInvocationHandler.java:51)
5314:27:15,706 INFO  [stdout] (MSC service thread 1-11)   at $Proxy611.getFileAsStream(Unknown Source)
5414:27:15,707 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portlet.documentlibrary.store.DLStoreUtil.getFileAsStream(DLStoreUtil.java:451)
5514:27:15,707 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portlet.documentlibrary.service.impl.DLFileEntryLocalServiceImpl.getFileAsStream(DLFileEntryLocalServiceImpl.java:821)
5614:27:15,707 INFO  [stdout] (MSC service thread 1-11)   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
5714:27:15,708 INFO  [stdout] (MSC service thread 1-11)   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
5814:27:15,708 INFO  [stdout] (MSC service thread 1-11)   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)14:27:15,708 INFO  [stdout] (MSC service thread 1-11)   at java.lang.reflect.Method.invoke(Method.java:597)
5914:27:15,708 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:117)
6014:27:15,709 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:218)
6114:27:15,709 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.security.pacl.PACLInvocationHandler.doInvoke(PACLInvocationHandler.java:62)
6214:27:15,709 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.security.pacl.PACLInvocationHandler.invoke(PACLInvocationHandler.java:51)
6314:27:15,709 INFO  [stdout] (MSC service thread 1-11)   at $Proxy307.getFileAsStream(Unknown Source)
6414:27:15,709 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portlet.documentlibrary.service.DLFileEntryLocalServiceUtil.getFileAsStream(DLFileEntryLocalServiceUtil.java:449)
6514:27:15,710 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyDocumentLibrary$1.performAction(VerifyDocumentLibrary.java:144)
6614:27:15,710 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.kernel.dao.orm.BaseActionableDynamicQuery.performActions(BaseActionableDynamicQuery.java:95)
6714:27:15,710 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.kernel.dao.orm.BaseActionableDynamicQuery.performActions(BaseActionableDynamicQuery.java:70)
6814:27:15,711 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyDocumentLibrary.checkFileEntryMimeTypes(VerifyDocumentLibrary.java:172)
6914:27:15,711 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyDocumentLibrary.checkMimeTypes(VerifyDocumentLibrary.java:221)
7014:27:15,711 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyDocumentLibrary.doVerify(VerifyDocumentLibrary.java:334)
7114:27:15,711 INFO  [stdout] (MSC service thread 1-11)   at com.liferay.portal.verify.VerifyProcess.verify(VerifyProcess.java:58)
7214:27:15,712 INFO  [stdout] (MSC service thread 1-11)   ... 24 more
7314:27:15,712 INFO  [stdout] (MSC service thread 1-11) Stopping the server due to unexpected startup errors
7414:27:15,721 INFO  [org.jboss.as.osgi] (MSC service thread 1-7) JBAS011942: Stopping OSGi Framework



I'm wondering about this filename '1' thing.
Maybe this is not a jackrabbit issue but some misconfiguration in the main liferay database?
To check this I had a look at it.

1lportal=> select * from dlfileentry where name = '1';
2                uuid_                 | fileentryid | groupid | companyid | userid | username | versionuserid | versionusername |       createdate        |      modifieddate       | repositoryid | folderid | name | extension | mimetype  |    title    | description | extrasettings | fileentrytypeid | version | size_ | readcount | smallimageid | largeimageid | custom1imageid | custom2imageid
3--------------------------------------+-------------+---------+-----------+--------+----------+---------------+-----------------+-------------------------+-------------------------+--------------+----------+------+-----------+-----------+-------------+-------------+---------------+-----------------+---------+-------+-----------+--------------+--------------+----------------+----------------
4 255d3469-b6b7-44e4-9361-753a13ee97a2 |       10488 |   10179 |     10153 |  10157 |          |         10157 |                 | 2012-03-15 16:58:05.419 | 2012-03-15 16:58:05.419 |        10179 |    10486 | 1    | png       | image/png | cell_bg.png |             |               |          0 | 1.0     |   305 |         0 |            0 |            0 |              0 |              0
5(1 row)


So there is a filename "1" ... also there are more filenames of this kind.

 1lportal=> select name,fileentryid,title from dlfileentry;
 2 name | fileentryid |                                  title
 3------+-------------+-------------------------------------------------------------------------
 4 1    |       10488 | cell_bg.png
 5 13   |       10629 | web_publishing.png
 6 14   |       10718 | cog_blue.png
 7 15   |       10728 | cog_light_blue.png
 8 16   |       10744 | cog_orange.png
 9 17   |       10752 | blogs_icon.png
10 18   |       10770 | cog_network_advertisement.png


cell_bg.png is not a impage I do remember. So it seems to be something related to liferay itsself or a 3rd party plugin.
I tried the following:

1. dropped and reinitialized the database 'lportal'
2. removed the dlfileentry record
delete from dlfileentry where uuid_ = '255d3469-b6b7-44e4-9361-753a13ee97a2';
3. and restarted the application server.

The result:

115:24:29,447 INFO  [stdout] (MSC service thread 1-1) 15:24:29,445 ERROR [MSC service thread 1-1][MainServlet:217] com.liferay.portal.kernel.events.ActionException: com.liferay.portal.verify.VerifyException: com.liferay.portal.verify.VerifyException: com.liferay.portlet.documentlibrary.NoSuchFileException: {fileName=[b]13[/b], versionLabel=1.0}
215:24:29,448 INFO  [stdout] (MSC service thread 1-1) com.liferay.portal.kernel.events.ActionException: com.liferay.portal.verify.VerifyException: com.liferay.portal.verify.VerifyException: com.liferay.portlet.documentlibrary.NoSuchFileException: {fileName=[b]13[/b], versionLabel=1.0}
315:24:29,448 INFO  [stdout] (MSC service thread 1-1)    at com.liferay.portal.events.StartupAction.run(StartupAction.java:56)


This finally prooves, that liferay seems to expect files stored in Jackrabbit, which seem not to be available. That may also be true for the running 6.1.0 portal, but doesn't harm, because those files are not used at all.
Another explanation may be, the UUIDs in between liferay and jackrabbit do not match at all.
IMHO since LR 6.1.0 was running for more than 2 years and multiple things where tried on this platform, there is reasonable chance to have "dead" entries in the database. However: Is there a way to check the databases? I've had a look at the UUIDs stored in the running liferay and jackrabbit databases and was not able to match anything ... even on the running platform and for files that are definitely available.

Any help would be warmly welcome.

Jens