Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1314950808.1213869945855.JavaMail.jira@brutus>
Date: Thu, 19 Jun 2008 03:05:45 -0700 (PDT)
From: "Alexander Klimetschek (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-1656) Repository get locked when redeploying
 the brms war file on weblogic.
In-Reply-To: <1291999058.1213865145328.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Klimetschek resolved JCR-1656.
----------------------------------------

    Resolution: Invalid

You need to shutdown the repository before redeploying the repository code. The repository lock is a Java lock that stays open until the VM is restarted or when the repository is shutdown properly. Looks like the Repository instance is still running when you redeploy. See TransientRepository.shutdown(): http://jackrabbit.apache.org/api/1.4/org/apache/jackrabbit/core/TransientRepository.html

Resolving issue as invalid.

(BTW: Please try to give the issue a name that describes the Jackrabbit issue and not your application's name or details. Thanks!)

> Repository get locked when redeploying the brms war file on weblogic.
> ---------------------------------------------------------------------
>
>                 Key: JCR-1656
>                 URL: https://issues.apache.org/jira/browse/JCR-1656
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core
>         Environment: Windows, weblogic, jdk 1.5, oracle 10g
>            Reporter: santosh gadkari
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Most of the time when we need to redeploy the brms web application on weblogic, we are expriencing the below exception. 
> The worst part of this is that, only after restarting the server this get disappear. We don't want server restarts, as we are high profile finance company.
> restarting at critical time may be penalty of us.
> weblogic.application.ModuleException:
>         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:894)
>         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:336)
>         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
>         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
>         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
>         Truncated. see log file for complete stacktrace
> javax.jcr.RepositoryException: The repository home at C:\Local\weblogic92\user_projects\domains\base_domain\repository appears to be in use since the file at C:\Local\weblogic92\user_projects\domains\base_domain\repository\.lock is locked by another process.
>         at org.apache.jackrabbit.core.RepositoryImpl.acquireRepositoryLock(RepositoryImpl.java:423)
>         at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:236)
>         at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:584)
>         at org.apache.jackrabbit.core.TransientRepository$2.getRepository(TransientRepository.java:245)
>         at org.apache.jackrabbit.core.TransientRepository.startRepository(TransientRepository.java:265)
>         Truncated. see log file for complete stacktrace
> >
> Please suggest suitable solution to avoid this exception. 
> We tried to use OracleFileSystem for storing repository but not able to get rid of this problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.