[jboss-jira] [JBoss JIRA] Closed: (JBRULES-1650) Repository get locked when redeploying the drools-jbrms.war file on weblogic

Michael Neale (JIRA) jira-events at lists.jboss.org
Tue Oct 28 01:43:15 EDT 2008


     [ https://jira.jboss.org/jira/browse/JBRULES-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Neale closed JBRULES-1650.
----------------------------------

    Resolution: Won't Fix


A restart is required due to the way jackrabbit works at this time, unfortunately. Due to all the caching that goes on, a deploy of the BRMS war on the fly is not recommended without a restart (the same applies to most apps).

> Repository get locked when redeploying the drools-jbrms.war file on weblogic
> ----------------------------------------------------------------------------
>
>                 Key: JBRULES-1650
>                 URL: https://jira.jboss.org/jira/browse/JBRULES-1650
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: weblogic, jdk1.5, oracle,
>            Reporter: santosh gadkari
>            Assignee: Michael Neale
>             Fix For: 5.0.0.M3
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> Redeploying the drools-jbrms.war on weblogic when someone is accessing  the application throws "javax.jcr.RepositoryException" Exception.
> Steps to reproduce;
> 1) Deploy drools-jbrms.war file
> 2) login to the application and perform some operation
> 3) Redepoy drools-jbrms.war again
> 4) depoy fails with javax.jcr.RepositoryException. Please find the its stack trace as below.
> Obly after rebooting the server we could able to deploy the application. We don't want server restarts, as we are high profile finance company. restarting at critical time may be penalty of us.
> Exception Trace : 
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list