jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "cheng (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCRSITE-38) The repository home appears to be already locked by the current process.
Date Thu, 02 Aug 2012 02:04:02 GMT
cheng created JCRSITE-38:

             Summary: The repository home appears to be already locked by the current process.
                 Key: JCRSITE-38
                 URL: https://issues.apache.org/jira/browse/JCRSITE-38
             Project: Jackrabbit Site
          Issue Type: Bug
          Components: site
    Affects Versions: parent 6
         Environment: redhat linux, jdk1.6,jackrabbit-2.4.2,liferay-6.0.5
            Reporter: cheng
             Fix For: parent 6

Caused by: javax.jcr.RepositoryException: The repository home /home/pcpprd/data/jackrabbit/home
appears to be already locked by the current process.
	at org.apache.jackrabbit.core.util.RepositoryLock.tryLock(RepositoryLock.java:183)
	at org.apache.jackrabbit.core.util.RepositoryLock.acquire(RepositoryLock.java:138)
	at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:302)
	at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:673)
	at org.apache.jackrabbit.core.TransientRepository$2.getRepository(TransientRepository.java:231)
	at org.apache.jackrabbit.core.TransientRepository.startRepository(TransientRepository.java:279)
	at org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:375)
	at com.liferay.portal.jcr.jackrabbit.JCRFactoryImpl.createSession(JCRFactoryImpl.java:67)
	at com.liferay.portal.jcr.JCRFactoryUtil.createSession(JCRFactoryUtil.java:43)
	at com.liferay.portal.jcr.JCRFactoryUtil.createSession(JCRFactoryUtil.java:47)
	at com.liferay.documentlibrary.util.JCRHook.getFileAsStream(JCRHook.java:457)

synchronized (identifier) {
            if (null != System.getProperty(identifier)) {
                // note that the newly acquired (redundant) file lock
                // is deliberately *not* released because this could
                // potentially cause, depending on the implementation,
                // the previously acquired lock(s) to be released
                // as well
                throw new RepositoryException(
                        "The repository home " + directory + " appears to be"
                        + " already locked by the current process.");
            } else {
                try {
                    System.setProperty(identifier, identifier);
                } catch (SecurityException e) {
                    LOG.warn("Unable to set system property: " + identifier, e);

but I already use jdk1.6, anyone can help me?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message