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
