db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: [jira] Created: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is made with another driver
Date Tue, 27 Jun 2006 19:24:40 GMT
Hi Kathey,

Thanks for logging DERBY-1459. That's an excellent description of the 
problem. I have marked DERBY-1429 as a duplicate of your 
better-described JIRA.

I think that DERBY-1428 is a related problem but I regard it as a 
separate issue. It describes behavior that exists in the current 
release, pre-JDBC4. The behavior described in DERBY-1428 is so ancient 
and ingrained that I don't think we can modify it. I'm afraid the best 
we can do is provide tools to customers and tech support so they can 
spot the problem when it surfaces.

Regards,
-Rick

Kathey Marsden wrote:

> Kathey Marsden (JIRA) wrote:
>
>> Early load of Derby driver with JDBC 4.0 autoloading can lead to 
>> derby properties not being processed or derby boot time actions 
>> consuming resources when a connection is made with another driver
>> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

>>
>>
>>  
>>
> Perhaps DERBY-1428 and DERBY-1429 can marked as duplicates of this 
> issue as they are special cases of the problem.
> Then focus for 10.2 can be on  fixing the general issue.
>
> Does that sound ok?
>
> Kathey
>
>


Mime
View raw message