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,
Reporter: santosh gadkari
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.
