[jira] [Resolved] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas resolved DERBY-6445. Fix Version/s: 10.15.2.1 10.16.1.2 10.17.1.1 10.18.0.0 Resolution: Fixed > JDBC 4.2: Add support for new date and time classes > --- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC >Affects Versions: 10.10.1.1 >Reporter: Knut Anders Hatlen >Priority: Major > Fix For: 10.15.2.1, 10.16.1.2, 10.17.1.1, 10.18.0.0 > > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html, > derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff, > derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff, > derby-6445-02-aa-patchExplanation.diff, tweaks.diff > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7163) Make it possible to build and test Derby with Open JDK 23
[
https://issues.apache.org/jira/browse/DERBY-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853806#comment-17853806
]
Richard N. Hillegas commented on DERBY-7163:
Attaching derby-7163-01-aa-addJDK23vm.diff. This patch adds a JDK 23 test VM.
Tests with this patch, using Open JDK build 23-ea+26-2269 passed cleanly using
both the classpath and the modulepath. Derby builds and tests cleanly with that
Open JDK build. The javadoc builds cleanly too.
Touches the following files:
{noformat}
M
java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyTesting.jar.lastcontents
M
java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyTesting.jar.lastcontents
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/harness/JavaVersionHolder.java
A
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/harness/jdk123.java
{noformat}
> Make it possible to build and test Derby with Open JDK 23
> -
>
> Key: DERBY-7163
> URL: https://issues.apache.org/jira/browse/DERBY-7163
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Affects Versions: 10.18.0.0
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7163-01-aa-addJDK23vm.diff
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7163) Make it possible to build and test Derby with Open JDK 23
[ https://issues.apache.org/jira/browse/DERBY-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7163: --- Attachment: derby-7163-01-aa-addJDK23vm.diff > Make it possible to build and test Derby with Open JDK 23 > - > > Key: DERBY-7163 > URL: https://issues.apache.org/jira/browse/DERBY-7163 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.18.0.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7163-01-aa-addJDK23vm.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853797#comment-17853797 ] Richard N. Hillegas commented on DERBY-6445: Linking this issue to DERBY-6834, another discussion about the precision of Derby's DATE/TIME/TIMESTAMP types. > JDBC 4.2: Add support for new date and time classes > --- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC >Affects Versions: 10.10.1.1 >Reporter: Knut Anders Hatlen >Priority: Major > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html, > derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff, > derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff, > derby-6445-02-aa-patchExplanation.diff, tweaks.diff > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853796#comment-17853796 ] Richard N. Hillegas commented on DERBY-6445: Thanks for your thoughts, Philippe and Bryan. It seems that there is broad agreement that the precision of Derby's TIME datatype is outside the scope of this JIRA issue. > JDBC 4.2: Add support for new date and time classes > --- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC >Affects Versions: 10.10.1.1 >Reporter: Knut Anders Hatlen >Priority: Major > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html, > derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff, > derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff, > derby-6445-02-aa-patchExplanation.diff, tweaks.diff > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DERBY-7163) Make it possible to build and test Derby with Open JDK 23
Richard N. Hillegas created DERBY-7163: -- Summary: Make it possible to build and test Derby with Open JDK 23 Key: DERBY-7163 URL: https://issues.apache.org/jira/browse/DERBY-7163 Project: Derby Issue Type: Task Components: Build tools Affects Versions: 10.18.0.0 Reporter: Richard N. Hillegas Assignee: Richard N. Hillegas -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[
https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851796#comment-17851796
]
Richard N. Hillegas commented on DERBY-6445:
Thanks for that great explanation, Philippe. I have added it to the header
comment of SQLTimstamp.
I am confused about the subtleties surrounding the precision of the
java.sql.Time and SQL TIME types. My experiments show that java.sql.Time
truncates a millisecond-granularity timestamp to seconds, throwing away the
excess milliseconds, even using the Calendar code you included. The SQL TIME
datatype has HOUR, MINUTE, and SECONDs parts (no milliseconds), according to
the SQL Standard, part 2 (Foundation), clause 4.6.2 (Datetimes). So it seems to
me that the code in the patch is correct as is.
Here is the experiment I ran:
{noformat}
import java.sql.*;
import java.util.Calendar;
public class TimeTest
{
public static void main(String... args) throws Exception {
Connection conn =
DriverManager.getConnection("jdbc:derby:memory:db;create=true");
prepareStatement(conn, "CREATE TABLE t(a TIME)").execute();
Time time1 = new Time(System.currentTimeMillis());
Calendar calendar = Calendar.getInstance();
calendar.clear();
calendar.set(Calendar.YEAR, 1970);
calendar.set(Calendar.MONTH, Calendar.JANUARY);
calendar.set(Calendar.DAY_OF_MONTH, 1);
calendar.set(Calendar.HOUR_OF_DAY, 1);
calendar.set(Calendar.MINUTE, 2);
calendar.set(Calendar.SECOND, 3);
calendar.set(Calendar.MILLISECOND, 456);
Time time2 = new Time(calendar.getTimeInMillis());
try (PreparedStatement ps = prepareStatement(conn, "INSERT INTO t
VALUES (?)"))
{
setTime(ps, time1);
ps.execute();
setTime(ps, time2);
ps.execute();
}
try (PreparedStatement ps = prepareStatement(conn, "SELECT * from t"))
{
try (ResultSet rs = ps.executeQuery())
{
while(rs.next())
{
println(rs.getTime(1).toString());
}
}
}
}
private static void setTime(PreparedStatement ps, Time time) throws
SQLException {
println("Setting time column to " + time.toString());
ps.setTime(1, time);
}
private static PreparedStatement prepareStatement(Connection conn, String
text) throws SQLException {
println("Preparing '" + text + "' ...");
return conn.prepareStatement(text);
}
private static void println(String text) { System.out.println(text); }
}
{noformat}
Here is the output of that experiment:
{noformat}
Preparing 'CREATE TABLE t(a TIME)' ...
Preparing 'INSERT INTO t VALUES (?)' ...
Setting time column to 12:26:04
Setting time column to 01:02:03
Preparing 'SELECT * from t' ...
12:26:04
01:02:03
{noformat}
> JDBC 4.2: Add support for new date and time classes
> ---
>
> Key: DERBY-6445
> URL: https://issues.apache.org/jira/browse/DERBY-6445
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
>Affects Versions: 10.10.1.1
>Reporter: Knut Anders Hatlen
>Priority: Major
> Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html,
> derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff,
> derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff,
> derby-6445-02-aa-patchExplanation.diff, tweaks.diff
>
>
> JDBC 4.2 added type mappings for new date and time classes found in Java 8.
> Derby should support these new mappings.
> This would at least affect Derby's implementation of the various getObject(),
> setObject() and setNull() methods in ResultSet, PreparedStatement and
> CallableStatement.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[
https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851769#comment-17851769
]
Richard N. Hillegas commented on DERBY-6445:
Attaching derby-6445-02-aa-patchExplanation.diff. This patch adds Philippe's
explanation to the header comment for SQLTimestamp.
Touches the following files:
{noformat}
M
java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLTimestamp.java
Philippe's explanation.
M java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLDate.java
M java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLTime.java
References to the SQLTimestamp header comment, for people interested in
following the behavior of
java.time.LocalDate and java.time.LocalTime.
{noformat}
> JDBC 4.2: Add support for new date and time classes
> ---
>
> Key: DERBY-6445
> URL: https://issues.apache.org/jira/browse/DERBY-6445
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
>Affects Versions: 10.10.1.1
>Reporter: Knut Anders Hatlen
>Priority: Major
> Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html,
> derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff,
> derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff,
> derby-6445-02-aa-patchExplanation.diff, tweaks.diff
>
>
> JDBC 4.2 added type mappings for new date and time classes found in Java 8.
> Derby should support these new mappings.
> This would at least affect Derby's implementation of the various getObject(),
> setObject() and setNull() methods in ResultSet, PreparedStatement and
> CallableStatement.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-6445: --- Attachment: derby-6445-02-aa-patchExplanation.diff > JDBC 4.2: Add support for new date and time classes > --- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC >Affects Versions: 10.10.1.1 >Reporter: Knut Anders Hatlen >Priority: Major > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html, > derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff, > derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff, > derby-6445-02-aa-patchExplanation.diff, tweaks.diff > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849588#comment-17849588 ] Richard N. Hillegas commented on DERBY-6445: Attaching derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff. This adds some additional tweaks to the derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff patch. Also attaching tweaks.diff which shows the difference between derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff and derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff. The tweaks are: 1) Diagnostic traces were added for entering and exiting some of the methods. As Philippe points out, there is no ideal approach to this problem. The original tracing was for entering/exiting the JDBC getter and setter methods. This breaks down when dealing with get/setObject() because those methods forward to more specific getters and setters. I added traces to the new forwarding methods. 2) I reduced the visibility of some of the new methods from public to private in order to avoid encroaching on public interfaces which may change in future revs of the JDBC spec. 3) I changed the data types reported in some error messages. This patch touches the same files as the previous patches. I ran full tests using both the classpath and the modulepath. Both runs were clean. I am inclined to commit this patch because, despite my reservations (see below), I think that this is a large piece of solid, incremental work. Having some support for these data types is better than raising exceptions. Thanks, Philippe, for this valuable contribution. My chief reservations are the following: A) I am not an expert on the new date/time classes. I can't evaluate whether the patch causes these types to serialize and deserialize correctly. These classes came out of long, tortured discussions among Java champions and my sense is that the experts failed to reach consensus. I have nothing to add to those discussions. I am worried that an expert may log a bug saying that Derby is not (de)serializing these classes correctly. B) Therefore, I would like to see some comments which explain the approach taken in serializing these objects, that is, for converting between the new classes and the JDBC types which Derby already supports. Right now, there are very few comments in this large patch. The comments should help us field bug reports which may be filed against the correctness of the serialization. C) I would also like to see comments added to the new test methods, explaining what the methods are testing. Thanks, -Rick > JDBC 4.2: Add support for new date and time classes > --- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC >Affects Versions: 10.10.1.1 >Reporter: Knut Anders Hatlen >Priority: Major > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html, > derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff, > derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff, tweaks.diff > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-6445: --- Attachment: tweaks.diff > JDBC 4.2: Add support for new date and time classes > --- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC >Affects Versions: 10.10.1.1 >Reporter: Knut Anders Hatlen >Priority: Major > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html, > derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff, > derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff, tweaks.diff > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-6445: --- Attachment: derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff > JDBC 4.2: Add support for new date and time classes > --- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC >Affects Versions: 10.10.1.1 >Reporter: Knut Anders Hatlen >Priority: Major > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html, > derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff, > derby-6445-01-ab-DERBY-6445.patchPlusPlusTweaks.diff > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849411#comment-17849411 ] Richard N. Hillegas commented on DERBY-6445: Thanks for your thoughts about diagnostic logging, Philippe. I am going through the patch, making additional tweaks, including adding diagnostic logging calls. We can discuss this further when I post that revised patch. > JDBC 4.2: Add support for new date and time classes > --- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC >Affects Versions: 10.10.1.1 >Reporter: Knut Anders Hatlen >Priority: Major > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html, > derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849372#comment-17849372 ] Richard N. Hillegas commented on DERBY-6445: Tests passed (with the classpath) on derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff. > JDBC 4.2: Add support for new date and time classes > --- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC >Affects Versions: 10.10.1.1 >Reporter: Knut Anders Hatlen >Priority: Major > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html, > derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[
https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849350#comment-17849350
]
Richard N. Hillegas commented on DERBY-6445:
Attaching derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff. This is
Philippe's patch plus some fixes for its Javadoc warnings. I will run full
tests against this patch.
A quick glance at the patch indicates that some methods are missing the
diagnostic logging which appears in sister methods. At a minimum, the patch
will need a little more tweaking to bring it into alignment with that
diagnostic logging pattern.
Touches the following files:
{noformat}
M
java/org.apache.derby.client/org/apache/derby/client/am/ClientCallableStatement.java
M
java/org.apache.derby.client/org/apache/derby/client/am/ClientPreparedStatement.java
M
java/org.apache.derby.client/org/apache/derby/client/am/ClientResultSet.java
M
java/org.apache.derby.client/org/apache/derby/client/am/CrossConverters.java
M java/org.apache.derby.client/org/apache/derby/client/am/Cursor.java
M java/org.apache.derby.client/org/apache/derby/client/am/DateTime.java
M
java/org.apache.derby.client/org/apache/derby/client/am/DateTimeValue.java
M java/org.apache.derby.engine/org/apache/derby/iapi/types/DataType.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/types/DataValueDescriptor.java
M java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLChar.java
M java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLClob.java
M java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLDate.java
M java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLTime.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/types/SQLTimestamp.java
M java/org.apache.derby.engine/org/apache/derby/iapi/types/UserType.java
M
java/org.apache.derby.engine/org/apache/derby/impl/jdbc/EmbedCallableStatement.java
M
java/org.apache.derby.engine/org/apache/derby/impl/jdbc/EmbedPreparedStatement.java
M
java/org.apache.derby.engine/org/apache/derby/impl/jdbc/EmbedResultSet.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbc4/CallableStatementTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbc4/PreparedStatementTest42.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbc4/Wrapper41Test.java
{noformat}
> JDBC 4.2: Add support for new date and time classes
> ---
>
> Key: DERBY-6445
> URL: https://issues.apache.org/jira/browse/DERBY-6445
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
>Affects Versions: 10.10.1.1
>Reporter: Knut Anders Hatlen
>Priority: Major
> Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html,
> derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff
>
>
> JDBC 4.2 added type mappings for new date and time classes found in Java 8.
> Derby should support these new mappings.
> This would at least affect Derby's implementation of the various getObject(),
> setObject() and setNull() methods in ResultSet, PreparedStatement and
> CallableStatement.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-6445: --- Attachment: derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff > JDBC 4.2: Add support for new date and time classes > --- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC >Affects Versions: 10.10.1.1 >Reporter: Knut Anders Hatlen >Priority: Major > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html, > derby-6445-01-aa-DERBY-6445.patchPlusJavadocCleanup.diff > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-6445) JDBC 4.2: Add support for new date and time classes
[ https://issues.apache.org/jira/browse/DERBY-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849349#comment-17849349 ] Richard N. Hillegas commented on DERBY-6445: Thanks, Philippe. I will take a look at this patch. > JDBC 4.2: Add support for new date and time classes > --- > > Key: DERBY-6445 > URL: https://issues.apache.org/jira/browse/DERBY-6445 > Project: Derby > Issue Type: Improvement > Components: JDBC >Affects Versions: 10.10.1.1 >Reporter: Knut Anders Hatlen >Priority: Major > Attachments: DERBY-6445.patch, Derby-6445.html, Derby-6445.html > > > JDBC 4.2 added type mappings for new date and time classes found in Java 8. > Derby should support these new mappings. > This would at least affect Derby's implementation of the various getObject(), > setObject() and setNull() methods in ResultSet, PreparedStatement and > CallableStatement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7161) Document the need for client-side applications to vet user-supplied connection directives
[ https://issues.apache.org/jira/browse/DERBY-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7161: --- Attachment: derby-7161-01-aa-traceFileAttributes.tar > Document the need for client-side applications to vet user-supplied > connection directives > - > > Key: DERBY-7161 > URL: https://issues.apache.org/jira/browse/DERBY-7161 > Project: Derby > Issue Type: Task > Components: Documentation, Network Client >Affects Versions: 10.18.0.0 >Reporter: Richard N. Hillegas >Priority: Major > Attachments: derby-7161-01-aa-traceFileAttributes.diff, > derby-7161-01-aa-traceFileAttributes.tar > > > Somewhere, we should document the fact that client-side applications should > not use user-supplied URLs or Properties objects to connect to remote > databases. Those URLs and Properties objects may contain instructions for > tracing network traffic. If the client-side application runs from a more > privileged account than the user, then this could let the user pollute parts > of the directory system to which the user does not normally have > write-access. Client-side applications should vet all user-supplied > directives before establishing connections. > A related MySQL problem is described by [1]. > [1] > https://github.com/apache/security-site/compare/main...raboof:security-site:mysql -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7161) Document the need for client-side applications to vet user-supplied connection directives
[
https://issues.apache.org/jira/browse/DERBY-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840245#comment-17840245
]
Richard N. Hillegas commented on DERBY-7161:
Attaching derby-7161-01-aa-traceFileAttributes.diff. This patch adds some
documentation which warns users about the security implications of the trace
file connection attributes. Also attaching
derby-7161-01-aa-traceFileAttributes.tar, a tarball of corresponding generated
output.
Touches the following files:
{noformat}
M src/adminguide/cadminappsclient.dita
Adds a warning to the Admin Guide's "Accessing the Network Server by using the
network client driver" topic.
M src/devguide/cdevdvlp51654.dita
Adds a warning to the Developer's Guide's "Working with the database connection
URL attributes" topic.
M src/ref/rrefattrib24612.dita
Adds a warning to the Reference Guide's "Setting attributes for the database
connection URL" topic.
M src/security/csecintrosafer.dita
Adds a warning to the Security Guide's "Designing safer Derby applications"
topic.
{noformat}
> Document the need for client-side applications to vet user-supplied
> connection directives
> -
>
> Key: DERBY-7161
> URL: https://issues.apache.org/jira/browse/DERBY-7161
> Project: Derby
> Issue Type: Task
> Components: Documentation, Network Client
>Affects Versions: 10.18.0.0
>Reporter: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7161-01-aa-traceFileAttributes.diff,
> derby-7161-01-aa-traceFileAttributes.tar
>
>
> Somewhere, we should document the fact that client-side applications should
> not use user-supplied URLs or Properties objects to connect to remote
> databases. Those URLs and Properties objects may contain instructions for
> tracing network traffic. If the client-side application runs from a more
> privileged account than the user, then this could let the user pollute parts
> of the directory system to which the user does not normally have
> write-access. Client-side applications should vet all user-supplied
> directives before establishing connections.
> A related MySQL problem is described by [1].
> [1]
> https://github.com/apache/security-site/compare/main...raboof:security-site:mysql
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7161) Document the need for client-side applications to vet user-supplied connection directives
[ https://issues.apache.org/jira/browse/DERBY-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7161: --- Attachment: derby-7161-01-aa-traceFileAttributes.diff > Document the need for client-side applications to vet user-supplied > connection directives > - > > Key: DERBY-7161 > URL: https://issues.apache.org/jira/browse/DERBY-7161 > Project: Derby > Issue Type: Task > Components: Documentation, Network Client >Affects Versions: 10.18.0.0 >Reporter: Richard N. Hillegas >Priority: Major > Attachments: derby-7161-01-aa-traceFileAttributes.diff > > > Somewhere, we should document the fact that client-side applications should > not use user-supplied URLs or Properties objects to connect to remote > databases. Those URLs and Properties objects may contain instructions for > tracing network traffic. If the client-side application runs from a more > privileged account than the user, then this could let the user pollute parts > of the directory system to which the user does not normally have > write-access. Client-side applications should vet all user-supplied > directives before establishing connections. > A related MySQL problem is described by [1]. > [1] > https://github.com/apache/security-site/compare/main...raboof:security-site:mysql -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7162) Update Git mirror for db-derby. Current mirror is out of date, hasn't been updated since 2019
[ https://issues.apache.org/jira/browse/DERBY-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836956#comment-17836956 ] Richard N. Hillegas commented on DERBY-7162: Can you describe the problem you had when trying to build Derby locally? Maybe someone can advise you on how to get over that hurdle. > Update Git mirror for db-derby. Current mirror is out of date, hasn't been > updated since 2019 > - > > Key: DERBY-7162 > URL: https://issues.apache.org/jira/browse/DERBY-7162 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Bob Neugebauer >Priority: Major > > There is an existing GIT mirror for DB-DERBY available at > [https://github.com/apache/derby] however this mirror is out of date. Last > commit was Aug 2019. This mirror is missing all branches and tags that the > derby SVN repo contains. > I had opened an INFRA ticket INFRA-25623 to request an update to git but > Chris said this had to come from the derby maintainers. > I have a project that is using derby, in particular 10.17, and I am looking > for the best way to avoid having our build servers hit ASF frequently to pull > from SVN. Using a git fork would seem the best way to achieve this. > > Thanks, Bob -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7162) Update Git mirror for db-derby. Current mirror is out of date, hasn't been updated since 2019
[ https://issues.apache.org/jira/browse/DERBY-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836955#comment-17836955 ] Richard N. Hillegas commented on DERBY-7162: Linking this issue to DERBY-6645, a previous attempt to create a parallel maven-based build for Derby. If I remember correctly, that attempt foundered on the complexity of message-file generation. Maven-related discussion should be moved to DERBY-6645. I am happy to coach you through a follow-on mavenization effort there. > Update Git mirror for db-derby. Current mirror is out of date, hasn't been > updated since 2019 > - > > Key: DERBY-7162 > URL: https://issues.apache.org/jira/browse/DERBY-7162 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Bob Neugebauer >Priority: Major > > There is an existing GIT mirror for DB-DERBY available at > [https://github.com/apache/derby] however this mirror is out of date. Last > commit was Aug 2019. This mirror is missing all branches and tags that the > derby SVN repo contains. > I had opened an INFRA ticket INFRA-25623 to request an update to git but > Chris said this had to come from the derby maintainers. > I have a project that is using derby, in particular 10.17, and I am looking > for the best way to avoid having our build servers hit ASF frequently to pull > from SVN. Using a git fork would seem the best way to achieve this. > > Thanks, Bob -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7161) Document the need for client-side applications to vet user-supplied connection directives
[ https://issues.apache.org/jira/browse/DERBY-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834712#comment-17834712 ] Richard N. Hillegas commented on DERBY-7161: Those sound like good places to add some verbiage too. Thanks > Document the need for client-side applications to vet user-supplied > connection directives > - > > Key: DERBY-7161 > URL: https://issues.apache.org/jira/browse/DERBY-7161 > Project: Derby > Issue Type: Task > Components: Documentation, Network Client >Affects Versions: 10.18.0.0 >Reporter: Richard N. Hillegas >Priority: Major > > Somewhere, we should document the fact that client-side applications should > not use user-supplied URLs or Properties objects to connect to remote > databases. Those URLs and Properties objects may contain instructions for > tracing network traffic. If the client-side application runs from a more > privileged account than the user, then this could let the user pollute parts > of the directory system to which the user does not normally have > write-access. Client-side applications should vet all user-supplied > directives before establishing connections. > A related MySQL problem is described by [1]. > [1] > https://github.com/apache/security-site/compare/main...raboof:security-site:mysql -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7161) Document the need for client-side applications to vet user-supplied connection directives
[ https://issues.apache.org/jira/browse/DERBY-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834543#comment-17834543 ] Richard N. Hillegas commented on DERBY-7161: Hi Bryan, I suppose that something should be said in the Server Guide and the Security Guide. What are your thoughts? > Document the need for client-side applications to vet user-supplied > connection directives > - > > Key: DERBY-7161 > URL: https://issues.apache.org/jira/browse/DERBY-7161 > Project: Derby > Issue Type: Task > Components: Documentation, Network Client >Affects Versions: 10.18.0.0 >Reporter: Richard N. Hillegas >Priority: Major > > Somewhere, we should document the fact that client-side applications should > not use user-supplied URLs or Properties objects to connect to remote > databases. Those URLs and Properties objects may contain instructions for > tracing network traffic. If the client-side application runs from a more > privileged account than the user, then this could let the user pollute parts > of the directory system to which the user does not normally have > write-access. Client-side applications should vet all user-supplied > directives before establishing connections. > A related MySQL problem is described by [1]. > [1] > https://github.com/apache/security-site/compare/main...raboof:security-site:mysql -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7162) Update Git mirror for db-derby. Current mirror is out of date, hasn't been updated since 2019
[ https://issues.apache.org/jira/browse/DERBY-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829946#comment-17829946 ] Richard N. Hillegas commented on DERBY-7162: Apache Derby is an old project maintained by old engineers who use old tools. Our code is maintained in subversion. None of the active committers accept contributions via git. I don't remember who created this git mirror. Clearly no-one volunteered to keep it evergreen. That said, I have no objection to periodic, automatic updates of this git mirror provided that 1) I don't have to do anything more than make one request to INFRA to make it so. 2) It is understood that the Derby project considers this to be a read-only mirror. 3) It is further understood that the Derby project will ignore this mirror and all forks from it. If that is an acceptable situation, then I will need someone to tell me what I need to do to enable it. -Rick > Update Git mirror for db-derby. Current mirror is out of date, hasn't been > updated since 2019 > - > > Key: DERBY-7162 > URL: https://issues.apache.org/jira/browse/DERBY-7162 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Bob Neugebauer >Priority: Major > > There is an existing GIT mirror for DB-DERBY available at > [https://github.com/apache/derby] however this mirror is out of date. Last > commit was Aug 2019. This mirror is missing all branches and tags that the > derby SVN repo contains. > I had opened an INFRA ticket INFRA-25623 to request an update to git but > Chris said this had to come from the derby maintainers. > I have a project that is using derby, in particular 10.17, and I am looking > for the best way to avoid having our build servers hit ASF frequently to pull > from SVN. Using a git fork would seem the best way to achieve this. > > Thanks, Bob -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7161) Document the need for client-side applications to vet user-supplied connection directives
[ https://issues.apache.org/jira/browse/DERBY-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7161: --- Component/s: Documentation > Document the need for client-side applications to vet user-supplied > connection directives > - > > Key: DERBY-7161 > URL: https://issues.apache.org/jira/browse/DERBY-7161 > Project: Derby > Issue Type: Task > Components: Documentation, Network Client >Affects Versions: 10.18.0.0 >Reporter: Richard N. Hillegas >Priority: Major > > Somewhere, we should document the fact that client-side applications should > not use user-supplied URLs or Properties objects to connect to remote > databases. Those URLs and Properties objects may contain instructions for > tracing network traffic. If the client-side application runs from a more > privileged account than the user, then this could let the user pollute parts > of the directory system to which the user does not normally have > write-access. Client-side applications should vet all user-supplied > directives before establishing connections. > A related MySQL problem is described by [1]. > [1] > https://github.com/apache/security-site/compare/main...raboof:security-site:mysql -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DERBY-7161) Document the need for client-side applications to vet user-supplied connection directives
Richard N. Hillegas created DERBY-7161: -- Summary: Document the need for client-side applications to vet user-supplied connection directives Key: DERBY-7161 URL: https://issues.apache.org/jira/browse/DERBY-7161 Project: Derby Issue Type: Task Components: Network Client Affects Versions: 10.18.0.0 Reporter: Richard N. Hillegas Somewhere, we should document the fact that client-side applications should not use user-supplied URLs or Properties objects to connect to remote databases. Those URLs and Properties objects may contain instructions for tracing network traffic. If the client-side application runs from a more privileged account than the user, then this could let the user pollute parts of the directory system to which the user does not normally have write-access. Client-side applications should vet all user-supplied directives before establishing connections. A related MySQL problem is described by [1]. [1] https://github.com/apache/security-site/compare/main...raboof:security-site:mysql -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DERBY-7160) Why do we see test failure/regression cause ERROR 22003: The resulting value is outside the range for the data type DECIMAL/NUMERIC(30,15)
[
https://issues.apache.org/jira/browse/DERBY-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard N. Hillegas closed DERBY-7160.
--
> Why do we see test failure/regression cause ERROR 22003: The resulting value
> is outside the range for the data type DECIMAL/NUMERIC(30,15)
> --
>
> Key: DERBY-7160
> URL: https://issues.apache.org/jira/browse/DERBY-7160
> Project: Derby
> Issue Type: Bug
>Affects Versions: 10.17.1.0
>Reporter: Scott Marlow
>Priority: Major
> Fix For: 10.17.1.1
>
> Attachments: DERBY_7160-1.java, DERBY_7160.java
>
>
> This may be a regression or maybe a design change, not sure of which as the
> same tests pass for us on Java SE 11/17 with
> https://dlcdn.apache.org//db/derby/db-derby-10.15.2.0/db-derby-10.15.2.0-bin.zip.
> We are seeing a JDBC TCK test failure (Jakarta EE 10 TCK) when testing
> against [https://db.apache.org/derby/releases/release-10_17_1_0.cgi] on java
> 21 with the external project [https://github.com/wildfly/wildfly] that I
> contribute to.
> I marked this issue as a bug but I really have no idea where the bug is. The
> JDBC test that is failing is
> [https://github.com/jakartaee/platform-tck/blob/10.0.x/src/com/sun/ts/tests/jdbc/ee/callStmt/callStmt16/callStmtClient16.java#L968]
> when run on Java 21 with 10.17.1.0.
> The failure is:
> {quote}
> Caused by: ERROR 22003: The resulting value is outside the range for the data
> type DECIMAL/NUMERIC(30,15).
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientStatement.completeExecute(ClientStatement.java:1868)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(NetStatementReply.java:323)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatementReply.readExecuteCall(NetStatementReply.java:107)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.StatementReply.readExecuteCall(StatementReply.java:84)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatement.readExecuteCall_(NetStatement.java:193)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientStatement.readExecuteCall(ClientStatement.java:1831)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.flowExecute(ClientPreparedStatement.java:2180)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.executeUpdateX(ClientPreparedStatement.java:410)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.executeUpdate(ClientPreparedStatement.java:396)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) ... 16 more
> {quote}
>
> The called stored procedure source is at
> https://github.com/jakartaee/platform-tck/blob/10.0.x/sql/derby/derby.ddl.sprocs.sql#L224
> which contains:
> {quote}
> create procedure Decimal_In_Max (in MAX_PARAM DECIMAL(30,15)) language java
> external name 'com.sun.ts.lib.tests.jdbc.CS_Procs.Decimal_In_Max' parameter
> style java;
> {quote}
> The referenced com.sun.ts.lib.tests.jdbc.CS_Procs.Decimal_In_Max contains:
> {code}
> Connection con = DriverManager.getConnection("jdbc:default:connection");
> PreparedStatement ps = con
> .prepareStatement("update Decimal_Tab set MAX_VAL=?");
> ps.setBigDecimal(1, max_param);
> ps.executeUpdate();
> ps.close();
> ps = null;
> con.close();
> con = null;
> }
> {code}
> More details are being added soon ...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (DERBY-7160) Why do we see test failure/regression cause ERROR 22003: The resulting value is outside the range for the data type DECIMAL/NUMERIC(30,15)
[
https://issues.apache.org/jira/browse/DERBY-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard N. Hillegas resolved DERBY-7160.
Resolution: Not A Problem
Resolving this issue. I see no evidence of a regression in Derby's behavior.
> Why do we see test failure/regression cause ERROR 22003: The resulting value
> is outside the range for the data type DECIMAL/NUMERIC(30,15)
> --
>
> Key: DERBY-7160
> URL: https://issues.apache.org/jira/browse/DERBY-7160
> Project: Derby
> Issue Type: Bug
>Affects Versions: 10.17.1.0
>Reporter: Scott Marlow
>Priority: Major
> Fix For: 10.17.1.1
>
> Attachments: DERBY_7160-1.java, DERBY_7160.java
>
>
> This may be a regression or maybe a design change, not sure of which as the
> same tests pass for us on Java SE 11/17 with
> https://dlcdn.apache.org//db/derby/db-derby-10.15.2.0/db-derby-10.15.2.0-bin.zip.
> We are seeing a JDBC TCK test failure (Jakarta EE 10 TCK) when testing
> against [https://db.apache.org/derby/releases/release-10_17_1_0.cgi] on java
> 21 with the external project [https://github.com/wildfly/wildfly] that I
> contribute to.
> I marked this issue as a bug but I really have no idea where the bug is. The
> JDBC test that is failing is
> [https://github.com/jakartaee/platform-tck/blob/10.0.x/src/com/sun/ts/tests/jdbc/ee/callStmt/callStmt16/callStmtClient16.java#L968]
> when run on Java 21 with 10.17.1.0.
> The failure is:
> {quote}
> Caused by: ERROR 22003: The resulting value is outside the range for the data
> type DECIMAL/NUMERIC(30,15).
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientStatement.completeExecute(ClientStatement.java:1868)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(NetStatementReply.java:323)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatementReply.readExecuteCall(NetStatementReply.java:107)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.StatementReply.readExecuteCall(StatementReply.java:84)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatement.readExecuteCall_(NetStatement.java:193)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientStatement.readExecuteCall(ClientStatement.java:1831)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.flowExecute(ClientPreparedStatement.java:2180)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.executeUpdateX(ClientPreparedStatement.java:410)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.executeUpdate(ClientPreparedStatement.java:396)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) ... 16 more
> {quote}
>
> The called stored procedure source is at
> https://github.com/jakartaee/platform-tck/blob/10.0.x/sql/derby/derby.ddl.sprocs.sql#L224
> which contains:
> {quote}
> create procedure Decimal_In_Max (in MAX_PARAM DECIMAL(30,15)) language java
> external name 'com.sun.ts.lib.tests.jdbc.CS_Procs.Decimal_In_Max' parameter
> style java;
> {quote}
> The referenced com.sun.ts.lib.tests.jdbc.CS_Procs.Decimal_In_Max contains:
> {code}
> Connection con = DriverManager.getConnection("jdbc:default:connection");
> PreparedStatement ps = con
> .prepareStatement("update Decimal_Tab set MAX_VAL=?");
> ps.setBigDecimal(1, max_param);
> ps.executeUpdate();
> ps.close();
> ps = null;
> con.close();
> con = null;
> }
> {code}
> More details are being added soon ...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DERBY-7160) Why do we see test failure/regression cause ERROR 22003: The resulting value is outside the range for the data type DECIMAL/NUMERIC(30,15)
[
https://issues.apache.org/jira/browse/DERBY-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828509#comment-17828509
]
Richard N. Hillegas commented on DERBY-7160:
I modified DERBY_7160. Now it tests Derby's behavior on the String values
Float.MAX_VALUE.toString(), 1.0E15, 9.999E14. Here is the program's
behavior on Java 11, 17, and 21 and Derby 10.15.2.0 and 10.17.1.0:
{noformat}
mainline (21) > . switchVM 11
mainline (11) > runjavaExperimental
/Users/rhillegas/derby/upgradeReleases/10.15.2.0 DERBY_7160
Java 11, Derby 10.15
Experiment Float.MAX_VALUE : Float = 3.4028235E38...
Caught exception java.sql.SQLDataException with message: The resulting
value is outside the range for the data type DECIMAL/NUMERIC(30,15).
Experiment 1.0E15 : Float = 9.999E14...
DECIMAL_IN_MAX received value 99986991104.000
Experiment succeeded.
Experiment 9.999E14 : Float = 9.999E14...
DECIMAL_IN_MAX received value 99986991104.000
Experiment succeeded.
mainline (11) > . switchVM 17
mainline (17) > runjavaExperimental
/Users/rhillegas/derby/upgradeReleases/10.15.2.0 DERBY_7160
Java 17, Derby 10.15
Experiment Float.MAX_VALUE : Float = 3.4028235E38...
Caught exception java.sql.SQLDataException with message: The resulting
value is outside the range for the data type DECIMAL/NUMERIC(30,15).
Experiment 1.0E15 : Float = 9.999E14...
DECIMAL_IN_MAX received value 99986991104.000
Experiment succeeded.
Experiment 9.999E14 : Float = 9.999E14...
DECIMAL_IN_MAX received value 99986991104.000
Experiment succeeded.
mainline (17) > . switchVM 21
mainline (21) > runjavaExperimental
/Users/rhillegas/derby/upgradeReleases/10.15.2.0 DERBY_7160
Java 21, Derby 10.15
Experiment Float.MAX_VALUE : Float = 3.4028235E38...
Caught exception java.sql.SQLDataException with message: The resulting
value is outside the range for the data type DECIMAL/NUMERIC(30,15).
Experiment 1.0E15 : Float = 1.0E15...
DECIMAL_IN_MAX received value 99986991104.000
Experiment succeeded.
Experiment 9.999E14 : Float = 1.0E15...
DECIMAL_IN_MAX received value 99986991104.000
Experiment succeeded.
mainline (21) > runjavaExperimental
/Users/rhillegas/derby/upgradeReleases/10.17.1.0 DERBY_7160
Java 21, Derby 10.17
Experiment Float.MAX_VALUE : Float = 3.4028235E38...
Caught exception java.sql.SQLDataException with message: The resulting
value is outside the range for the data type DECIMAL/NUMERIC(30,15).
Experiment 1.0E15 : Float = 1.0E15...
DECIMAL_IN_MAX received value 99986991104.000
Experiment succeeded.
Experiment 9.999E14 : Float = 1.0E15...
DECIMAL_IN_MAX received value 99986991104.000
Experiment succeeded.
{noformat}
Derby's behavior does not change across different JVMs and different Derby
releases. The only change is the behavior of Float.toString(), which changed in
Java 21.
> Why do we see test failure/regression cause ERROR 22003: The resulting value
> is outside the range for the data type DECIMAL/NUMERIC(30,15)
> --
>
> Key: DERBY-7160
> URL: https://issues.apache.org/jira/browse/DERBY-7160
> Project: Derby
> Issue Type: Bug
>Affects Versions: 10.17.1.0
>Reporter: Scott Marlow
>Priority: Major
> Fix For: 10.17.1.1
>
> Attachments: DERBY_7160-1.java, DERBY_7160.java
>
>
> This may be a regression or maybe a design change, not sure of which as the
> same tests pass for us on Java SE 11/17 with
> https://dlcdn.apache.org//db/derby/db-derby-10.15.2.0/db-derby-10.15.2.0-bin.zip.
> We are seeing a JDBC TCK test failure (Jakarta EE 10 TCK) when testing
> against [https://db.apache.org/derby/releases/release-10_17_1_0.cgi] on java
> 21 with the external project [https://github.com/wildfly/wildfly] that I
> contribute to.
> I marked this issue as a bug but I really have no idea where the bug is. The
> JDBC test that is failing is
> [https://github.com/jakartaee/platform-tck/blob/10.0.x/src/com/sun/ts/tests/jdbc/ee/callStmt/callStmt16/callStmtClient16.java#L968]
> when run on Java 21 with 10.17.1.0.
> The failure is:
> {quote}
> Caused by: ERROR 22003: The resulting value is outside the range for the data
> type DECIMAL/NUMERIC(30,15).
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientStatement.completeExecute(ClientStatement.java:1868)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
>
[jira] [Updated] (DERBY-7160) Why do we see test failure/regression cause ERROR 22003: The resulting value is outside the range for the data type DECIMAL/NUMERIC(30,15)
[
https://issues.apache.org/jira/browse/DERBY-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard N. Hillegas updated DERBY-7160:
---
Attachment: DERBY_7160-1.java
> Why do we see test failure/regression cause ERROR 22003: The resulting value
> is outside the range for the data type DECIMAL/NUMERIC(30,15)
> --
>
> Key: DERBY-7160
> URL: https://issues.apache.org/jira/browse/DERBY-7160
> Project: Derby
> Issue Type: Bug
>Affects Versions: 10.17.1.0
>Reporter: Scott Marlow
>Priority: Major
> Fix For: 10.17.1.1
>
> Attachments: DERBY_7160-1.java, DERBY_7160.java
>
>
> This may be a regression or maybe a design change, not sure of which as the
> same tests pass for us on Java SE 11/17 with
> https://dlcdn.apache.org//db/derby/db-derby-10.15.2.0/db-derby-10.15.2.0-bin.zip.
> We are seeing a JDBC TCK test failure (Jakarta EE 10 TCK) when testing
> against [https://db.apache.org/derby/releases/release-10_17_1_0.cgi] on java
> 21 with the external project [https://github.com/wildfly/wildfly] that I
> contribute to.
> I marked this issue as a bug but I really have no idea where the bug is. The
> JDBC test that is failing is
> [https://github.com/jakartaee/platform-tck/blob/10.0.x/src/com/sun/ts/tests/jdbc/ee/callStmt/callStmt16/callStmtClient16.java#L968]
> when run on Java 21 with 10.17.1.0.
> The failure is:
> {quote}
> Caused by: ERROR 22003: The resulting value is outside the range for the data
> type DECIMAL/NUMERIC(30,15).
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientStatement.completeExecute(ClientStatement.java:1868)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(NetStatementReply.java:323)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatementReply.readExecuteCall(NetStatementReply.java:107)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.StatementReply.readExecuteCall(StatementReply.java:84)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatement.readExecuteCall_(NetStatement.java:193)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientStatement.readExecuteCall(ClientStatement.java:1831)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.flowExecute(ClientPreparedStatement.java:2180)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.executeUpdateX(ClientPreparedStatement.java:410)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.executeUpdate(ClientPreparedStatement.java:396)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) ... 16 more
> {quote}
>
> The called stored procedure source is at
> https://github.com/jakartaee/platform-tck/blob/10.0.x/sql/derby/derby.ddl.sprocs.sql#L224
> which contains:
> {quote}
> create procedure Decimal_In_Max (in MAX_PARAM DECIMAL(30,15)) language java
> external name 'com.sun.ts.lib.tests.jdbc.CS_Procs.Decimal_In_Max' parameter
> style java;
> {quote}
> The referenced com.sun.ts.lib.tests.jdbc.CS_Procs.Decimal_In_Max contains:
> {code}
> Connection con = DriverManager.getConnection("jdbc:default:connection");
> PreparedStatement ps = con
> .prepareStatement("update Decimal_Tab set MAX_VAL=?");
> ps.setBigDecimal(1, max_param);
> ps.executeUpdate();
> ps.close();
> ps = null;
> con.close();
> con = null;
> }
> {code}
> More details are being added soon ...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DERBY-7160) Why do we see test failure/regression cause ERROR 22003: The resulting value is outside the range for the data type DECIMAL/NUMERIC(30,15)
[
https://issues.apache.org/jira/browse/DERBY-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828124#comment-17828124
]
Richard N. Hillegas commented on DERBY-7160:
I don't know of any changes to Derby which would be responsible for this
result. It is hard to make much headway on narrowing down the problem until we
know what the suspect Float value is.
The variable naming in callStmtClient16.testSetObject177() suggests that the
procedure might be trying to stuff a Float.MAX_VALUE into an input procedure
argument of type DECIMAL(30,15).
I am attaching a program (DERBY_7160) which runs that experiment. I compiled
the program with JDK 11. Since Float.MAX_VALUE is outside the range of
DECIMAL(30,15), the program fails with the following error:
{noformat}
Exception in thread "main" java.sql.SQLDataException: The resulting value is
outside the range for the data type DECIMAL/NUMERIC(30,15).
at
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:84)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:230)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(TransactionResourceImpl.java:431)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(TransactionResourceImpl.java:360)
at
org.apache.derby.impl.jdbc.EmbedConnection.handleException(EmbedConnection.java:2405)
at
org.apache.derby.impl.jdbc.ConnectionChild.handleException(ConnectionChild.java:88)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1436)
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(EmbedPreparedStatement.java:1709)
at
org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(EmbedCallableStatement.java:134)
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(EmbedPreparedStatement.java:1394)
at DERBY_7160.main(DERBY_7160.java:23)
Caused by: ERROR 22003: The resulting value is outside the range for the data
type DECIMAL/NUMERIC(30,15).
at
org.apache.derby.shared.common.error.StandardException.newException(StandardException.java:300)
at
org.apache.derby.shared.common.error.StandardException.newException(StandardException.java:295)
at org.apache.derby.iapi.types.SQLDecimal.setWidth(SQLDecimal.java:991)
at
org.apache.derby.exe.ac3ea3c0fbx018ex53bfx4594x075b77200.g0(Unknown Source)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.apache.derby.impl.services.reflect.ReflectMethod.invoke(ReflectMethod.java:46)
at
org.apache.derby.impl.sql.execute.CallStatementResultSet.open(CallStatementResultSet.java:75)
at
org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(GenericPreparedStatement.java:472)
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:351)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1344)
... 4 more
{noformat}
The experiment fails on the following platforms:
{noformat}
JDKDERBY
11 10.15.2.0
17 10.15.2.0
21 10.15.2.0
21 10.17.1.0
{noformat}
> Why do we see test failure/regression cause ERROR 22003: The resulting value
> is outside the range for the data type DECIMAL/NUMERIC(30,15)
> --
>
> Key: DERBY-7160
> URL: https://issues.apache.org/jira/browse/DERBY-7160
> Project: Derby
> Issue Type: Bug
>Affects Versions: 10.17.1.0
>Reporter: Scott Marlow
>Priority: Major
> Fix For: 10.17.1.1
>
> Attachments: DERBY_7160.java
>
>
> This may be a regression or maybe a design change, not sure of which as the
> same tests pass for us on Java SE 11/17 with
> https://dlcdn.apache.org//db/derby/db-derby-10.15.2.0/db-derby-10.15.2.0-bin.zip.
> We are seeing a JDBC TCK test failure (Jakarta EE 10 TCK) when testing
> against [https://db.apache.org/derby/releases/release-10_17_1_0.cgi] on java
> 21 with the external project [https://github.com/wildfly/wildfly] that I
> contribute to.
> I marked this issue as a bug but I really have no idea where the bug is. The
> JDBC test that is failing is
>
[jira] [Updated] (DERBY-7160) Why do we see test failure/regression cause ERROR 22003: The resulting value is outside the range for the data type DECIMAL/NUMERIC(30,15)
[
https://issues.apache.org/jira/browse/DERBY-7160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard N. Hillegas updated DERBY-7160:
---
Attachment: DERBY_7160.java
> Why do we see test failure/regression cause ERROR 22003: The resulting value
> is outside the range for the data type DECIMAL/NUMERIC(30,15)
> --
>
> Key: DERBY-7160
> URL: https://issues.apache.org/jira/browse/DERBY-7160
> Project: Derby
> Issue Type: Bug
>Affects Versions: 10.17.1.0
>Reporter: Scott Marlow
>Priority: Major
> Fix For: 10.17.1.1
>
> Attachments: DERBY_7160.java
>
>
> This may be a regression or maybe a design change, not sure of which as the
> same tests pass for us on Java SE 11/17 with
> https://dlcdn.apache.org//db/derby/db-derby-10.15.2.0/db-derby-10.15.2.0-bin.zip.
> We are seeing a JDBC TCK test failure (Jakarta EE 10 TCK) when testing
> against [https://db.apache.org/derby/releases/release-10_17_1_0.cgi] on java
> 21 with the external project [https://github.com/wildfly/wildfly] that I
> contribute to.
> I marked this issue as a bug but I really have no idea where the bug is. The
> JDBC test that is failing is
> [https://github.com/jakartaee/platform-tck/blob/10.0.x/src/com/sun/ts/tests/jdbc/ee/callStmt/callStmt16/callStmtClient16.java#L968]
> when run on Java 21 with 10.17.1.0.
> The failure is:
> {quote}
> Caused by: ERROR 22003: The resulting value is outside the range for the data
> type DECIMAL/NUMERIC(30,15).
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientStatement.completeExecute(ClientStatement.java:1868)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(NetStatementReply.java:323)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatementReply.readExecuteCall(NetStatementReply.java:107)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.StatementReply.readExecuteCall(StatementReply.java:84)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.net.NetStatement.readExecuteCall_(NetStatement.java:193)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientStatement.readExecuteCall(ClientStatement.java:1831)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.flowExecute(ClientPreparedStatement.java:2180)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.executeUpdateX(ClientPreparedStatement.java:410)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) at
> org.apache.derby.client//org.apache.derby.client.am.ClientPreparedStatement.executeUpdate(ClientPreparedStatement.java:396)
> \u001b[0m\u001b[0m12:39:19,524 INFO [stdout] (Thread-69) ... 16 more
> {quote}
>
> The called stored procedure source is at
> https://github.com/jakartaee/platform-tck/blob/10.0.x/sql/derby/derby.ddl.sprocs.sql#L224
> which contains:
> {quote}
> create procedure Decimal_In_Max (in MAX_PARAM DECIMAL(30,15)) language java
> external name 'com.sun.ts.lib.tests.jdbc.CS_Procs.Decimal_In_Max' parameter
> style java;
> {quote}
> The referenced com.sun.ts.lib.tests.jdbc.CS_Procs.Decimal_In_Max contains:
> {code}
> Connection con = DriverManager.getConnection("jdbc:default:connection");
> PreparedStatement ps = con
> .prepareStatement("update Decimal_Tab set MAX_VAL=?");
> ps.setBigDecimal(1, max_param);
> ps.executeUpdate();
> ps.close();
> ps = null;
> con.close();
> con = null;
> }
> {code}
> More details are being added soon ...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationSchemeImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822865#comment-17822865 ] Richard N. Hillegas commented on DERBY-7147: "It is showing as affected from "10.1.1.0 Up to (excluding) 10.17.1.0" This is, technically, an accurate statement about the OFFICIAL derby releases. You must build your own UNOFFICIAL release if you need a fix-bearing set of Derby jars which run on Java LTS versions 8, 11, or 17. Your processes may need some work in order to accommodate unofficial software distributions. > LDAP injection vulnerability in LDAPAuthenticationSchemeImpl > > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0 > > Attachments: LDAPauthenticationVulnerability.pdf, > derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationSchemeImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822674#comment-17822674 ] Richard N. Hillegas edited comment on DERBY-7147 at 3/1/24 5:52 PM: I have verified that the fix has been applied to the head of the 10.14 branch: https://svn.apache.org/repos/asf/db/derby/code/branches/10.14 You can verify this yourself by looking for the string "7147" in https://svn.apache.org/repos/asf/db/derby/code/branches/10.14/java/engine/org/apache/derby/impl/jdbc/authentication/LDAPAuthenticationSchemeImpl.java There is no branch named 10.14.3. Branch names are two part ids which have the form majorNumber.minorNumber. To build a fix-bearing release off the head of the 10.14 branch, see the instructions in my comment dated 2024-01-24. Substitute "10.14" for every occurrence of "10.16" in those instructions. was (Author: rhillegas): I have verified that the fix has been applied to the head of the 10.14 branch: https://svn.apache.org/repos/asf/db/derby/code/branches/10.14 You can verify this yourself by looking for the string "DERBY-7147" in https://svn.apache.org/repos/asf/db/derby/code/branches/10.14/java/engine/org/apache/derby/impl/jdbc/authentication/LDAPAuthenticationSchemeImpl.java There is no branch named 10.14.3. Branch names are two part ids which have the form majorNumber.minorNumber. To build a fix-bearing release off the head of the 10.14 branch, see the instructions in my comment dated 2024-01-24. Substitute "10.14" for every occurrence of "10.16" in those instructions. > LDAP injection vulnerability in LDAPAuthenticationSchemeImpl > > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0 > > Attachments: LDAPauthenticationVulnerability.pdf, > derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationSchemeImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822674#comment-17822674 ] Richard N. Hillegas commented on DERBY-7147: I have verified that the fix has been applied to the head of the 10.14 branch: https://svn.apache.org/repos/asf/db/derby/code/branches/10.14 You can verify this yourself by looking for the string "DERBY-7147" in https://svn.apache.org/repos/asf/db/derby/code/branches/10.14/java/engine/org/apache/derby/impl/jdbc/authentication/LDAPAuthenticationSchemeImpl.java There is no branch named 10.14.3. Branch names are two part ids which have the form majorNumber.minorNumber. To build a fix-bearing release off the head of the 10.14 branch, see the instructions in my comment dated 2024-01-24. Substitute "10.14" for every occurrence of "10.16" in those instructions. > LDAP injection vulnerability in LDAPAuthenticationSchemeImpl > > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0 > > Attachments: LDAPauthenticationVulnerability.pdf, > derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7159) Make it possible to build and test Derby with Open JDK 22
[ https://issues.apache.org/jira/browse/DERBY-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819020#comment-17819020 ] Richard N. Hillegas commented on DERBY-7159: Derby built cleanly (including javadoc) with the first release candidate for Open JDK 22 (build 22+36-2370). The tests ran cleanly with both the classpath and modulepath. > Make it possible to build and test Derby with Open JDK 22 > - > > Key: DERBY-7159 > URL: https://issues.apache.org/jira/browse/DERBY-7159 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.18.0.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7159-01-aa-addJdk22VM.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7159) Make it possible to build and test Derby with Open JDK 22
[ https://issues.apache.org/jira/browse/DERBY-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17811657#comment-17811657 ] Richard N. Hillegas commented on DERBY-7159: Derby built cleanly (including javadoc) with Open JDK build 22-ea+33-2356. The tests ran cleanly with both the classpath and modulepath. > Make it possible to build and test Derby with Open JDK 22 > - > > Key: DERBY-7159 > URL: https://issues.apache.org/jira/browse/DERBY-7159 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.18.0.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7159-01-aa-addJdk22VM.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationSchemeImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805250#comment-17805250 ] Richard N. Hillegas commented on DERBY-7147: No one has volunteered to manage a fix-bearing release built off the 10.16 branch. As stated above in previous comments, you will need to build your own 10.16 jar files. Instructions for building 10.16 can be found here: https://svn.apache.org/repos/asf/db/derby/code/branches/10.16/BUILDING.html You will need the Derby source from the head of the 10.16 branch: https://svn.apache.org/repos/asf/db/derby/code/branches/10.16/ Subversion is the tool you will need to grab that source. > LDAP injection vulnerability in LDAPAuthenticationSchemeImpl > > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0 > > Attachments: LDAPauthenticationVulnerability.pdf, > derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationSchemeImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17802280#comment-17802280 ] Richard N. Hillegas commented on DERBY-7147: I have checked the head of the 10.14 branch and verified that the fix was applied there. I recently updated the Apache CVE website to include more detailed version ranges. Those changes are now reflected at https://www.cve.org/CVERecord?id=CVE-2022-46337 I cannot speculate about why your scanners are raising this alarm. > LDAP injection vulnerability in LDAPAuthenticationSchemeImpl > > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0 > > Attachments: LDAPauthenticationVulnerability.pdf, > derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7159) Make it possible to build and test Derby with Open JDK 22
[
https://issues.apache.org/jira/browse/DERBY-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17802276#comment-17802276
]
Richard N. Hillegas commented on DERBY-7159:
Attaching derby-7159-01-aa-addJdk22VM.diff. This patch adds a jdk22 vm to the
tests.
Touches the following file:
{noformat}
M
java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyTesting.jar.lastcontents
M
java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyTesting.jar.lastcontents
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/harness/JavaVersionHolder.java
A
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/harness/jdk122.java
{noformat}
> Make it possible to build and test Derby with Open JDK 22
> -
>
> Key: DERBY-7159
> URL: https://issues.apache.org/jira/browse/DERBY-7159
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Affects Versions: 10.18.0.0
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7159-01-aa-addJdk22VM.diff
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7159) Make it possible to build and test Derby with Open JDK 22
[ https://issues.apache.org/jira/browse/DERBY-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7159: --- Attachment: derby-7159-01-aa-addJdk22VM.diff > Make it possible to build and test Derby with Open JDK 22 > - > > Key: DERBY-7159 > URL: https://issues.apache.org/jira/browse/DERBY-7159 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.18.0.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7159-01-aa-addJdk22VM.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationSchemeImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799918#comment-17799918 ] Richard N. Hillegas commented on DERBY-7147: I am mystified by the high rating which NVD analysts gave to this minor security issue: https://nvd.nist.gov/vuln/detail/CVE-2022-46337 There are no plans to produce patch-bearing official releases for LTS Java versions 8, 11, or 17. Users who must remain on those Java versions will need to build their own Derby jars from, respectively, the heads of the 10.14, 10.15, and 10.16 branches. > LDAP injection vulnerability in LDAPAuthenticationSchemeImpl > > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0 > > Attachments: LDAPauthenticationVulnerability.pdf, > derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationSchemeImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799544#comment-17799544 ] Richard N. Hillegas commented on DERBY-7147: The patch was backported to the 10.16, 10.15, and 10.14 branches, which correspond, respectively with LTS Java versions 17, 11, and 8. For those branches and Java versions, no one has volunteered to manage an official release which includes this fix. > LDAP injection vulnerability in LDAPAuthenticationSchemeImpl > > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0 > > Attachments: LDAPauthenticationVulnerability.pdf, > derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DERBY-7158) ArrayIndexOutOfBoundsException when connecting to Embedded Derby
[
https://issues.apache.org/jira/browse/DERBY-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard N. Hillegas closed DERBY-7158.
--
> ArrayIndexOutOfBoundsException when connecting to Embedded Derby
>
>
> Key: DERBY-7158
> URL: https://issues.apache.org/jira/browse/DERBY-7158
> Project: Derby
> Issue Type: Bug
>Affects Versions: 10.14.2.0
>Reporter: Yuliana Ganchevska
>Priority: Major
> Fix For: 10.14.2.0
>
>
> Hello,
> our project is using Embedded Derby 10.14.2 with Java 11. A client recently
> complained they can't connect to the DB and it seems the DB is corrupted. At
> the time the issue happened they said the only change they made was to
> increase the memory. When the application is trying to connect to the DB, it
> throws the following exception:
> {code:java}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: Index -1 out of bounds
> for length 28
> at org.apache.derby.impl.store.raw.data.BasePage.getHeaderAtSlot(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.data.BasePage.setDeleteStatus(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at
> org.apache.derby.impl.store.raw.data.CachedPage.setDeleteStatus(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at
> org.apache.derby.impl.store.raw.data.StoredPage.setDeleteStatus(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.data.InsertOperation.undoMe(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.data.LogicalUndoOperation.doMe(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.log.FileLogger.logAndUndo(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.xact.Xact.logAndUndo(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.log.FileLogger.undo(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.xact.Xact.abort(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at
> org.apache.derby.impl.store.raw.xact.XactFactory.rollbackAllTransactions(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.log.LogToFile.recover(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.FileMonitor.startModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at
> org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.access.RAMAccessManager$5.run(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
> at
> org.apache.derby.impl.store.access.RAMAccessManager.bootServiceModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.FileMonitor.startModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at
> org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.db.BasicDatabase$5.run(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
> at org.apache.derby.impl.db.BasicDatabase.bootServiceModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at
> org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService(Unknown
>
[jira] [Commented] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationSchemeImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17797959#comment-17797959 ] Richard N. Hillegas commented on DERBY-7147: The patch has been backported to the 10.14 branch. If you build Derby jars from the head of that branch, you will have a version of Derby which includes the fix and which runs on Java 8. > LDAP injection vulnerability in LDAPAuthenticationSchemeImpl > > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0 > > Attachments: LDAPauthenticationVulnerability.pdf, > derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7159) Make it possible to build and test Derby with Open JDK 22
[ https://issues.apache.org/jira/browse/DERBY-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796943#comment-17796943 ] Richard N. Hillegas commented on DERBY-7159: Derby builds (including javadoc) and tests cleanly with Open JDK 22 build 22-ea+27-2262. > Make it possible to build and test Derby with Open JDK 22 > - > > Key: DERBY-7159 > URL: https://issues.apache.org/jira/browse/DERBY-7159 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.18.0.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7159) Make it possible to build and test Derby with Open JDK 22
[ https://issues.apache.org/jira/browse/DERBY-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7159: --- Component/s: Build tools Urgency: Normal Affects Version/s: 10.18.0.0 > Make it possible to build and test Derby with Open JDK 22 > - > > Key: DERBY-7159 > URL: https://issues.apache.org/jira/browse/DERBY-7159 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.18.0.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DERBY-7159) Make it possible to build and test Derby with Open JDK 22
Richard N. Hillegas created DERBY-7159: -- Summary: Make it possible to build and test Derby with Open JDK 22 Key: DERBY-7159 URL: https://issues.apache.org/jira/browse/DERBY-7159 Project: Derby Issue Type: Task Reporter: Richard N. Hillegas -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (DERBY-7159) Make it possible to build and test Derby with Open JDK 22
[ https://issues.apache.org/jira/browse/DERBY-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas reassigned DERBY-7159: -- Assignee: Richard N. Hillegas > Make it possible to build and test Derby with Open JDK 22 > - > > Key: DERBY-7159 > URL: https://issues.apache.org/jira/browse/DERBY-7159 > Project: Derby > Issue Type: Task >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7158) ArrayIndexOutOfBoundsException when connecting to Embedded Derby
[
https://issues.apache.org/jira/browse/DERBY-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794837#comment-17794837
]
Richard N. Hillegas commented on DERBY-7158:
If you don't have a backup, then a last resort is the rawDBReader optional
tool. It is documented in the Derby Tools Guide. See
https://db.apache.org/derby/docs/10.17/tools/rtoolsoptdbreader.html The tool
attaches to the corrupt, unbootable database and lets you dump its tables into
a fresh, newly created empty database.
I don't see how adding memory would corrupt a Derby database.
Hope this helps,
-Rick
> ArrayIndexOutOfBoundsException when connecting to Embedded Derby
>
>
> Key: DERBY-7158
> URL: https://issues.apache.org/jira/browse/DERBY-7158
> Project: Derby
> Issue Type: Bug
>Affects Versions: 10.14.2.0
>Reporter: Yuliana Ganchevska
>Priority: Major
>
> Hello,
> our project is using Embedded Derby 10.14.2 with Java 11. A client recently
> complained they can't connect to the DB and it seems the DB is corrupted. At
> the time the issue happened they said the only change they made was to
> increase the memory. When the application is trying to connect to the DB, it
> throws the following exception:
> {code:java}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: Index -1 out of bounds
> for length 28
> at org.apache.derby.impl.store.raw.data.BasePage.getHeaderAtSlot(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.data.BasePage.setDeleteStatus(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at
> org.apache.derby.impl.store.raw.data.CachedPage.setDeleteStatus(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at
> org.apache.derby.impl.store.raw.data.StoredPage.setDeleteStatus(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.data.InsertOperation.undoMe(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.data.LogicalUndoOperation.doMe(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.log.FileLogger.logAndUndo(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.xact.Xact.logAndUndo(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.log.FileLogger.undo(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.xact.Xact.abort(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at
> org.apache.derby.impl.store.raw.xact.XactFactory.rollbackAllTransactions(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.log.LogToFile.recover(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.FileMonitor.startModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at
> org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.access.RAMAccessManager$5.run(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
> at
> org.apache.derby.impl.store.access.RAMAccessManager.bootServiceModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.services.monitor.FileMonitor.startModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at
> org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.db.BasicDatabase$5.run(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
> at org.apache.derby.impl.db.BasicDatabase.bootServiceModule(Unknown
> Source) ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)
> ~[derby-10.14.2.jar:?]
> at
[jira] [Commented] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationSchemeImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17786963#comment-17786963 ] Richard N. Hillegas commented on DERBY-7147: Attaching LDAPauthenticationVulnerability.pdf, the original description of the vulnerability. > LDAP injection vulnerability in LDAPAuthenticationSchemeImpl > > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0 > > Attachments: LDAPauthenticationVulnerability.pdf, > derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationSchemeImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7147: --- Attachment: LDAPauthenticationVulnerability.pdf > LDAP injection vulnerability in LDAPAuthenticationSchemeImpl > > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0 > > Attachments: LDAPauthenticationVulnerability.pdf, > derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationSchemeImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7147: --- Summary: LDAP injection vulnerability in LDAPAuthenticationSchemeImpl (was: LDAP injection vulnerability in LDAPAuthenticationImpl) > LDAP injection vulnerability in LDAPAuthenticationSchemeImpl > > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.1.0 > > Attachments: derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17786048#comment-17786048
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-16-aa-updateSTATUS.diff. This patch adds 10.17.1.0 to the
"Official Releases" section of the STATUS file.
Touches the following file:
{noformat}
M STATUS
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff,
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff,
> derby-7157-06-aa-newDataDictionaryVersion.diff,
> derby-7157-07-aa-recordBranchesOnWebsite.diff,
> derby-7157-08-aa-updateAntVersion.diff,
> derby-7157-09-aa-goofProofBranchName.diff,
> derby-7157-10-aa-deprecatedJavaPlatforms.diff,
> derby-7157-11-aa-addReleaseToWebsite.diff,
> derby-7157-12-aa-adjustMavenWarPom.diff, derby-7157-13-aa-updateDOAP.diff,
> derby-7157-14-aa-add10.17.1.0toArrayOfUpgradeStartingPoints.diff,
> derby-7157-15-aa-updateNewsSection.diff, derby-7157-16-aa-updateSTATUS.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-16-aa-updateSTATUS.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff, > derby-7157-09-aa-goofProofBranchName.diff, > derby-7157-10-aa-deprecatedJavaPlatforms.diff, > derby-7157-11-aa-addReleaseToWebsite.diff, > derby-7157-12-aa-adjustMavenWarPom.diff, derby-7157-13-aa-updateDOAP.diff, > derby-7157-14-aa-add10.17.1.0toArrayOfUpgradeStartingPoints.diff, > derby-7157-15-aa-updateNewsSection.diff, derby-7157-16-aa-updateSTATUS.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17786047#comment-17786047 ] Richard N. Hillegas commented on DERBY-7157: Attaching derby-7157-15-aa-updateNewsSection.diff. This patch adds the 10.17.1.0 announcement to the News section on the landing page of the Derby website. > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff, > derby-7157-09-aa-goofProofBranchName.diff, > derby-7157-10-aa-deprecatedJavaPlatforms.diff, > derby-7157-11-aa-addReleaseToWebsite.diff, > derby-7157-12-aa-adjustMavenWarPom.diff, derby-7157-13-aa-updateDOAP.diff, > derby-7157-14-aa-add10.17.1.0toArrayOfUpgradeStartingPoints.diff, > derby-7157-15-aa-updateNewsSection.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-15-aa-updateNewsSection.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff, > derby-7157-09-aa-goofProofBranchName.diff, > derby-7157-10-aa-deprecatedJavaPlatforms.diff, > derby-7157-11-aa-addReleaseToWebsite.diff, > derby-7157-12-aa-adjustMavenWarPom.diff, derby-7157-13-aa-updateDOAP.diff, > derby-7157-14-aa-add10.17.1.0toArrayOfUpgradeStartingPoints.diff, > derby-7157-15-aa-updateNewsSection.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-14-aa-add10.17.1.0toArrayOfUpgradeStartingPoints.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff, > derby-7157-09-aa-goofProofBranchName.diff, > derby-7157-10-aa-deprecatedJavaPlatforms.diff, > derby-7157-11-aa-addReleaseToWebsite.diff, > derby-7157-12-aa-adjustMavenWarPom.diff, derby-7157-13-aa-updateDOAP.diff, > derby-7157-14-aa-add10.17.1.0toArrayOfUpgradeStartingPoints.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785063#comment-17785063
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-14-aa-add10.17.1.0toArrayOfUpgradeStartingPoints.diff.
This patch adds 10.17.1.0 to the list of starting points for upgrade
trajectories.
Touches the following file:
{noformat}
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/upgradeTests/OldVersions.java
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff,
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff,
> derby-7157-06-aa-newDataDictionaryVersion.diff,
> derby-7157-07-aa-recordBranchesOnWebsite.diff,
> derby-7157-08-aa-updateAntVersion.diff,
> derby-7157-09-aa-goofProofBranchName.diff,
> derby-7157-10-aa-deprecatedJavaPlatforms.diff,
> derby-7157-11-aa-addReleaseToWebsite.diff,
> derby-7157-12-aa-adjustMavenWarPom.diff, derby-7157-13-aa-updateDOAP.diff,
> derby-7157-14-aa-add10.17.1.0toArrayOfUpgradeStartingPoints.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785041#comment-17785041
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-13-aa-updateDOAP.diff. This patch records the 10.17.1.0
release in the Derby DOAP descriptor.
Touches the following file:
{noformat}
M doap_Derby.rdf
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff,
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff,
> derby-7157-06-aa-newDataDictionaryVersion.diff,
> derby-7157-07-aa-recordBranchesOnWebsite.diff,
> derby-7157-08-aa-updateAntVersion.diff,
> derby-7157-09-aa-goofProofBranchName.diff,
> derby-7157-10-aa-deprecatedJavaPlatforms.diff,
> derby-7157-11-aa-addReleaseToWebsite.diff,
> derby-7157-12-aa-adjustMavenWarPom.diff, derby-7157-13-aa-updateDOAP.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-13-aa-updateDOAP.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff, > derby-7157-09-aa-goofProofBranchName.diff, > derby-7157-10-aa-deprecatedJavaPlatforms.diff, > derby-7157-11-aa-addReleaseToWebsite.diff, > derby-7157-12-aa-adjustMavenWarPom.diff, derby-7157-13-aa-updateDOAP.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784636#comment-17784636
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-12-aa-adjustMavenWarPom.diff. This patch adjusts the maven
war pom so that the maven publication step will work.
My first attempt to follow the instructions in maven2/README.txt failed on a
version mismatch related to maven2/war/pom.xml. So I upgraded to the latest
maven version (3.9.5) and I changed the war pom to reference the latest version
of the war plugin (3.3.1). Then publication failed, complaining that maven
couldn't find a war.xml file. I hacked around this by adding the following
stanza to the war plugin descriptor:
false
and I removed the following stanza, the hack needed to address a related
problem when publishing 10.16.1.1:
${basedir}/../../tools/j2ee/derby/WEB-INF/web.xml
Touches the following file:
{noformat}
M maven2/war/pom.xml
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff,
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff,
> derby-7157-06-aa-newDataDictionaryVersion.diff,
> derby-7157-07-aa-recordBranchesOnWebsite.diff,
> derby-7157-08-aa-updateAntVersion.diff,
> derby-7157-09-aa-goofProofBranchName.diff,
> derby-7157-10-aa-deprecatedJavaPlatforms.diff,
> derby-7157-11-aa-addReleaseToWebsite.diff,
> derby-7157-12-aa-adjustMavenWarPom.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-12-aa-adjustMavenWarPom.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff, > derby-7157-09-aa-goofProofBranchName.diff, > derby-7157-10-aa-deprecatedJavaPlatforms.diff, > derby-7157-11-aa-addReleaseToWebsite.diff, > derby-7157-12-aa-adjustMavenWarPom.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784585#comment-17784585
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-11-aa-addReleaseToWebsite.diff. This patch adds the
10.17.1.0 download page to the website. The top level download page has been
adjusted to indicate why certain releases are bound to certain Java versions.
Touches the following files:
{noformat}
X build/site
M src/documentation/conf/cli.xconf
M src/documentation/content/xdocs/derby_downloads.xml
M src/documentation/content/xdocs/manuals/index.xml
M src/documentation/content/xdocs/papers/DerbyTut/install_software.xml
M src/documentation/content/xdocs/quick_start.xml
D src/documentation/content/xdocs/releases/release-10_15_2_0.cgi
M src/documentation/content/xdocs/releases/release-10_15_2_0.html
A src/documentation/content/xdocs/releases/release-10_17_1_0.cgi
A src/documentation/content/xdocs/releases/release-10_17_1_0.html
M src/documentation/skinconf.xml
Performing status on external item at 'build/site':
M build/site/DerbyBugGuidelines.html
M build/site/blogs/index.html
M build/site/derby_charter.html
M build/site/derby_comm.html
M build/site/derby_downloads.html
M build/site/derby_mail.html
M build/site/derby_proposal.html
M build/site/derby_tests.html
M build/site/dev/derby_source.html
M build/site/faq.html
M build/site/index.html
M build/site/integrate/DerbyTomcat5512JPetStor.html
M build/site/integrate/JPOX_Derby.html
M build/site/integrate/JPetStoreGeronimo.html
M build/site/integrate/JPetStoreWebSphere.html
M build/site/integrate/SQuirreL_Derby.html
M build/site/integrate/db_ddlutils.html
M build/site/integrate/db_torque.html
M build/site/integrate/derby_plugin_info.html
M build/site/integrate/index.html
M build/site/license.html
M build/site/linkmap.html
M build/site/logo.html
M build/site/manuals/dita.html
M build/site/manuals/docscheck.html
M build/site/manuals/docsfaq.html
M build/site/manuals/guidelines.html
M build/site/manuals/index.html
M build/site/manuals/messages.html
M build/site/papers/ApacheCon.html
M build/site/papers/DerbyClientSpec.html
M build/site/papers/DerbyTut/embedded_intro.html
M build/site/papers/DerbyTut/ij_intro.html
M build/site/papers/DerbyTut/index.html
M build/site/papers/DerbyTut/install_software.html
M build/site/papers/DerbyTut/ns_intro.html
M build/site/papers/Intersect-design.html
M build/site/papers/JDBCImplementation.html
M build/site/papers/MiscPresentations.html
M build/site/papers/btree_package.html
M build/site/papers/derby_arch.html
M build/site/papers/derby_htw.html
M build/site/papers/derby_web.html
M build/site/papers/fortune_tut.html
M build/site/papers/index.html
M build/site/papers/logformats.html
M build/site/papers/optimizer.html
M build/site/papers/pageformats.html
M build/site/papers/recovery.html
M build/site/papers/versionupgrade.html
M build/site/quick_start.html
M build/site/releases/release-10.0.2.1.html
M build/site/releases/release-10.1.1.0.html
M build/site/releases/release-10.1.2.1.html
M build/site/releases/release-10.1.3.1.html
M build/site/releases/release-10.10.1.1.html
M build/site/releases/release-10.10.2.0.html
M build/site/releases/release-10.11.1.1.html
M build/site/releases/release-10.12.1.1.html
M build/site/releases/release-10.13.1.1.html
M build/site/releases/release-10.15.1.3.html
M build/site/releases/release-10.2.1.6.html
M build/site/releases/release-10.2.2.0.html
M build/site/releases/release-10.3.3.0.html
M build/site/releases/release-10.4.1.3.html
M build/site/releases/release-10.4.2.0.html
M build/site/releases/release-10.5.1.1.html
M build/site/releases/release-10.5.3.0.html
M build/site/releases/release-10.6.1.0.html
M build/site/releases/release-10.6.2.1.html
M build/site/releases/release-10.7.1.1.html
M build/site/releases/release-10.8.1.2.html
M build/site/releases/release-10.8.2.2.html
M build/site/releases/release-10.8.3.0.html
M build/site/releases/release-10.9.1.0.html
M build/site/releases/release-10_14_2_0.html
D build/site/releases/release-10_15_2_0.cgi
M build/site/releases/release-10_15_2_0.html
A build/site/releases/release-10_17_1_0.cgi
A build/site/releases/release-10_17_1_0.html
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL:
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-11-aa-addReleaseToWebsite.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff, > derby-7157-09-aa-goofProofBranchName.diff, > derby-7157-10-aa-deprecatedJavaPlatforms.diff, > derby-7157-11-aa-addReleaseToWebsite.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781913#comment-17781913
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-10-aa-deprecatedJavaPlatforms.diff. This patch adds a
sentence to the release notes, stating that 10.17.1.0 does NOT support Java
releases prior to Java SE 21--as Knut suggested.
Touches the following files:
{noformat}
M RELEASE-NOTES.html
M releaseSummary.xml
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff,
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff,
> derby-7157-06-aa-newDataDictionaryVersion.diff,
> derby-7157-07-aa-recordBranchesOnWebsite.diff,
> derby-7157-08-aa-updateAntVersion.diff,
> derby-7157-09-aa-goofProofBranchName.diff,
> derby-7157-10-aa-deprecatedJavaPlatforms.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-10-aa-deprecatedJavaPlatforms.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff, > derby-7157-09-aa-goofProofBranchName.diff, > derby-7157-10-aa-deprecatedJavaPlatforms.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780033#comment-17780033 ] Richard N. Hillegas commented on DERBY-7157: Responding to Knut and Bryan's comments about the confusing state of what Java versions 10.17.1.0 supports: The Overview section of the release notes does state that 10.17.1.0 runs on Java SE 21 and higher. For future release notes, to reduce confusion, should we explicitly state what Java versions the release won't run on? How can we make this clearer? Responding to Knut's comment about deprecating support for JDK 17 and earlier: Support was deprecated because the Open JDK has deprecated support for the SecurityManager in such a way that we had to change our instructions for how to boot Derby. We thought that continuing to support a deprecated feature was going to cause us trouble going forward and would make our user documentation confusing. Responding to Bryan's comments about the download page: As far as I know, there is no upper bound yet on the Java platforms which any of our releases support. Caveat: however, in order to run an old Derby version on a modern platform, you may have to change your boot command. We don't document what you need to do. Instead, if you want to use the SecurityManager, you have to boot Derby according to the documentation, trip over a fatal error from the JVM, google up that error message, and adjust your boot command accordingly. At some point, the Open JDK will actually rip out the SecurityManager. That change may impose an upper bound on the Java platforms supported by old Derby versions--I don't know, I think it depends on how the Open JDK handles the code removal. I like Bryan's suggestion about adding some verbiage concerning Modules and the deprecated SecurityManager. This would help users understand why we introduced lower bounds on platform support. > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff, > derby-7157-09-aa-goofProofBranchName.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780009#comment-17780009
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-09-aa-goofProofBranchName.diff. This patch changes the
ReleaseNoteGenerator program so that extracts the branch name from the
user-supplied release ID rather than from subversion-controlled information.
Touches the following files:
{noformat}
M java/build/org/apache/derbyBuild/GeneratorBase.java
M java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java
Changes to the release note generator.
M RELEASE-NOTES.html
Regenerated release notes for 10.17.1.0.
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff,
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff,
> derby-7157-06-aa-newDataDictionaryVersion.diff,
> derby-7157-07-aa-recordBranchesOnWebsite.diff,
> derby-7157-08-aa-updateAntVersion.diff,
> derby-7157-09-aa-goofProofBranchName.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-09-aa-goofProofBranchName.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff, > derby-7157-09-aa-goofProofBranchName.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779975#comment-17779975 ] Richard N. Hillegas commented on DERBY-7157: Thanks for reading the release notes carefully, Knut. The branch name mistake happened because: 1) I built the release notes on trunk rather than the 10.17 branch. 2) There is a weakness in the ReleaseNoteGenerator program. It gets the branch name from the source code tree. I think it would be better if the program extracted the branch name from the user-supplied release ID. I will correct that weakness and regenerate the release notes. Then, at least, the branch name will be correct in the 10.17 branch and the process will be more goof-proofed going forward. > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778462#comment-17778462
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-08-aa-updateAntVersion.diff. This patch updates the Ant
version to 1.10.14 in the 10.17.1 release notes and in the instructions for
building Derby.
Touches the following files:
{noformat}
M BUILDING.html
M RELEASE-NOTES.html
M releaseSummary.xml
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff,
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff,
> derby-7157-06-aa-newDataDictionaryVersion.diff,
> derby-7157-07-aa-recordBranchesOnWebsite.diff,
> derby-7157-08-aa-updateAntVersion.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-08-aa-updateAntVersion.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff, > derby-7157-08-aa-updateAntVersion.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778459#comment-17778459
]
Richard N. Hillegas commented on DERBY-7157:
My first attempt to build a 10.17.1 release candidate failed because my version
of Ant failed on executions of the task. These died with the following
stack trace:
{noformat}
[java] java.lang.UnsupportedOperationException: The Security Manager is
deprecated and will be removed in a future release
[java] at
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:194)
[java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:861)
[java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:231)
[java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:135)
[java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:108)
[java] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
[java] at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
[java] at java.base/java.lang.reflect.Method.invoke(Method.java:580)
[java] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
[java] at org.apache.tools.ant.Task.perform(Task.java:350)
[java] at org.apache.tools.ant.Target.execute(Target.java:449)
[java] at org.apache.tools.ant.Target.performTasks(Target.java:470)
[java] at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1391)
[java] at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
[java] at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[java] at
org.apache.tools.ant.Project.executeTargets(Project.java:1254)
[java] at org.apache.tools.ant.Main.runBuild(Main.java:830)
[java] at org.apache.tools.ant.Main.startAnt(Main.java:223)
[java] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
[java] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
[java] Caused by: java.lang.UnsupportedOperationException: The Security
Manager is deprecated and will be removed in a future release
[java] at
java.base/java.lang.System.setSecurityManager(System.java:429)
[java] at
org.apache.tools.ant.types.Permissions.setSecurityManager(Permissions.java:103)
[java] at
org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:216)
[java] at
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:155)
[java] ... 19 more
{noformat}
This is clearly more fallout from OpenJDK's deprecation of the SecurityManager.
The task succeeds after upgrading to the latest version of Ant (1.10.14).
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff,
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff,
> derby-7157-06-aa-newDataDictionaryVersion.diff,
> derby-7157-07-aa-recordBranchesOnWebsite.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778458#comment-17778458 ] Richard N. Hillegas commented on DERBY-7157: Thanks for finding that, Bryan. Nope, the step is there at the end of the description of how to create a new branch (https://cwiki.apache.org/confluence/display/DERBY/CreatingDerbyBranch) which, in turn, is pointed to by the description of Release Prep steps (https://cwiki.apache.org/confluence/display/DERBY/ReleasePrep). I just skipped over that step while creating the branches and forgot to go back to finish the step. I have added 10.16 and 10.17 to the source page. > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-07-aa-recordBranchesOnWebsite.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff, > derby-7157-07-aa-recordBranchesOnWebsite.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17778456#comment-17778456
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-07-aa-recordBranchesOnWebsite.diff. This patch adds the
10.16 and 10.17 branches to the list of branches on the website.
Touches the following files:
{noformat}
X build/site
M src/documentation/content/xdocs/dev/derby_source.xml
Performing status on external item at 'build/site':
M build/site/dev/derby_source.html
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff,
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff,
> derby-7157-06-aa-newDataDictionaryVersion.diff,
> derby-7157-07-aa-recordBranchesOnWebsite.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-06-aa-newDataDictionaryVersion.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff, > derby-7157-06-aa-newDataDictionaryVersion.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776910#comment-17776910
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-06-aa-newDataDictionaryVersion.diff. This patch adds a new
10.18 DataDictionary version on the trunk. Tests passed cleanly with the
classpath. I didn't bother running the modulepath tests.
Touches the following files:
{noformat}
M
java/org.apache.derby.engine/org/apache/derby/iapi/sql/dictionary/DataDictionary.java
M
java/org.apache.derby.engine/org/apache/derby/impl/sql/catalog/DD_Version.java
M
java/org.apache.derby.engine/org/apache/derby/impl/sql/catalog/DataDictionaryImpl.java
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff,
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff,
> derby-7157-06-aa-newDataDictionaryVersion.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff, > derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776858#comment-17776858
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff. This patch bumps the
trunk release version to 10.18.0.0.
Touches the following file:
{noformat}
M tools/ant/properties/release.properties
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff,
> derby-7157-05-aa-bumpReleaseNumberOnTrunk.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776845#comment-17776845
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-04-aa-updateReleaseProperties.diff. Just to be safe,
update the copyright year in release.properties.
Touches the following file:
{noformat}
M tools/ant/properties/release.properties
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff,
> derby-7157-04-aa-updateReleaseProperties.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-04-aa-updateReleaseProperties.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff, > derby-7157-04-aa-updateReleaseProperties.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776788#comment-17776788
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-03-aa-updateDocConstants.diff. This patch updates the
copyright year constant and the minimum jdk constant used to build the docs.
Touches the following file:
{noformat}
M docs.properties
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff,
> derby-7157-03-aa-updateDocConstants.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-03-aa-updateDocConstants.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff, > derby-7157-03-aa-updateDocConstants.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-02-aa-initialSTATUSupdate.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff, > derby-7157-02-aa-initialSTATUSupdate.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776768#comment-17776768
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-02-aa-initialSTATUSupdate.diff. This patch updates the
STATUS file to record the dates of release milestones for the previous
(10.16.1.1) release.
Touches the following file:
{noformat}
M STATUS
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff,
> derby-7157-02-aa-initialSTATUSupdate.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DERBY-7157) Tasks for releasing Derby 10.17.1
[
https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773826#comment-17773826
]
Richard N. Hillegas commented on DERBY-7157:
Attaching derby-7157-01-aa-draftReleaseNotes.diff. This patch is the first
draft of the release notes.
Touches the following files:
{noformat}
M RELEASE-NOTES.html
M releaseSummary.xml
{noformat}
> Tasks for releasing Derby 10.17.1
> -
>
> Key: DERBY-7157
> URL: https://issues.apache.org/jira/browse/DERBY-7157
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: derby-7157-01-aa-draftReleaseNotes.diff
>
>
> Placeholder for activity related to producing a 10.17.1 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7157) Tasks for releasing Derby 10.17.1
[ https://issues.apache.org/jira/browse/DERBY-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7157: --- Attachment: derby-7157-01-aa-draftReleaseNotes.diff > Tasks for releasing Derby 10.17.1 > - > > Key: DERBY-7157 > URL: https://issues.apache.org/jira/browse/DERBY-7157 > Project: Derby > Issue Type: Task > Components: Build tools >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7157-01-aa-draftReleaseNotes.diff > > > Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DERBY-7157) Tasks for releasing Derby 10.17.1
Richard N. Hillegas created DERBY-7157: -- Summary: Tasks for releasing Derby 10.17.1 Key: DERBY-7157 URL: https://issues.apache.org/jira/browse/DERBY-7157 Project: Derby Issue Type: Task Components: Build tools Reporter: Richard N. Hillegas Assignee: Richard N. Hillegas Placeholder for activity related to producing a 10.17.1 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7147: --- Attachment: releaseNote.html > LDAP injection vulnerability in LDAPAuthenticationImpl > -- > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.0.0 > > Attachments: derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7147: --- Attachment: (was: releaseNote-1.html) > LDAP injection vulnerability in LDAPAuthenticationImpl > -- > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.0.0 > > Attachments: derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7147: --- Attachment: (was: releaseNote.html) > LDAP injection vulnerability in LDAPAuthenticationImpl > -- > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.0.0 > > Attachments: derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7147: --- Attachment: releaseNote-1.html > LDAP injection vulnerability in LDAPAuthenticationImpl > -- > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.0.0 > > Attachments: derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7147) LDAP injection vulnerability in LDAPAuthenticationImpl
[ https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17758153#comment-17758153 ] Richard N. Hillegas commented on DERBY-7147: This issue has been assigned CVE-2022-46337. The reporter, Qing Xu, has asked that credit for discovering this exploit should be given to 4ra1n and Y4tacker. > LDAP injection vulnerability in LDAPAuthenticationImpl > -- > > Key: DERBY-7147 > URL: https://issues.apache.org/jira/browse/DERBY-7147 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.16.1.1 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.14.3, 10.15.2.1, 10.16.1.2, 10.17.0.0 > > Attachments: derby-7147-01-aa-reformatForReadability.diff, > derby-7147-02-aa-escapeLDAPsearchFilter.diff, > derby-7147-02-ab-escapeLDAPsearchFilter.diff, > derby-7147-03-aa-updateLDAPinstructions.diff, > derby-7147-03-aa-updateLDAPinstructions.tar, > derby-7147-03-ab-updateLDAPinstructions.diff, > derby-7147-03-ab-updateLDAPinstructions.tar, > derby-7147-04-aa-pointLDAPTestAtInstructions.diff, releaseNote.html > > > An LDAP injection vulnerability has been identified in > LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been > provided, but there is a possibility that an intruder could bypass > authentication checks in Derby-powered applications which rely on external > LDAP servers. > For more information on LDAP injection, see > https://www.synopsys.com/glossary/what-is-ldap-injection.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7155) Make it possible to build and test Derby with Open JDK 21
[ https://issues.apache.org/jira/browse/DERBY-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17758146#comment-17758146 ] Richard N. Hillegas commented on DERBY-7155: Derby built cleanly (including javadoc) with Open JDK build 21+35-2513. Full regression tests ran cleanly with both the classpath and the modulepath. > Make it possible to build and test Derby with Open JDK 21 > - > > Key: DERBY-7155 > URL: https://issues.apache.org/jira/browse/DERBY-7155 > Project: Derby > Issue Type: Task >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: derby-7155-01-aa-addJDK21vmWrapper.diff > > > An early access release of Open JDK 21 is now available. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DERBY-7156) ERROR XSDAO: Internal error: Page attempted latched twice when executing parallel accesses to the same binary column
[
https://issues.apache.org/jira/browse/DERBY-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757619#comment-17757619
]
Richard N. Hillegas commented on DERBY-7156:
The comments in BasePage.setExclusive() suggest that the latching
implementation could be made more robust at the cost of more object creation on
the inner loop. This is tricky code outside my area of expertise.
> ERROR XSDAO: Internal error: Page attempted latched twice when executing
> parallel accesses to the same binary column
>
>
> Key: DERBY-7156
> URL: https://issues.apache.org/jira/browse/DERBY-7156
> Project: Derby
> Issue Type: Bug
> Components: Store
>Affects Versions: 10.15.1.3, 10.15.2.0, 10.16.1.1
> Environment: OS name: Windows 10
> OS architecture: amd64
> OS version: 10.0
> Java Version:17.0.7
> Java Vendor: Eclipse Adoptium
>Reporter: Sergio Cruz
>Priority: Major
> Attachments: TestTx.java, derby.log, sysinfo.txt
>
>
> {{When executing parallel _SELECT_ statements accessing to a table with a
> binary column, sometimes an error indicating that a page was attempted
> latched twice is received while reading the value of the binary column.}}
>
> {{This error _ERROR XSDAO: Internal error: page Page(334,Container(0, 1456))
> attempted latched twice_ is received when connection is inside a
> transaction.}}
> {{In case the connection is not in a transaction, the error is different:
> _ERROR 40XD0: Container has been closed_}}
>
> I attach a Java class for reproducing the issue. It has the following lines
> for testing both versions of the error
> {code:java}
> //conn.setAutoCommit(true); //ERROR 40XD0: Container has been closed.
> conn.setAutoCommit(false); //ERROR XSDAO: Internal error: page
> Page(334,Container(0, 1392)) attempted latched twice. {code}
> This is an example of the received error.
>
> {noformat}
> Exception in thread "pool-1-thread-1" java.lang.RuntimeException:
> java.io.IOException: ERROR XSDAO: Internal error: page Page(334,Container(0,
> 1456)) attempted latched twice.
> at org.scruz.derby.TestTx$Access.run(TestTx.java:60)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.io.IOException: ERROR XSDAO: Internal error: page
> Page(334,Container(0, 1456)) attempted latched twice.
> at
> org.apache.derby.impl.store.raw.data.OverflowInputStream.fillByteHolder(OverflowInputStream.java:168)
> at
> org.apache.derby.impl.store.raw.data.BufferedByteHolderInputStream.read(BufferedByteHolderInputStream.java:37)
> at java.base/java.io.FilterInputStream.read(FilterInputStream.java:82)
> at java.base/java.io.FilterInputStream.read(FilterInputStream.java:82)
> at java.base/java.io.FilterInputStream.read(FilterInputStream.java:82)
> at
> org.apache.derby.iapi.services.io.CloseFilterInputStream.read(CloseFilterInputStream.java:60)
> at org.scruz.derby.TestTx$Access.run(TestTx.java:55)
> ... 3 more
> Caused by: ERROR XSDAO: Internal error: page Page(334,Container(0, 1456))
> attempted latched twice.
> at
> org.apache.derby.shared.common.error.StandardException.newException(StandardException.java:300)
> at
> org.apache.derby.shared.common.error.StandardException.newException(StandardException.java:295)
> at
> org.apache.derby.impl.store.raw.data.BasePage.setExclusive(BasePage.java:1710)
> at
> org.apache.derby.impl.store.raw.data.BaseContainer.latchPage(BaseContainer.java:527)
> at
> org.apache.derby.impl.store.raw.data.FileContainer.latchPage(FileContainer.java:3532)
> at
> org.apache.derby.impl.store.raw.data.FileContainer.getUserPage(FileContainer.java:2551)
> at
> org.apache.derby.impl.store.raw.data.FileContainer.getPage(FileContainer.java:2593)
> at
> org.apache.derby.impl.store.raw.data.BaseContainerHandle.getPage(BaseContainerHandle.java:319)
> at
> org.apache.derby.impl.store.raw.data.OverflowInputStream.fillByteHolder(OverflowInputStream.java:151)
> ... 9 more{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DERBY-7156) ERROR XSDAO: Internal error: Page attempted latched twice when executing parallel accesses to the same binary column
[
https://issues.apache.org/jira/browse/DERBY-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard N. Hillegas updated DERBY-7156:
---
Bug behavior facts: Crash,Seen in production (was: Seen in production)
> ERROR XSDAO: Internal error: Page attempted latched twice when executing
> parallel accesses to the same binary column
>
>
> Key: DERBY-7156
> URL: https://issues.apache.org/jira/browse/DERBY-7156
> Project: Derby
> Issue Type: Bug
> Components: Store
>Affects Versions: 10.15.1.3, 10.15.2.0, 10.16.1.1
> Environment: OS name: Windows 10
> OS architecture: amd64
> OS version: 10.0
> Java Version:17.0.7
> Java Vendor: Eclipse Adoptium
>Reporter: Sergio Cruz
>Priority: Major
> Attachments: TestTx.java, derby.log, sysinfo.txt
>
>
> {{When executing parallel _SELECT_ statements accessing to a table with a
> binary column, sometimes an error indicating that a page was attempted
> latched twice is received while reading the value of the binary column.}}
>
> {{This error _ERROR XSDAO: Internal error: page Page(334,Container(0, 1456))
> attempted latched twice_ is received when connection is inside a
> transaction.}}
> {{In case the connection is not in a transaction, the error is different:
> _ERROR 40XD0: Container has been closed_}}
>
> I attach a Java class for reproducing the issue. It has the following lines
> for testing both versions of the error
> {code:java}
> //conn.setAutoCommit(true); //ERROR 40XD0: Container has been closed.
> conn.setAutoCommit(false); //ERROR XSDAO: Internal error: page
> Page(334,Container(0, 1392)) attempted latched twice. {code}
> This is an example of the received error.
>
> {noformat}
> Exception in thread "pool-1-thread-1" java.lang.RuntimeException:
> java.io.IOException: ERROR XSDAO: Internal error: page Page(334,Container(0,
> 1456)) attempted latched twice.
> at org.scruz.derby.TestTx$Access.run(TestTx.java:60)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.io.IOException: ERROR XSDAO: Internal error: page
> Page(334,Container(0, 1456)) attempted latched twice.
> at
> org.apache.derby.impl.store.raw.data.OverflowInputStream.fillByteHolder(OverflowInputStream.java:168)
> at
> org.apache.derby.impl.store.raw.data.BufferedByteHolderInputStream.read(BufferedByteHolderInputStream.java:37)
> at java.base/java.io.FilterInputStream.read(FilterInputStream.java:82)
> at java.base/java.io.FilterInputStream.read(FilterInputStream.java:82)
> at java.base/java.io.FilterInputStream.read(FilterInputStream.java:82)
> at
> org.apache.derby.iapi.services.io.CloseFilterInputStream.read(CloseFilterInputStream.java:60)
> at org.scruz.derby.TestTx$Access.run(TestTx.java:55)
> ... 3 more
> Caused by: ERROR XSDAO: Internal error: page Page(334,Container(0, 1456))
> attempted latched twice.
> at
> org.apache.derby.shared.common.error.StandardException.newException(StandardException.java:300)
> at
> org.apache.derby.shared.common.error.StandardException.newException(StandardException.java:295)
> at
> org.apache.derby.impl.store.raw.data.BasePage.setExclusive(BasePage.java:1710)
> at
> org.apache.derby.impl.store.raw.data.BaseContainer.latchPage(BaseContainer.java:527)
> at
> org.apache.derby.impl.store.raw.data.FileContainer.latchPage(FileContainer.java:3532)
> at
> org.apache.derby.impl.store.raw.data.FileContainer.getUserPage(FileContainer.java:2551)
> at
> org.apache.derby.impl.store.raw.data.FileContainer.getPage(FileContainer.java:2593)
> at
> org.apache.derby.impl.store.raw.data.BaseContainerHandle.getPage(BaseContainerHandle.java:319)
> at
> org.apache.derby.impl.store.raw.data.OverflowInputStream.fillByteHolder(OverflowInputStream.java:151)
> ... 9 more{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DERBY-7156) ERROR XSDAO: Internal error: Page attempted latched twice when executing parallel accesses to the same binary column
[
https://issues.apache.org/jira/browse/DERBY-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757045#comment-17757045
]
Richard N. Hillegas commented on DERBY-7156:
Thanks for the repro. I have verified the XSDAO error.
> ERROR XSDAO: Internal error: Page attempted latched twice when executing
> parallel accesses to the same binary column
>
>
> Key: DERBY-7156
> URL: https://issues.apache.org/jira/browse/DERBY-7156
> Project: Derby
> Issue Type: Bug
> Components: Store
>Affects Versions: 10.15.1.3, 10.15.2.0, 10.16.1.1
> Environment: OS name: Windows 10
> OS architecture: amd64
> OS version: 10.0
> Java Version:17.0.7
> Java Vendor: Eclipse Adoptium
>Reporter: Sergio Cruz
>Priority: Major
> Attachments: TestTx.java, derby.log, sysinfo.txt
>
>
> {{When executing parallel _SELECT_ statements accessing to a table with a
> binary column, sometimes an error indicating that a page was attempted
> latched twice is received while reading the value of the binary column.}}
>
> {{This error _ERROR XSDAO: Internal error: page Page(334,Container(0, 1456))
> attempted latched twice_ is received when connection is inside a
> transaction.}}
> {{In case the connection is not in a transaction, the error is different:
> _ERROR 40XD0: Container has been closed_}}
>
> I attach a Java class for reproducing the issue. It has the following lines
> for testing both versions of the error
> {code:java}
> //conn.setAutoCommit(true); //ERROR 40XD0: Container has been closed.
> conn.setAutoCommit(false); //ERROR XSDAO: Internal error: page
> Page(334,Container(0, 1392)) attempted latched twice. {code}
> This is an example of the received error.
>
> {noformat}
> Exception in thread "pool-1-thread-1" java.lang.RuntimeException:
> java.io.IOException: ERROR XSDAO: Internal error: page Page(334,Container(0,
> 1456)) attempted latched twice.
> at org.scruz.derby.TestTx$Access.run(TestTx.java:60)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.io.IOException: ERROR XSDAO: Internal error: page
> Page(334,Container(0, 1456)) attempted latched twice.
> at
> org.apache.derby.impl.store.raw.data.OverflowInputStream.fillByteHolder(OverflowInputStream.java:168)
> at
> org.apache.derby.impl.store.raw.data.BufferedByteHolderInputStream.read(BufferedByteHolderInputStream.java:37)
> at java.base/java.io.FilterInputStream.read(FilterInputStream.java:82)
> at java.base/java.io.FilterInputStream.read(FilterInputStream.java:82)
> at java.base/java.io.FilterInputStream.read(FilterInputStream.java:82)
> at
> org.apache.derby.iapi.services.io.CloseFilterInputStream.read(CloseFilterInputStream.java:60)
> at org.scruz.derby.TestTx$Access.run(TestTx.java:55)
> ... 3 more
> Caused by: ERROR XSDAO: Internal error: page Page(334,Container(0, 1456))
> attempted latched twice.
> at
> org.apache.derby.shared.common.error.StandardException.newException(StandardException.java:300)
> at
> org.apache.derby.shared.common.error.StandardException.newException(StandardException.java:295)
> at
> org.apache.derby.impl.store.raw.data.BasePage.setExclusive(BasePage.java:1710)
> at
> org.apache.derby.impl.store.raw.data.BaseContainer.latchPage(BaseContainer.java:527)
> at
> org.apache.derby.impl.store.raw.data.FileContainer.latchPage(FileContainer.java:3532)
> at
> org.apache.derby.impl.store.raw.data.FileContainer.getUserPage(FileContainer.java:2551)
> at
> org.apache.derby.impl.store.raw.data.FileContainer.getPage(FileContainer.java:2593)
> at
> org.apache.derby.impl.store.raw.data.BaseContainerHandle.getPage(BaseContainerHandle.java:319)
> at
> org.apache.derby.impl.store.raw.data.OverflowInputStream.fillByteHolder(OverflowInputStream.java:151)
> ... 9 more{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
