db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shreyas Kaushik <Shreyas.Kaus...@Sun.COM>
Subject Re: DriverManager question
Date Thu, 15 Sep 2005 05:19:18 GMT
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.
>
>

Mime
View raw message