Derby
  1. Derby
  2. DERBY-4601

Shutting down just a single database should log a different message than shutting down the system

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.5.3.0
    • Fix Version/s: 10.5.3.2, 10.6.2.4, 10.7.1.1
    • Component/s: Services
    • Labels:
      None
    • Issue & fix info:
      Newcomer, Repro attached

      Description

      When shutting down just a single database and not the Derby system, the log should print a message that just that database was shutdown as I believe Derby is still loaded.

      e.g.

      ij version 10.6
      ij> run 'testMessages.sql';
      ij> connect 'jdbc:derby:wombat';
      ij> connect 'jdbc:derby:wombat2';
      ij(CONNECTION1)> connect 'jdbc:derby:wombat2;shutdown=true';
      ERROR 08006: Database 'wombat2' shutdown.
      ij(CONNECTION1)> connect 'jdbc:derby:;shutdown=true';
      ERROR XJ015: Derby system shutdown.

      yields the following log:
      2010-03-26 15:27:16.375 GMT:
      Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (927879M): instance a816c00e-0127-9b15-988d-0000002083e0
      on database directory C:\kmarsden\repro\DERBY-4588\wombat with class loader sun.misc.Launcher$AppClassLoader@42c042c0

      Database Class Loader started - derby.database.classpath=''

      ----------------------------------------------------------------

      2010-03-26 15:27:16.921 GMT:
      Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (927879M): instance 601a400f-0127-9b15-988d-0000002083e0
      on database directory C:\kmarsden\repro\DERBY-4588\wombat2 with class loader sun.misc.Launcher$AppClassLoader@42c042c0

      Database Class Loader started - derby.database.classpath=''

      2010-03-26 15:27:17.171 GMT:
      Shutting down instance 601a400f-0127-9b15-988d-0000002083e0 with class loader sun.misc.Launcher$AppClassLoader@42c042c0

      ----------------------------------------------------------------

      2010-03-26 15:27:17.218 GMT:
      Shutting down instance a816c00e-0127-9b15-988d-0000002083e0 with class loader sun.misc.Launcher$AppClassLoader@42c042c0

      ----------------------------------------------------------------

      The first shutdown should say that just the database wombat2 was shutdown, not the entire system.

      1. DERBY4601_stat2_diff.txt
        0.3 kB
        Mamta A. Satoor
      2. DERBY4601_stat1_diff.txt
        0.3 kB
        Mamta A. Satoor
      3. DERBY4601_patch2_diff.txt
        4 kB
        Mamta A. Satoor
      4. DERBY4601_patch1_diff.txt
        4 kB
        Mamta A. Satoor
      5. derby.log
        4 kB
        Mamta A. Satoor
      6. ASF.LICENSE.NOT.GRANTED--derby-4601.diff
        0.8 kB
        Eranda Sooriyabandara

        Issue Links

          Activity

          Hide
          Nirmal Fernando added a comment -

          Hi Kathey,

          ij> connect 'jdbc:derby:wombat';
          ij> connect 'jdbc:derby:wombat2';
          ij(CONNECTION1)> connect 'jdbc:derby:wombat2;shutdown=true';
          ERROR 08006: Database 'wombat2' shutdown.

                                                                                                                                                      • ************This is correct, isn't it?

          ***********************************************************************
          ij(CONNECTION1)> connect 'jdbc:derby:;shutdown=true';
          ERROR XJ015: Derby system shutdown.
          ***********************************************************************
          ************I think this also correct, since you have queried to shutdown 'jdbc:derby' which is the Derby system, and if you queried,
          connect 'jdbc:derby:wombat;shutdown=true'; this will result in following,
          ERROR 08006: Database 'wombat' shutdown.

          Thanks!!

          Show
          Nirmal Fernando added a comment - Hi Kathey, ij> connect 'jdbc:derby:wombat'; ij> connect 'jdbc:derby:wombat2'; ij(CONNECTION1)> connect 'jdbc:derby:wombat2;shutdown=true'; ERROR 08006: Database 'wombat2' shutdown. ************This is correct, isn't it? *********************************************************************** ij(CONNECTION1)> connect 'jdbc:derby:;shutdown=true'; ERROR XJ015: Derby system shutdown. *********************************************************************** ************I think this also correct, since you have queried to shutdown 'jdbc:derby' which is the Derby system, and if you queried, connect 'jdbc:derby:wombat;shutdown=true'; this will result in following, ERROR 08006: Database 'wombat' shutdown. Thanks!!
          Hide
          Thiwanka Somasiri added a comment - - edited

          Hi all,
          As I understood, Kathey focussed on the derby.log file.The ij tool is ok with the output it displays.But the thing is that the derby.log shows the same output for derby database shutdown and the system shutdown.It gives the results as follows:

          ij command to shutdown derby database : CONNECT 'jdbc:derby:firstdb;shutdown=true';
          derby.log :
          2010-04-11 04:44:27.682 GMT:
          Shutting down instance a816c00e-0127-eb2d-9710-0000032be180 with class
          loader sun.misc.Launcher$AppClassLoader@2c2bbd86

          ij command to shutdown system : CONNECT 'jdbc:derby:;shutdown=true';
          derby.log :
          2010-04-11 04:44:37.944 GMT:
          Shutting down instance 601a400f-0127-eb2d-9710-0000032be180 with class
          loader sun.misc.Launcher$AppClassLoader@2c2bbd86

          As this says both db and sys shutdowns gives the same output.The thing I need to know is, "whether the Derby system is down even after the above second ij command is issued?"
          I need to clarify which derby.log output is correct in this case.Better if someone can explain this.

          Thanks.

          Show
          Thiwanka Somasiri added a comment - - edited Hi all, As I understood, Kathey focussed on the derby.log file.The ij tool is ok with the output it displays.But the thing is that the derby.log shows the same output for derby database shutdown and the system shutdown.It gives the results as follows: ij command to shutdown derby database : CONNECT 'jdbc:derby:firstdb;shutdown=true'; derby.log : 2010-04-11 04:44:27.682 GMT: Shutting down instance a816c00e-0127-eb2d-9710-0000032be180 with class loader sun.misc.Launcher$AppClassLoader@2c2bbd86 ij command to shutdown system : CONNECT 'jdbc:derby:;shutdown=true'; derby.log : 2010-04-11 04:44:37.944 GMT: Shutting down instance 601a400f-0127-eb2d-9710-0000032be180 with class loader sun.misc.Launcher$AppClassLoader@2c2bbd86 As this says both db and sys shutdowns gives the same output.The thing I need to know is, "whether the Derby system is down even after the above second ij command is issued?" I need to clarify which derby.log output is correct in this case.Better if someone can explain this. Thanks.
          Hide
          Nirmal Fernando added a comment -

          Hi All,

          @Thiwanka: Yeah, I got it wrong !! Thanks for pointing it out !!

          Sorry about that. I issued some queries in order to check what has happened after issuing the above two shutting down commands.

          ij> connect 'jdbc:derby:myDB';
          ij> connect 'jdbc:derby:myDB1';
          ij(CONNECTION1)> connect 'jdbc:derby:myDB'; ************to check whether I can switch connections --> yes
          ij(CONNECTION2)> connect 'jdbc:derby:;databaseName=myDB1;shutdown=true';
          ERROR 08006: Database 'myDB1' shutdown. ************this is fine
          ij(CONNECTION2)> connect 'jdbc:derby:myDB'; ************I connected back to myDB
          ij(CONNECTION3)> select * from t; ************it was ok --> Derby System has not shutdown ?? (Is this right?)
          A |B
          -----------------------
          1 |NULL
          1 |NULL
          NULL |NULL
          NULL |NULL
          NULL |1

          5 rows selected

          ***********************************************************************
          ij(CONNECTION3)>
          connect 'jdbc:derby:myDB';
          ij(CONNECTION4)> connect 'jdbc:derby:myDB1';
          ij(CONNECTION5)> connect 'jdbc:derby:;shutdown=true'; ***********I issued the command to shutdown the entire system
          ERROR XJ015: Derby system shutdown. ***********fine !!
          ij(CONNECTION5)> connect 'jdbc:derby:myDB'; ***********I tried to establish a connection after shut downing the entire system --> This should fail right??
          ij(CONNECTION6)> select * from t; ***********But it was successful !!

          A |B
          -----------------------
          1 |NULL
          1 |NULL
          NULL |NULL
          NULL |NULL
          NULL |1

          5 rows selected

          If my above assumptions are correct, this imply that the "system shutdown" was not actually done.

          Thanks !!

          Show
          Nirmal Fernando added a comment - Hi All, @Thiwanka: Yeah, I got it wrong !! Thanks for pointing it out !! Sorry about that. I issued some queries in order to check what has happened after issuing the above two shutting down commands. ij> connect 'jdbc:derby:myDB'; ij> connect 'jdbc:derby:myDB1'; ij(CONNECTION1)> connect 'jdbc:derby:myDB'; ************to check whether I can switch connections --> yes ij(CONNECTION2)> connect 'jdbc:derby:;databaseName=myDB1;shutdown=true'; ERROR 08006: Database 'myDB1' shutdown. ************this is fine ij(CONNECTION2)> connect 'jdbc:derby:myDB'; ************I connected back to myDB ij(CONNECTION3)> select * from t; ************it was ok --> Derby System has not shutdown ?? (Is this right?) A |B ----------------------- 1 |NULL 1 |NULL NULL |NULL NULL |NULL NULL |1 5 rows selected *********************************************************************** ij(CONNECTION3)> connect 'jdbc:derby:myDB'; ij(CONNECTION4)> connect 'jdbc:derby:myDB1'; ij(CONNECTION5)> connect 'jdbc:derby:;shutdown=true'; ***********I issued the command to shutdown the entire system ERROR XJ015: Derby system shutdown. ***********fine !! ij(CONNECTION5)> connect 'jdbc:derby:myDB'; ***********I tried to establish a connection after shut downing the entire system --> This should fail right?? ij(CONNECTION6)> select * from t; ***********But it was successful !! A |B ----------------------- 1 |NULL 1 |NULL NULL |NULL NULL |NULL NULL |1 5 rows selected If my above assumptions are correct, this imply that the "system shutdown" was not actually done. Thanks !!
          Hide
          Thiwanka Somasiri added a comment -

          Hi all,
          I think this is not a case of Derby system shutdown. It simply logs non-descriptive messages to separately identify the database shutdown and system shutdown in derby.log.

          CONNECT 'jdbc:derby:firstdb;create=true';

          This command creates a database if not existing one with name firstdb, with which the JDBC protocol specification for the Derby driver "jdbc:derby".
          So even if the Derby system is down it starts the Derby engine and create the database.

          So even we issue the command CONNECT 'jdbc:derby:firstdb;shutdown=true'; and then issue the CONNECT 'jdbc:derby:firstdb;create=true';
          the system shutdown first and then get started.So, as I understood there is not a problem with the Derby system shutdown.It is just a case of logging in the derby.log file.

          If there is any misunderstanding, please correct it...!

          Thank you all.

          Show
          Thiwanka Somasiri added a comment - Hi all, I think this is not a case of Derby system shutdown. It simply logs non-descriptive messages to separately identify the database shutdown and system shutdown in derby.log. CONNECT 'jdbc:derby:firstdb;create=true'; This command creates a database if not existing one with name firstdb, with which the JDBC protocol specification for the Derby driver "jdbc:derby". So even if the Derby system is down it starts the Derby engine and create the database. So even we issue the command CONNECT 'jdbc:derby:firstdb;shutdown=true'; and then issue the CONNECT 'jdbc:derby:firstdb;create=true'; the system shutdown first and then get started.So, as I understood there is not a problem with the Derby system shutdown.It is just a case of logging in the derby.log file. If there is any misunderstanding, please correct it...! Thank you all.
          Hide
          Eranda Sooriyabandara added a comment -

          Hi Thiwanka,Nirmal,
          Looking at the code at stop() method in BaseDataFileFactory will help you I think.

          Show
          Eranda Sooriyabandara added a comment - Hi Thiwanka,Nirmal, Looking at the code at stop() method in BaseDataFileFactory will help you I think.
          Hide
          Eranda Sooriyabandara added a comment -

          Hi Kathey,
          Here I found out something.
          The log message is all about shutting down single database not the full system. When we shutdown full system it logs which database shuts. It don't print as as a system shut.

          Here I connect some database instances

          ----------------------------------------------------------------
          2010-04-15 07:55:56.686 GMT:
          Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (1): instance a816c00e-0128-0077-9584-0000009e19d8
          on database directory E:\GSoC-2010\Derby-2785\trunk\wombat with class loader sun.misc.Launcher$AppClassLoader@11b86e7

          Database Class Loader started - derby.database.classpath=''
          ----------------------------------------------------------------
          2010-04-15 07:56:00.828 GMT:
          Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (1): instance 601a400f-0128-0077-9584-0000009e19d8
          on database directory E:\GSoC-2010\Derby-2785\trunk\wombat2 with class loader sun.misc.Launcher$AppClassLoader@11b86e7

          Database Class Loader started - derby.database.classpath=''
          ----------------------------------------------------------------
          2010-04-15 07:56:03.966 GMT Thread[main,5,main] Cleanup action starting
          2010-04-15 07:56:15.917 GMT:
          Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (1): instance f81e0010-0128-0077-9584-0000009e19d8
          on database directory E:\GSoC-2010\Derby-2785\trunk\wombat3 with class loader sun.misc.Launcher$AppClassLoader@11b86e7

          Database Class Loader started - derby.database.classpath=''
          ----------------------------------------------------------------
          2010-04-15 07:56:33.415 GMT:
          Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (1): instance d381409a-0128-0077-9584-0000009e19d8
          on database directory E:\GSoC-2010\Derby-2785\trunk\wombat4 with class loader sun.misc.Launcher$AppClassLoader@11b86e7

          Database Class Loader started - derby.database.classpath=''

          And shut them at once with the path with the additional part of absolute path of the database directory. What I get in the log was

          2010-04-15 07:57:09.015 GMT:
          Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat4 d381409a-0128-0077-9584-0000009e19d8 with class loader sun.misc.Launcher$AppClassLoader@11b86e7
          ----------------------------------------------------------------

          2010-04-15 07:57:09.104 GMT:
          Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat3 f81e0010-0128-0077-9584-0000009e19d8 with class loader sun.misc.Launcher$AppClassLoader@11b86e7
          ----------------------------------------------------------------

          2010-04-15 07:57:09.191 GMT:
          Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat2 601a400f-0128-0077-9584-0000009e19d8 with class loader sun.misc.Launcher$AppClassLoader@11b86e7
          ----------------------------------------------------------------

          2010-04-15 07:57:09.223 GMT:
          Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat a816c00e-0128-0077-9584-0000009e19d8 with class loader sun.misc.Launcher$AppClassLoader@11b86e7
          ----------------------------------------------------------------

          That means though we shut all the connection at once it shuts connections one by one and log separately.

          So I think the better way is to add the database name to the log. What you think?

          Show
          Eranda Sooriyabandara added a comment - Hi Kathey, Here I found out something. The log message is all about shutting down single database not the full system. When we shutdown full system it logs which database shuts. It don't print as as a system shut. Here I connect some database instances ---------------------------------------------------------------- 2010-04-15 07:55:56.686 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (1): instance a816c00e-0128-0077-9584-0000009e19d8 on database directory E:\GSoC-2010\Derby-2785\trunk\wombat with class loader sun.misc.Launcher$AppClassLoader@11b86e7 Database Class Loader started - derby.database.classpath='' ---------------------------------------------------------------- 2010-04-15 07:56:00.828 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (1): instance 601a400f-0128-0077-9584-0000009e19d8 on database directory E:\GSoC-2010\Derby-2785\trunk\wombat2 with class loader sun.misc.Launcher$AppClassLoader@11b86e7 Database Class Loader started - derby.database.classpath='' ---------------------------------------------------------------- 2010-04-15 07:56:03.966 GMT Thread [main,5,main] Cleanup action starting 2010-04-15 07:56:15.917 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (1): instance f81e0010-0128-0077-9584-0000009e19d8 on database directory E:\GSoC-2010\Derby-2785\trunk\wombat3 with class loader sun.misc.Launcher$AppClassLoader@11b86e7 Database Class Loader started - derby.database.classpath='' ---------------------------------------------------------------- 2010-04-15 07:56:33.415 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (1): instance d381409a-0128-0077-9584-0000009e19d8 on database directory E:\GSoC-2010\Derby-2785\trunk\wombat4 with class loader sun.misc.Launcher$AppClassLoader@11b86e7 Database Class Loader started - derby.database.classpath='' And shut them at once with the path with the additional part of absolute path of the database directory. What I get in the log was 2010-04-15 07:57:09.015 GMT: Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat4 d381409a-0128-0077-9584-0000009e19d8 with class loader sun.misc.Launcher$AppClassLoader@11b86e7 ---------------------------------------------------------------- 2010-04-15 07:57:09.104 GMT: Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat3 f81e0010-0128-0077-9584-0000009e19d8 with class loader sun.misc.Launcher$AppClassLoader@11b86e7 ---------------------------------------------------------------- 2010-04-15 07:57:09.191 GMT: Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat2 601a400f-0128-0077-9584-0000009e19d8 with class loader sun.misc.Launcher$AppClassLoader@11b86e7 ---------------------------------------------------------------- 2010-04-15 07:57:09.223 GMT: Shutting down instance E:\GSoC-2010\Derby-2785\trunk\wombat a816c00e-0128-0077-9584-0000009e19d8 with class loader sun.misc.Launcher$AppClassLoader@11b86e7 ---------------------------------------------------------------- That means though we shut all the connection at once it shuts connections one by one and log separately. So I think the better way is to add the database name to the log. What you think?
          Hide
          Eranda Sooriyabandara added a comment -

          Hi,
          I think this patch can be use if it need the modification of print database name on the log.
          Thanks

          Show
          Eranda Sooriyabandara added a comment - Hi, I think this patch can be use if it need the modification of print database name on the log. Thanks
          Hide
          Knut Anders Hatlen added a comment -

          Mamta posted a patch for this issue on DERBY-4610. I'm adding my comments here:

          1) loc/messages.xml:

          + <text>:Shutting down Derby Engine </text>

          Is the colon before "Shutting" and the blank space after "Engine" intended? If so, would it be better to add those characters using literals in BaseMonitor.java (same way as we use a literal there to add an extra newline)? I think there's a good chance that translators will think the characters are not part of the message and will leave them out.

          2) BaseDataFileFactory.java:

          MessageService.getTextMessage(
          MessageId.STORE_SHUTDOWN_MSG,

          • getIdentifier(),
            + getIdentifier()+" on database directory "+getRootDirectory(),

          Hard-coding English text as an argument to an internationalized message like this will make the message look awkward when it's localized to another language. It would be better to change STORE_SHUTDOWN_MSG to take an extra argument (the root directory).

          Show
          Knut Anders Hatlen added a comment - Mamta posted a patch for this issue on DERBY-4610 . I'm adding my comments here: 1) loc/messages.xml: + <text>:Shutting down Derby Engine </text> Is the colon before "Shutting" and the blank space after "Engine" intended? If so, would it be better to add those characters using literals in BaseMonitor.java (same way as we use a literal there to add an extra newline)? I think there's a good chance that translators will think the characters are not part of the message and will leave them out. 2) BaseDataFileFactory.java: MessageService.getTextMessage( MessageId.STORE_SHUTDOWN_MSG, getIdentifier(), + getIdentifier()+" on database directory "+getRootDirectory(), Hard-coding English text as an argument to an internationalized message like this will make the message look awkward when it's localized to another language. It would be better to change STORE_SHUTDOWN_MSG to take an extra argument (the root directory).
          Hide
          Mamta A. Satoor added a comment -

          Attaching a patch which will log the Engine shutdown message in derby.log. The existing message logging for each individual connection close which happen because of engine shutdown will still be logged but they will now print the name of the database being shutdown.

          The existing regression tests ran fine. If there is no objection to this patch, I will commit it by Wednesday morning.

          Show
          Mamta A. Satoor added a comment - Attaching a patch which will log the Engine shutdown message in derby.log. The existing message logging for each individual connection close which happen because of engine shutdown will still be logged but they will now print the name of the database being shutdown. The existing regression tests ran fine. If there is no objection to this patch, I will commit it by Wednesday morning.
          Hide
          Mamta A. Satoor added a comment -

          Thanks, Knut, for taking the time to review the patch. In loc/messages.xml, I have removed the blank space after the message. The colon is needed to separate the message from the timestamp header. I have changed BaseMonitor.java to take care of that colon rather than putting it directly in messages.xml. In BaseDataFileFactory.java, I have removed the english text and added it to the existing message in messages.xml.

          Please let me know if you have any further comments.

          Show
          Mamta A. Satoor added a comment - Thanks, Knut, for taking the time to review the patch. In loc/messages.xml, I have removed the blank space after the message. The colon is needed to separate the message from the timestamp header. I have changed BaseMonitor.java to take care of that colon rather than putting it directly in messages.xml. In BaseDataFileFactory.java, I have removed the english text and added it to the existing message in messages.xml. Please let me know if you have any further comments.
          Hide
          Knut Anders Hatlen added a comment -

          Thanks Mamta. The latest patch looks good to me. +1

          Show
          Knut Anders Hatlen added a comment - Thanks Mamta. The latest patch looks good to me. +1
          Hide
          Kim Haase added a comment -

          If the changes to the output will affect the messages shown in the Getting Started guide and elsewhere – for example, in http://db.apache.org/derby/docs/dev/getstart/getstart-single.html#twwdactivity1 and the sections after that – please file a documentation issue after this issue is resolved, so we can get these fixed.

          Show
          Kim Haase added a comment - If the changes to the output will affect the messages shown in the Getting Started guide and elsewhere – for example, in http://db.apache.org/derby/docs/dev/getstart/getstart-single.html#twwdactivity1 and the sections after that – please file a documentation issue after this issue is resolved, so we can get these fixed.
          Hide
          Mamta A. Satoor added a comment -

          Knut, I will go ahead and enter a jira for the doc changes. Committed the code changes for this jira with revision 966393

          Show
          Mamta A. Satoor added a comment - Knut, I will go ahead and enter a jira for the doc changes. Committed the code changes for this jira with revision 966393
          Hide
          Mamta A. Satoor added a comment -

          By mistake, I was printing the timestamp twice in derby.log for engine shutdown. Fixed that with revision 967201.

          Also, created a jira for doc updates DERBY-4755

          Show
          Mamta A. Satoor added a comment - By mistake, I was printing the timestamp twice in derby.log for engine shutdown. Fixed that with revision 967201. Also, created a jira for doc updates DERBY-4755
          Hide
          Mamta A. Satoor added a comment -

          Made couple more checkins to make the shutdown message more readable in derby.log I have attached a sample derby.log to see how the shutdown message will look like

          Show
          Mamta A. Satoor added a comment - Made couple more checkins to make the shutdown message more readable in derby.log I have attached a sample derby.log to see how the shutdown message will look like
          Hide
          Kathey Marsden added a comment -

          Reopen for backport

          Show
          Kathey Marsden added a comment - Reopen for backport
          Hide
          Mamta A. Satoor added a comment -

          Kathey, I backported the issue to 10.6 and 10.5.

          Show
          Mamta A. Satoor added a comment - Kathey, I backported the issue to 10.6 and 10.5.
          Hide
          Knut Anders Hatlen added a comment -

          [bulk update] Close all resolved issues that haven't been updated for more than one year.

          Show
          Knut Anders Hatlen added a comment - [bulk update] Close all resolved issues that haven't been updated for more than one year.

            People

            • Assignee:
              Mamta A. Satoor
              Reporter:
              Kathey Marsden
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development