Uploaded image for project: 'eXo-JCR'
  1. eXo-JCR
  2. EXOJCR-781

LockManagerImpl should call InitialContextInitializer.recall

    Details

      Description

      When I tried to use LockManagerImpl in the configuration of the new Tenant

      <lock-manager>
      <time-out>15m</time-out>
      <persister class="org.exoplatform.services.jcr.impl.core.lock.FileSystemLockPersister">
      <properties>
      <property name="path" value="${gatein.jcr.data.dir}/${gatein.tenant.repository.name}/lock/system" />
      </properties>
      </persister>
      </lock-manager>

      The exception occur
      javax.jcr.RepositoryException: JDNI exception. javax.naming.NameNotFoundException: Name jdbcjcr_portal is not bound in this Context: JDNI exception. javax.naming.NameNotFoundException: Name jdbcjcr_portal is not bound in this Context
      at org.exoplatform.services.jcr.impl.config.RepositoryServiceConfigurationImpl.retain(RepositoryServiceConfigurationImpl.java:207)
      at org.exoplatform.services.jcr.ext.backup.impl.JobRepositoryRestore.restore(JobRepositoryRestore.java:182)
      at org.exoplatform.services.jcr.ext.backup.impl.JobRepositoryRestore.run(JobRepositoryRestore.java:276)
      Caused by: org.exoplatform.services.jcr.config.RepositoryConfigurationException: JDNI exception. javax.naming.NameNotFoundException: Name jdbcjcr_portal is not bound in this Context
      at org.exoplatform.services.jcr.impl.config.JDBCConfigurationPersister.write(JDBCConfigurationPersister.java:388)
      at org.exoplatform.services.jcr.impl.config.RepositoryServiceConfigurationImpl.retain(RepositoryServiceConfigurationImpl.java:189)
      ... 2 more
      Caused by: javax.naming.NameNotFoundException: Name jdbcjcr_portal is not bound in this Context
      at org.apache.naming.NamingContext.lookup(NamingContext.java:770)
      at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
      at org.apache.naming.SelectorContext.lookup(SelectorContext.java:152)
      at javax.naming.InitialContext.lookup(InitialContext.java:392)
      at org.exoplatform.services.jcr.impl.config.JDBCConfigurationPersister.openConnection(JDBCConfigurationPersister.java:199)
      at org.exoplatform.services.jcr.impl.config.JDBCConfigurationPersister.write(JDBCConfigurationPersister.java:318)
      ... 3 more
      org.exoplatform.services.jcr.config.RepositoryConfigurationException: JDNI exception. javax.naming.NameNotFoundException: Name jdbcjcr_portal is not bound in this Context
      at org.exoplatform.services.jcr.impl.config.JDBCConfigurationPersister.write(JDBCConfigurationPersister.java:388)
      at org.exoplatform.services.jcr.impl.config.RepositoryServiceConfigurationImpl.retain(RepositoryServiceConfigurationImpl.java:189)
      at org.exoplatform.services.jcr.ext.backup.impl.JobRepositoryRestore.restore(JobRepositoryRestore.java:182)
      at org.exoplatform.services.jcr.ext.backup.impl.JobRepositoryRestore.run(JobRepositoryRestore.java:276)
      Caused by: javax.naming.NameNotFoundException: Name jdbcjcr_portal is not bound in this Context
      at org.apache.naming.NamingContext.lookup(NamingContext.java:770)
      at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
      at org.apache.naming.SelectorContext.lookup(SelectorContext.java:152)
      at javax.naming.InitialContext.lookup(InitialContext.java:392)
      at org.exoplatform.services.jcr.impl.config.JDBCConfigurationPersister.openConnection(JDBCConfigurationPersister.java:199)
      at org.exoplatform.services.jcr.impl.config.JDBCConfigurationPersister.write(JDBCConfigurationPersister.java:318)
      ... 3 more

      Deeper study showed: that would prevent a similar situation org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl class in constructor call context.recall() method.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                sergiykarpenko Sergiy Karpenko (Inactive)
                Reporter:
                skabashnyuk Sergey Kabashnyuk
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Time Spent - 3 days, 6 hours Remaining Estimate - 2 hours
                  2h
                  Logged:
                  Time Spent - 3 days, 6 hours Remaining Estimate - 2 hours
                  3d 6h