org.tmatesoft.sqljet.core.SqlJetException: CANTOPEN: error code is CANTOPEN

Atlassian JIRA | Kah Loun Foong [Atlassian] | 4 years ago
  1. 0

    h3.Steps to reproduce: # Create an new repository with the command 'svnadmin reponame' # Make sure that the file 'rep-cache.db' does not exist # Add the repository into FishEye Reindex will fail with the following error: {noformat} 2013-05-02 09:18:57,038 INFO [InitialPinger2 reponame] fisheye BaseRepositoryScanner-ping - processing dsagile-hmi 2013-05-02 09:18:57,038 DEBUG [InitialPinger2 reponame] fisheye SvnRepositoryTester-checkRepoSettings - Checking repository: reponame:file:///path/to/repo/svn/reponame/ 2013-05-02 09:18:57,038 DEBUG [SvnExecution1129 reponame] fisheye SvnTask-run - Executing info -r HEAD file:///path/to/repo/svn/reponame/@HEAD 2013-05-02 09:18:57,073 INFO [SvnExecution1129 reponame] svnkit-fsfs DefaultSVNDebugLogger-log - FSFS: CANTOPEN org.tmatesoft.sqljet.core.SqlJetException: CANTOPEN: error code is CANTOPEN at org.tmatesoft.sqljet.core.internal.fs.SqlJetFileSystem.open(SqlJetFileSystem.java:158) at org.tmatesoft.sqljet.core.internal.fs.SqlJetFileSystem.open(SqlJetFileSystem.java:185) at org.tmatesoft.sqljet.core.internal.pager.SqlJetPager.open(SqlJetPager.java:395) at org.tmatesoft.sqljet.core.internal.btree.SqlJetBtree.open(SqlJetBtree.java:325) {noformat} [~tom@atlassian.com]: {quote} Because svnkit can also write to svn repositories (although FishEye never uses it to) it tries to open the rep-cache.db file in read/write mode. If it doesn't exist it will usually create it. If it does exist but is read-only it silently falls back to opening it read-only, which is fine as FishEye never invokes any svnkit operations which require a write. In the case of an empty repository whose files are read only the rep-cache.db file doesn't exist and can't be created, which triggers that error. As soon as that file is created (by a commit) svnkit successfully opens the repository. {quote}

    Atlassian JIRA | 4 years ago | Kah Loun Foong [Atlassian]
    org.tmatesoft.sqljet.core.SqlJetException: CANTOPEN: error code is CANTOPEN
  2. 0

    h3.Steps to reproduce: # Create an new repository with the command 'svnadmin reponame' # Make sure that the file 'rep-cache.db' does not exist # Add the repository into FishEye Reindex will fail with the following error: {noformat} 2013-05-02 09:18:57,038 INFO [InitialPinger2 reponame] fisheye BaseRepositoryScanner-ping - processing dsagile-hmi 2013-05-02 09:18:57,038 DEBUG [InitialPinger2 reponame] fisheye SvnRepositoryTester-checkRepoSettings - Checking repository: reponame:file:///path/to/repo/svn/reponame/ 2013-05-02 09:18:57,038 DEBUG [SvnExecution1129 reponame] fisheye SvnTask-run - Executing info -r HEAD file:///path/to/repo/svn/reponame/@HEAD 2013-05-02 09:18:57,073 INFO [SvnExecution1129 reponame] svnkit-fsfs DefaultSVNDebugLogger-log - FSFS: CANTOPEN org.tmatesoft.sqljet.core.SqlJetException: CANTOPEN: error code is CANTOPEN at org.tmatesoft.sqljet.core.internal.fs.SqlJetFileSystem.open(SqlJetFileSystem.java:158) at org.tmatesoft.sqljet.core.internal.fs.SqlJetFileSystem.open(SqlJetFileSystem.java:185) at org.tmatesoft.sqljet.core.internal.pager.SqlJetPager.open(SqlJetPager.java:395) at org.tmatesoft.sqljet.core.internal.btree.SqlJetBtree.open(SqlJetBtree.java:325) {noformat} [~tom@atlassian.com]: {quote} Because svnkit can also write to svn repositories (although FishEye never uses it to) it tries to open the rep-cache.db file in read/write mode. If it doesn't exist it will usually create it. If it does exist but is read-only it silently falls back to opening it read-only, which is fine as FishEye never invokes any svnkit operations which require a write. In the case of an empty repository whose files are read only the rep-cache.db file doesn't exist and can't be created, which triggers that error. As soon as that file is created (by a commit) svnkit successfully opens the repository. {quote}

    Atlassian JIRA | 4 years ago | Kah Loun Foong [Atlassian]
    org.tmatesoft.sqljet.core.SqlJetException: CANTOPEN: error code is CANTOPEN
  3. 0

    org.tmatesoft.sqljet.core.SqlJetException: BUSY: error code is BUSY

    Stack Overflow | 4 years ago | user2291260
    org.tmatesoft.svn.core.SVNException: svn: E200030: SQLite error
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Checkout Task fails with "svn: E200030: BUSY" message - Atlassian Documentation

    atlassian.com | 4 months ago
    java.lang.RuntimeException: com.atlassian.bamboo.repository.RepositoryException: Unable to retrieve source code for revision '12345', plan 'ABC-DEF1-GHI': svn: E200030: BUSY
  6. 0

    SVNKit - Users - SVNkit on OpenVMS Alpha V8.3 with Java 1.5...

    nabble.com | 11 months ago
    org.tmatesoft.svn.core.SVNException: svn: E200030: BUSY

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.tmatesoft.sqljet.core.SqlJetException

      CANTOPEN: error code is CANTOPEN

      at org.tmatesoft.sqljet.core.internal.fs.SqlJetFileSystem.open()
    2. SqlJet Library
      SqlJetBtree.open
      1. org.tmatesoft.sqljet.core.internal.fs.SqlJetFileSystem.open(SqlJetFileSystem.java:158)
      2. org.tmatesoft.sqljet.core.internal.fs.SqlJetFileSystem.open(SqlJetFileSystem.java:185)
      3. org.tmatesoft.sqljet.core.internal.pager.SqlJetPager.open(SqlJetPager.java:395)
      4. org.tmatesoft.sqljet.core.internal.btree.SqlJetBtree.open(SqlJetBtree.java:325)
      4 frames