You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2010/03/29 22:26:27 UTC
[jira] Created: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
-----------------------------------------------------------------------------------------------
Key: DERBY-4602
URL: https://issues.apache.org/jira/browse/DERBY-4602
Project: Derby
Issue Type: Bug
Components: Test
Affects Versions: 10.6.0.0
Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
Reporter: Myrna van Lunteren
Attachments: j9errorsandfailures.txt
Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
I believe these were the effect of the following checkin for DERBY-4483:
r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
This is the top of the first error:
-------------------
1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
------------------
The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-4602:
--------------------------------------
Issue & fix info: [Release Note Needed]
I think we would need a release note if the 1a patch is committed to explain weme users what to do if they get a message saying algorithm not supported when they try to connect. (This may happen if they create a database on a more capable platform, enable authentication, and copy the database to a restricted platform.) I think the error message they'll see is pretty self-explanatory, but I still think a release note is in order, as users may wonder why this started happening now.
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Attachments: derby-4602-1a.diff, derby-4602-1a.stat, j9errorsandfailures.txt, ListAlgorithms.java
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-4602:
--------------------------------------
Component/s: Services
Bug behavior facts: [Regression Test Failure, Security] (was: [Regression Test Failure])
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Attachments: derby-4602-1a.diff, derby-4602-1a.stat, j9errorsandfailures.txt, ListAlgorithms.java
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851268#action_12851268 ]
Knut Anders Hatlen commented on DERBY-4602:
-------------------------------------------
The failure in testVariousBuiltinAlgorithm() is not so serious in itself, as it could just be disabled on JVMs that don't support SHA-256. However, SHA-256 was made the default algorithm in revision 927368, so with a more recent version of trunk, you'd probably see even more of these errors.
The phoneME tests have been running cleanly after the DERBY-4483 changes. http://dbtg.foundry.sun.com/derby/test/Daily/javaME/testing/Limited/
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Attachments: j9errorsandfailures.txt
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-4602.
-------------------------------------
All tests pass again with weme 6.2.
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Fix For: 10.6.0.0
>
> Attachments: derby-4602-1a.diff, derby-4602-1a.stat, derby-4602-1b.diff, j9errorsandfailures.txt, ListAlgorithms.java, releaseNote.html
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851470#action_12851470 ]
Myrna van Lunteren commented on DERBY-4602:
-------------------------------------------
The output with weme 6.2 is:
Digest algorithms:
MD5
SHA-1
Providers:
OTI
J9JCE
J9JSSE
And indeed, there's more errors since March 25 (revision 927661) we've now gotten up to 10 failures and 122 errors...(not all are because of missing SHA-256, some of those are due to a lock being held from some previous test, or similar trouble).
Perhaps it's possible to have some exception code to have SHA-1 be the default for weme...The weme jvm is recognizable by a number of properties starting with 'com.ibm.oti'... We already have one weme specific code snippet in BaseTestCase to find the executable name...
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Attachments: j9errorsandfailures.txt, ListAlgorithms.java
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-4602:
--------------------------------------
Attachment: j9errorsandfailures.txt
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Attachments: j9errorsandfailures.txt
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-4602:
--------------------------------------
Attachment: derby-4602-1b.diff
Attaching updated patch (1b) that does not fail on database creation if SHA-1 is not present.
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Attachments: derby-4602-1a.diff, derby-4602-1a.stat, derby-4602-1b.diff, j9errorsandfailures.txt, ListAlgorithms.java, releaseNote.html
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-4602:
--------------------------------------
Attachment: ListAlgorithms.java
If the problem is that SHA-256 is missing, we could always make SHA-1 the default algorithm (it must be supported on weme, since that's what the old authentication scheme used). But before we do that, it would be interesting to see which security providers are available on weme, and which message digest algorithms they support. Myrna, could you please attach the output produced by the attached java class on weme? Thanks.
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Attachments: j9errorsandfailures.txt, ListAlgorithms.java
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4602) 10 failures and 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-4602:
---------------------------------
Summary: 10 failures and 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483 (was: 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483)
> 10 failures and 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -------------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Fix For: 10.6.0.0
>
> Attachments: derby-4602-1a.diff, derby-4602-1a.stat, derby-4602-1b.diff, j9errorsandfailures.txt, ListAlgorithms.java, releaseNote.html
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-4602:
--------------------------------------
Attachment: derby-4602-1a.diff
derby-4602-1a.stat
Rick also suggested (in a comment on DERBY-4483) that we should keep SHA-256 as the default on platforms that support it and fall back to SHA-1 on those that don't, so I'm attaching a patch that makes the suggested changes and updates AuthenticationTest to skip tests for unsupported algorithms.
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Attachments: derby-4602-1a.diff, derby-4602-1a.stat, j9errorsandfailures.txt, ListAlgorithms.java
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen reassigned DERBY-4602:
-----------------------------------------
Assignee: Knut Anders Hatlen
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Attachments: j9errorsandfailures.txt
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-4602.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.6.0.0
Thanks for testing the patch, Myrna!
Committed revision 929715.
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Fix For: 10.6.0.0
>
> Attachments: derby-4602-1a.diff, derby-4602-1a.stat, derby-4602-1b.diff, j9errorsandfailures.txt, ListAlgorithms.java, releaseNote.html
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851831#action_12851831 ]
Knut Anders Hatlen commented on DERBY-4602:
-------------------------------------------
Came to think about one issue... The 1a patch introduces a dependency on SHA-256 or SHA-1 being available at database creation time, even if the database does not actually use authentication. I think it would be better if it didn't fail when the database was created, but rather when/if the unsupported algorithm is attempted used, as it does today, so that it's still possible to create databases on JVMs without SHA-1 support as long as authentication is not used.
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Attachments: derby-4602-1a.diff, derby-4602-1a.stat, j9errorsandfailures.txt, ListAlgorithms.java
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852092#action_12852092 ]
Myrna van Lunteren commented on DERBY-4602:
-------------------------------------------
I tried out the test lang.GrantRevokeTest with the patch, and it fails without, and passes with the patch. I'll assume the other issues will work also, I'll try a full test run later to confirm, but any other fall-out can be addressed in a new issue... +1 from me.
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Attachments: derby-4602-1a.diff, derby-4602-1a.stat, derby-4602-1b.diff, j9errorsandfailures.txt, ListAlgorithms.java, releaseNote.html
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851485#action_12851485 ]
Knut Anders Hatlen commented on DERBY-4602:
-------------------------------------------
Thanks Myrna. Looks like we don't have many options on that platform, then. We could have a different default for weme, but then we may run into portability issues when moving a database created on another platform to weme, so I think having the same default on all platforms is the safest choice.
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Attachments: j9errorsandfailures.txt, ListAlgorithms.java
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4602) 10 failures & 11 errors with IBM
weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-4602:
--------------------------------------
Attachment: releaseNote.html
Attaching release note.
> 10 failures & 11 errors with IBM weme6.2/j9/cdc-foundation after revision 922304 for DERBY-4483
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-4602
> URL: https://issues.apache.org/jira/browse/DERBY-4602
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.6.0.0
> Environment: IBM's j2ME/cdc/foundation implementation (j9 jvm from weme6.2)
> Reporter: Myrna van Lunteren
> Assignee: Knut Anders Hatlen
> Attachments: derby-4602-1a.diff, derby-4602-1a.stat, j9errorsandfailures.txt, ListAlgorithms.java, releaseNote.html
>
>
> Since March 12 there's been 10 failures and 11 errors in the nightly test run with IBM's j2ME/CDC-foundation profile implementation, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-922467.html. Things were ok on March 10, see: http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-921667.html.
> I believe these were the effect of the following checkin for DERBY-4483:
> r922304 | kahatlen | 2010-03-12 08:01:20 -0800 (Fri, 12 Mar 2010) | 8 lines
> DERBY-4483: Provide a way to change the hash algorithm used by BUILTIN authentication
> I'll attach the full failure stacks in a separate file, but I believe perhaps new tests have been added that need to be excluded from the run, because the provider doesn't support the intended mechanism.
> I'd also be interested to know if these same failures occur with Sun's/Oracle's phoneME.
> This is the top of the first error:
> -------------------
> 1) testVariousBuiltinAlgorithms(org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest)java.sql.SQLException: The message digest algorithm 'SHA-256' is not supported by any of the available cryptography providers. Please install a cryptography provider that supports that algorithm, or specify another algorithm in the derby.authentication.builtin.algorithm property.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1208)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.setDatabaseProperty(AuthenticationTest.java:1218)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.AuthenticationTest.testVariousBuiltinAlgorithms(AuthenticationTest.java:1118)
> ------------------
> The failures are likely a result of this - the stack shows issues like no cleaning up of databases etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.