[
https://issues.apache.org/jira/browse/DERBY-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa closed DERBY-2592.
I have verified that the change to the JavaDoc looks as intended.
Thanks for the patch
[
https://issues.apache.org/jira/browse/DERBY-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543860
]
Olav Sandstaa commented on DERBY-3149:
--
I have tested the two new ant targets and they worked fine for me
[
https://issues.apache.org/jira/browse/DERBY-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543890
]
Olav Sandstaa commented on DERBY-3149:
--
One question about the ant junit-pptesting target: why do we have
Rick Hillegas wrote:
Please vote on whether we should make Dyre Tjeldvoll a committer.
+1
Olav
Rick Hillegas wrote:
Please vote on whether we should make Øystein Grøvlen a committer. The
vote will close at 5:00 pm San Francisco time on Tuesday August 28.
+1
Olav
Matt Doran wrote:
Rick Hillegas [EMAIL PROTECTED] writes:
* Performance and Memory Usage
o Reduces CPU usage in embedded mode.
Can anyone provide any more information on the above point? I had a look at
Jira but couldn't find the issue(s) related to this.
There were several
I have run some simple performance tests comparing the 10.3.1.0 beta
build against 10.2.2.0 to check the effect of the various performance
improvements that have gone into 10.3. The first test measure the
throughput of reading a random record from a table while the second test
runs TPC-B like
In case someone is interested in how these performance numbers for Derby
10.3 compare to other open-source databases, have a look at the last
four slides in the following presentation:
http://home.online.no/~olmsan/publications/pres/jazoon07/JavaDbJazoon07.pdf
Olav
Olav Sandstaa wrote:
I
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504155
]
Olav Sandstaa commented on DERBY-2020:
--
Thanks a lot for writing the release note, Myrna.
I think the release
Affects Versions: 10.3.0.0
Environment: Solaris/Linux, Sun JDK 5 6, IBM 1.5
Reporter: Olav Sandstaa
After check-in of svn 531971 on DERBY-2537 it seems like there for
some loads are a performance regression of about 10-15 percent.
For more info about this issue see
[
https://issues.apache.org/jira/browse/DERBY-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa updated DERBY-2657:
-
Attachment: TestClient2.java
Test client that can be used to show that there has been
[EMAIL PROTECTED] wrote:
Olav, could you please file a JIRA issue for the regression so that it
is not forgotten? A JIRA issue would also be a good place to upload the
test client that you posted in this thread.
Thanks for the suggestion. I have filed DERBY-2657 for this issue and
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494100
]
Olav Sandstaa commented on DERBY-2020:
--
Thanks for committing the patch, Kristian.
With regards to Craigs
using Sun JDK 5 VM and this also shows that
there seems to be a regression (see attached graph).
Olav
Olav Sandstaa wrote:
To see the effect of this in a different environment I started a
similar test running with IBM 1.5 VM on Linux. Unfortunately, the
machine I decided to use was a shared
The two last days I have seen a performance regression in some of the
performance tests I run. For some of the tests the reduction in
throughput is about 15 percent. It seems like the regression is
introduced by the latest check-in on DERBY-2537, svn 531971.
I have attached a graph showing
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa updated DERBY-2020:
-
Derby Info: [Patch Available]
Change file option for syncing log file to disk from rws to rwd
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa updated DERBY-2020:
-
Attachment: rwd_v2.diff
The only change in this patch (rwd_v2.diff) is to do the actual change
Hi Mike,
No, unfortunately these tests are not checked in. But using the test
client attached to DERBY-1961 should generate similar load.
Olav
Mike Matrigali wrote:
Are these tests checked in so that I can run them in my environment?
Olav Sandstaa wrote:
The two last days I have seen
a different VM (or OS) than I did they might not see the large
drop I see in my tests.
Olav
Mike Matrigali wrote:
Are these tests checked in so that I can run them in my environment?
Olav Sandstaa wrote:
The two last days I have seen a performance regression in some of the
performance tests
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa updated DERBY-2020:
-
Attachment: rwd_pre.stat
rwd_pre.diff
This patch (rwd_pre.diff) contains changes
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa updated DERBY-2020:
-
Derby Info: [Patch Available]
Change file option for syncing log file to disk from rws to rwd
Components: Javadoc
Affects Versions: 10.3.0.0
Reporter: Olav Sandstaa
Priority: Trivial
The public JavaDoc for LockTable says the following in the description of the
INDEXNAME retrieved from SYSCS_DIAG.LOCK_TABLE:
INDEXNAME varchar(128) - normally null
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490368
]
Olav Sandstaa commented on DERBY-2020:
--
Knut Anders, thanks for committing the patch and particularly
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489241
]
Olav Sandstaa commented on DERBY-2020:
--
Thanks for comments, Suresh.
1) The reason for creating a new file
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa updated DERBY-2020:
-
Attachment: jvmsyncbug_v3.stat
jvmsyncbug_v3.diff
This patch includes changes
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa updated DERBY-2020:
-
Attachment: jvmsyncbug_v2.stat
jvmsyncbug_v2.diff
Updated patch for how
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483962
]
Olav Sandstaa commented on DERBY-2020:
--
Hi Knut Anders,
Thanks for the review comments - and thanks
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482754
]
Olav Sandstaa commented on DERBY-2020:
--
Suresh and Mike,
Thanks for the comments.
I agree that Derby should
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa updated DERBY-2020:
-
Attachment: jvmsyncbug.stat
jvmsyncbug.diff
This patch (jvmsyncbug.diff
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480411
]
Olav Sandstaa commented on DERBY-2020:
--
Thanks for the comments, Knut Anders. I will go through the comments
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa reassigned DERBY-2020:
Assignee: Olav Sandstaa
Change file option for syncing log file to disk from rws to rwd
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa updated DERBY-2020:
-
Derby Info: [Patch Available]
Change file option for syncing log file to disk from rws to rwd
[
https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480050
]
Olav Sandstaa commented on DERBY-2020:
--
I have discussed this change with someone working on this part of Java
Rick Hillegas wrote:
Please vote on whether we should make Dag Wanvik a Derby committer.
The vote will close at 5:00 pm San Francisco time on Monday March 19.
+1
Olav
[
https://issues.apache.org/jira/browse/DERBY-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478390
]
Olav Sandstaa commented on DERBY-2029:
--
I have not tried to test with the other failures you mention, but I
I have downloaded and reviewed the patch. I like the introduction of the
CompatibilitySpace interface and having to explicitly to create
compatibility spaces. It mades the code more readable. Also removing the
hash table from SinglePool is good both for simplifying the code,
readability and
[
https://issues.apache.org/jira/browse/DERBY-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476570
]
Olav Sandstaa commented on DERBY-2328:
--
Adding comments sent earlier today to derby-dev when JIRA
Suresh,
Thanks for the information about log switches and checkpoints. I had to
use this server for some other work, but now I have restored the crashed
Derby database and started to look into the failing log files. See
comments inline.
Suresh Thalamati wrote:
Olav Sandstaa (JIRA) wrote
[
https://issues.apache.org/jira/browse/DERBY-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa updated DERBY-2276:
-
Attachment: DerbyPerfDurability.pdf
Attaching my presentation on Configuring Derby
[
https://issues.apache.org/jira/browse/DERBY-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466475
]
Olav Sandstaa commented on DERBY-2254:
--
Mike, thank you for commenting on this and for explaining what you
[
https://issues.apache.org/jira/browse/DERBY-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466490
]
Olav Sandstaa commented on DERBY-2254:
--
Just for the record: I tried to restart the database to see
Issue Type: Bug
Components: Store
Affects Versions: 10.3.0.0
Environment: Solaris 10, Java SE 6 build 104
Reporter: Olav Sandstaa
When running simple tpc-b like transactions against a embedded Derby based on a
SANE build of trunk the following assertion occurs
[
https://issues.apache.org/jira/browse/DERBY-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465881
]
Olav Sandstaa commented on DERBY-2254:
--
The crash happened when running simple transactions (3 updates, 1
Rick Hillegas wrote:
Please download and test-drive the 10.2.2.0 candidate, then vote on
whether to accept it as a Derby release.
I have downloaded the 10.2.2.0 candidate and run derbyall on Ubuntu 6.06
(Linux). With derbyTesting.jar in the test directory 51 tests failed. 50
of these were
://issues.apache.org/jira/browse/DERBY-2184
Project: Derby
Issue Type: Bug
Components: Documentation, Test
Affects Versions: 10.2.2.0, 10.3.0.0
Reporter: Olav Sandstaa
Priority: Trivial
The QuickStart section in java/testing/README.htm lists
Daniel John Debrunner wrote:
[EMAIL PROTECTED] wrote:
- A minor nit: This class appears to do a lot of division and
remainder calculations with powers of 2 (frequently 8). Is it not
generally preferably to do this with shifts and bitwise ANDs?
I prefer the approach that leads to code
Knut Anders Hatlen wrote:
To see the effect of this change, I tested the patch on a dual-CPU
machine with the test client from DERBY-1961 running single-record
select operations. Derby was running in embedded mode, and the entire
database was in the page cache. The results for 1 to 100
Knut Anders Hatlen wrote:
Mike Matrigali [EMAIL PROTECTED] writes:
One approach would be to continue to support the latching in the
lockmanager, but to provide an alternate implementation using the
same interfaces (or new interfaces if necessary). Then make the
default module
Great blog contribution, David! I also find the report highly biased
and agree with the other comments
regarding the presented results and the conclusion that is made. But
even if comparing Derby to BDB Java edition is comparing apples to
oranges, still I think some of the results are worth to
[ http://issues.apache.org/jira/browse/DERBY-2020?page=all ]
Olav Sandstaa updated DERBY-2020:
-
Attachment: rwd.diff
rwd.stat
This patch changes the sync mode of the log files from rws to rwd.
The purpose is to let other people test
[ http://issues.apache.org/jira/browse/DERBY-2090?page=all ]
Olav Sandstaa closed DERBY-2090.
Verified that the new link works in the latest build of the documentation.
Thanks for fixing this problem and for committing the patch, Kim and Knut
Anders
[
http://issues.apache.org/jira/browse/DERBY-2090?page=comments#action_12450676 ]
Olav Sandstaa commented on DERBY-2090:
--
I have looked at the HTML file and the change looks good. I agree that it is
better to point to a web page
Environment: All
Reporter: Olav Sandstaa
Priority: Trivial
In the section javax.sql: JDBC Extensions in the Reference manual the
following link:
http://java.sun.com/products/jdbc/jdbc20.stdext.javadoc/javax/sql/package-summary.html
is no longer valid
Jean T. Anderson wrote:
I propose that we add Laura Stewart as a committer for Derby.
+1
Olav
[
http://issues.apache.org/jira/browse/DERBY-2020?page=comments#action_12446971 ]
Olav Sandstaa commented on DERBY-2020:
--
I agree that it would be good to get a clarification of this into the
specification. I will try to discuss
Andrew McIntyre wrote:
Please vote +1 if you approve of Myrna as a committer. I will close
the voting at 10am PST on Tuesday, November 7th.
+1
Olav
Components: JDBC, Network Client
Affects Versions: 10.3.0.0
Environment: Client driver on most platforms
Reporter: Olav Sandstaa
Priority: Minor
Setting the login timeout by using DriverManager.setLoginTimeout(int
seconds) also affects the amount of time
[ http://issues.apache.org/jira/browse/DERBY-2026?page=all ]
Olav Sandstaa updated DERBY-2026:
-
Attachment: LoginTimeout.java
This is a repro showing that setting the login timeout to 10 seconds makes the
folloiwng query to fail with the exception
Mike Matrigali wrote:
Please vote +1 if you approve of Mamta as a committer.
+1
Olav
Components: JDBC, Network Client
Affects Versions: 10.2.1.8, 10.2.2.0, 10.3.0.0
Environment: Solaris 10, JDK 1.5
Reporter: Olav Sandstaa
Priority: Minor
An application using the client driver will hang infinite if the
server machine running the Derby server crashes
[ http://issues.apache.org/jira/browse/DERBY-2029?page=all ]
Olav Sandstaa updated DERBY-2029:
-
Attachment: QueryTimeout.java
This program can be used for reproducing this problem. In addition to this
program you need at least two machines
Components: Performance, Store
Affects Versions: 10.3.0.0
Reporter: Olav Sandstaa
For writing the transaction log to disk Derby uses a
RandomAccessFile. If it is supported by the JVM, the log files are
opened in rws mode making the file system take care of syncing
writes
[ http://issues.apache.org/jira/browse/DERBY-2020?page=all ]
Olav Sandstaa updated DERBY-2020:
-
Attachment: no-disk-cache.png
disk-cache.png
These graphs shows the throughput when running a specified numbers of clients
each running tpc
[
http://issues.apache.org/jira/browse/DERBY-2020?page=comments#action_12445865 ]
Olav Sandstaa commented on DERBY-2020:
--
A discussion related to this issue has taken place in the following mail thread:
http://www.nabble.com/Options
Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
+1
Olav
Daniel John Debrunner wrote:
I propose a vote for Fernanda Pizzorno as a Derby committer.
+1
Olav
I have done a simple comparison of the performance of the 10.2 release
compared to 10.1.2 using some simple performance clients.
Enclosed are graphs showing the difference in performance between
Derby 10.1.2 and Derby 10.2.1.3 beta for single-record select
transactions (1 primary key select
[ http://issues.apache.org/jira/browse/DERBY-1783?page=all ]
Olav Sandstaa resolved DERBY-1783.
--
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thanks for reviewing and committing this patch, Suresh.
I have verified the fix on trunk
[ http://issues.apache.org/jira/browse/DERBY-1783?page=all ]
Olav Sandstaa closed DERBY-1783.
Problem fixed on trunk.
Logical error in code for determining mode for opening of log files
to get similar performance. And most users will be very
happy with this and unaware of the consequences until one day their
favorite database is unable to recover after a power failure
Regards,
Olav
[1] http://java.sun.com/javase/6/docs/api/java/io/RandomAccessFile.html
Olav Sandstaa wrote
Suresh Thalamati wrote:
Olav Sandstaa wrote:
I have run some simple tests where I have changed mode from rws to
rwd for the Derby log file. When running a small numbers of
concurrent client threads the throughput is almost doubled and the
response time is almost halved. I am enclosing two
For writing the transaction log to disk Derby uses a
RandomAccessFile. If it is supported by the JVM, the log files are
opened in rws mode making the file system take care of syncing
writes to disk. rws mode will ensure that both the data and the file
meta-data is updated for every write to the
[ http://issues.apache.org/jira/browse/DERBY-1783?page=all ]
Olav Sandstaa updated DERBY-1783:
-
Attachment: rwsync.diff
Patch that fixes the logical code error by adding parentheses around the OR
clause. In addition one minor fix to the javadoc
[ http://issues.apache.org/jira/browse/DERBY-1783?page=all ]
Olav Sandstaa updated DERBY-1783:
-
Fix Version/s: 10.3.0.0
Derby Info: [Patch Available]
Logical error in code for determining mode for opening of log files
[
http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12427852 ]
Olav Sandstaa commented on DERBY-1399:
--
DerbyNetAutoStart runs without problems after DERBY-1459 was fixed. The patch
is not needed anymore. I agree that we
[ http://issues.apache.org/jira/browse/DERBY-1399?page=all ]
Olav Sandstaa updated DERBY-1399:
-
Derby Info: (was: [Patch Available])
This patch was never used since autoloading was improved (see DERBY1459) to
handle the situation which created
Kathey Marsden wrote:
This is a vote to define the coding conventions for the Derby project
per the db project guidelines http://db.apache.org/source.html
Vote closes 10:00am, Wednesday, August 15.
[+1] Adopt the coding convention described.
[-1 ] Do not adopt the coding convention
[
http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_12420833 ]
Olav Sandstaa commented on DERBY-253:
-
Thanks for reviewing and committing this patch, Knut Anders!
Since this patch removes functionality from the client driver (although
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Olav Sandstaa updated DERBY-253:
Derby Info: (was: [Patch Available])
Client should throw not implemented exception for depricated
setUnicodeStream/getUnicodeStream
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Olav Sandstaa resolved DERBY-253:
-
Resolution: Fixed
Verified that the patch is in. Thanks for commiting it, Knut Anders!
Client should throw not implemented exception for depricated
[
http://issues.apache.org/jira/browse/DERBY-253?page=comments#action_12420864 ]
Olav Sandstaa commented on DERBY-253:
-
Knut Anders, thanks for the proposal to release notes. This looks very good.
Client should throw not implemented exception
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Olav Sandstaa updated DERBY-253:
Attachment: derby253.diff
This patch replaces the existing implementation of setUnicodeStream and
getUnicodeStream in the client driver to just throw a SQL
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Olav Sandstaa updated DERBY-253:
Derby Info: [Patch Available]
Client should throw not implemented exception for depricated
setUnicodeStream/getUnicodeStream
Forgot to mention that I have run derbyall with no errors using JDK 1.5
on Solaris 10 x86.
..olav
Olav Sandstaa (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-253?page=all ]
Olav Sandstaa updated DERBY-253:
Attachment: derby253.diff
[ http://issues.apache.org/jira/browse/DERBY-955?page=all ]
Olav Sandstaa updated DERBY-955:
Attachment: bug955_derbyall.diff
This patch contains fixes to the following tests that are failing when
running derbyall with jdk 1.6:
* derbynetclientmats
[ http://issues.apache.org/jira/browse/DERBY-955?page=all ]
Olav Sandstaa updated DERBY-955:
Derby Info: [Patch Available]
Get derbyall on jdk1.6
--
Key: DERBY-955
URL: http://issues.apache.org/jira/browse
Components: JDBC, Newcomer
Versions: 10.2.0.0
Environment: Sun JDK 1.5
Reporter: Olav Sandstaa
Priority: Trivial
The first part of the string written by SQLExeption.toString() differs
between the Derby client driver and the embedded driver. The embedded
driver writes:
SQL
Components: Tools, JDBC, Network Client
Versions: 10.2.0.0
Environment: Sun JDK 1.6
Reporter: Olav Sandstaa
Priority: Minor
When running some SQL queries through ij that fails it seems like some
information about chained exceptions is not presented to the user when
running
[
http://issues.apache.org/jira/browse/DERBY-1438?page=comments#action_12417334 ]
Olav Sandstaa commented on DERBY-1438:
--
Personally, I prefer the text written by the embedded driver (SQL Exception:)
over the text written by the client driver
understand why the trailing SQLSTATE info has been stripped
off the network messages. Perhaps network serialization of chained
exceptions needs a closer look.
Regards,
-Rick
Olav Sandstaa wrote:
I am working on reducing the number of tests failing when running with
JDK 1.6. Some of the tests
Kathey Marsden wrote:
I'll analyze some usage scenarios that I am aware of and see what the
impact might be. The most important thing is that this be a
deliberate choice and that we not rush new functionality and
introduce a regression where there is a reasonable technical
alternative,
Versions: 10.2.0.0
Environment: Sun JDK 1.6
Reporter: Olav Sandstaa
Priority: Minor
When running sysinfo with jdk 1.6 information about which Java SE and JDBC
versions that is supported is missing in the output. The following is written:
- Derby Information
JRE
I am working on reducing the number of tests failing when running with
JDK 1.6. Some of the tests are now failing due to jdk16 specific
master files that have not been updated after introduction of textual
changes. To solve some of these failing tests I try eliminate the need
for jdk16 specific
[
http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12416359 ]
Olav Sandstaa commented on DERBY-1399:
--
Comments to Kathey's concerns about this patch (or rather the change introduced
in DERBY-930):
Autoloading of JDBC drivers
[
http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12416361 ]
Olav Sandstaa commented on DERBY-1399:
--
Rick, The failure you see is not related to neither autoloading nor my patch.
This problem is reported separately in DERBY-803
[
http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12416155 ]
Olav Sandstaa commented on DERBY-1399:
--
Bryan, thanks for commenting on this issue.
The call to TestUtil.loadDriver() needs to be in the test. This method loads
[ http://issues.apache.org/jira/browse/DERBY-1399?page=all ]
Olav Sandstaa updated DERBY-1399:
-
Attachment: autoload.diff
This patch fixes the problem with the embedded driver being autoloaded before
all Derby properties have been defined
[ http://issues.apache.org/jira/browse/DERBY-1399?page=all ]
Olav Sandstaa updated DERBY-1399:
-
Derby Info: [Patch Available]
DerbyNetAutoStart test fails on JDK 1.6 after introduction JDBC4 driver
autoloading
[ http://issues.apache.org/jira/browse/DERBY-1379?page=all ]
Olav Sandstaa resolved DERBY-1379:
--
Fix Version: 10.2.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Fix checked on trunk by Rick Hillegas (svn version 412859
[ http://issues.apache.org/jira/browse/DERBY-1379?page=all ]
Olav Sandstaa closed DERBY-1379:
Verified that the NIST suite runs successfully as part of derbyall with jdk 1.6.
NIST tests fail on jdk16 after introduction of JDBC4 driver autoloading
1 - 100 of 184 matches
Mail list logo
