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: pass (asf.osuosl.org: local policy)
Date: Thu, 15 Sep 2005 10:49:18 +0530
From: Shreyas Kaushik <Shreyas.Kaushik@Sun.COM>
Subject: Re: DriverManager question
In-reply-to: <20050914174810.47440.qmail@web30605.mail.mud.yahoo.com>
To: Derby Discussion <derby-user@db.apache.org>
Message-id: <43290456.6030409@Sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc3 (X11/20050720)
References: <20050914174810.47440.qmail@web30605.mail.mud.yahoo.com>

Hi Suavi,

    Some changes have gone in as a part of Mustang ( Java SE 6) where 
this *synchronized* has been done away with. We targeted particularly 
the reason you are giving why it should not be synchronized.

thanks
Shreyas

Suavi Ali Demir wrote:

> A different question:
>  
> DriverManager.getConnection() is synchronized. If database A does not 
> respond, we cannot get a connection to another database B neither. 
> (Blocks the whole system). Is it advisable to use Driver.connect() and 
> side step DriverManager?
>  
> Regards,
> Suavi
>
>
> */Daniel John Debrunner <djd@debrunners.com>/* wrote:
>
>     Suavi Ali Demir wrote:
>
>     > After a shutdown=true, you should be able to connect to the same
>     > database again after doing a DriverManager.registerDriver(
>     > Class.forName(driverName).newInstance() )
>
>     No, that's not the correct way to start Derby or any other JDBC
>     driver.
>     JDBC drivers are required to register themselves, applications should
>     not be registering drivers.
>     Simply loading the driver and creating an instance of it will start
>     Derby again.
>
>     Class.forName(driverName).newInstance();
>
>     Dan.
>
>