Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
From: "Brett Mason" <b.mason@adinstruments.com>
To: "'Derby Discussion'" <derby-user@db.apache.org>
References: 
 <4A6CDC394CC14B5B92AB8ED3D5695129@WINDOMAIN.adi.co.nz><x1oxhb8cuok5.fsf@oracle.com><9B9164891FE649378D27C0D59EF559B5@WINDOMAIN.adi.co.nz>
 <x662ohyhhv.fsf@oracle.com>
In-Reply-To: <x662ohyhhv.fsf@oracle.com>
Subject: RE: Disappearing service.properties file
Date: Fri, 17 Jun 2011 15:59:40 +1200
Message-ID: <A38B9657DF11491F9323F3B5C1744FBE@WINDOMAIN.adi.co.nz>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcwlC0/DK2DENjWmQ4ydXTgtBGg/RAHlwLMA

Thanks,

Logged as DERBY-5283.

Cheers,
Brett.

-----Original Message-----
From: Dag H. Wanvik [mailto:dag.wanvik@oracle.com] 
Sent: Wednesday, 8 June 2011 00:05
To: Derby Discussion
Subject: Re: Disappearing service.properties file

"Brett Mason" <b.mason@adinstruments.com> writes:

> It does seem that Cases 1 & 2 are fairly easy to reproduce by terminating
> the Java process while it is updating service.properties. I've included
some
> sample code which will trigger the problem quite reliably when it is
> terminated on the following environments:
>
> Windows 7 64-bit, Sun 32-bit JRE 1.6u20, Derby 10.6.1.0
> Windows 7 64-bit, Sun 32-bit JDK 1.6u25, Derby 10.8.1.2
> Debian Linux 5.0, 32-bit, Sun JRE 1.6u20, Derby 10.6.1.0 (running within
> Virtual Box)
>
> Is this issue worth reporting as a bug?
>
> Are there other scenarios where the file might be updated as part of
> "normal" database usage? Particularly for regular INSERT/UPDATE/DELETE
> statements, but also maintenance procedures such as SYSCS_BACKUP_DATABASE,
> SYSCS_CHECK_TABLE, SYSCS_COMPRESS_TABLE, SYSCS_UPDATE_STATISTICS.

Please file a JIRA issue for this so we can discuss it in the community
with a view to improving the way we handle these transactional propery
settings. I don't think INSERT/UPDATE/DELETE are subject to this
scenario, but backup/restore may be. As for statistics, I don't think so
from my preliminary investigation, but I am not 100% sure yet.

Dag

>
> Thanks,
> Brett.
>
>
>
> 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();
>         }
>     }
> }