Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-5283

Crash / process termination during SYSCS_DISABLE_LOG_ARCHIVE_MODE can leave service.properties broken

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.6.1.0, 10.8.1.2
    • 10.8.3.3, 10.9.1.0
    • Miscellaneous
    • None
    • Data corruption, Seen in production

    Description

      If Derby is terminated while SYSCS_DISABLE_LOG_ARCHIVE_MODE is being called service.properties can be left in a broken state.

      Depending on timing either of the two cases can happen:
      Case 1:
      "ERROR XBM0S: Unable to rename file 'C:\PATH_TO_DB\service.properties' to 'C:\PATH_TO_DB\service.propertiesold' " is thrown when next trying to call
      SYSCS_DISABLE_LOG_ARCHIVE_MODE(1). Both "service.properties" and "service.propertiesold" are present in the database directory. Removing "service.propertiesold" corrects the problem.

      Case 2:
      "SQLException: Database 'C:\PATH_TO_DB' not found" is thrown when booting the database. The file service.properties does not exist in the database directory but service.propertiesold does exist. Renaming the file back to "service.properties" corrects the problem.

      As mentioned above both cases have workarounds but they require manual intervention which is a problem for applications installed to a customer site. It would be great if a more reliable method to update the file could be found.

      The following sample code will reproduce the issue fairly reliably by terminating the java process:

      import java.sql.*;
      import org.apache.derby.jdbc.*;

      public class DerbyLogArchiveModeTest {

      public static void main(String[] args) {
      final EmbeddedDataSource ds = new EmbeddedDataSource();
      ds.setDatabaseName("derbyTest");
      ds.setCreateDatabase("create");

      try {
      final Connection conn = ds.getConnection();

      try {
      final Statement stmt = conn.createStatement();

      try {
      while (true)

      { stmt.execute("call SYSCS_UTIL.SYSCS_DISABLE_LOG_ARCHIVE_MODE(1)"); }

      } finally

      { stmt.close(); }

      } finally

      { conn.close(); }

      } catch (SQLException e)

      { e.printStackTrace(); }

      }
      }

      Attachments

        1. derby-5283_10_8_diff.txt
          27 kB
          Katherine Marsden
        2. derby-5283-1a-recover.diff
          19 kB
          Kristian Waagan
        3. derby-5283-1b-recover.diff
          34 kB
          Kristian Waagan
        4. derby-5283-1c-recover.diff
          34 kB
          Kristian Waagan
        5. derby-5283-2a-update_test_with_errorcodes.diff
          1 kB
          Kristian Waagan

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. DERBY-6289 Derby 10.8 backport issue (summer 2013)

          • Major - Major loss of function.
          • Closed

          Activity

            People

              kristwaa Kristian Waagan
              b.mason@adinstruments.com Brett Mason
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: