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 "Andrew McIntyre (JIRA)" <de...@db.apache.org> on 2005/06/30 09:02:57 UTC
[jira] Created: (DERBY-417) Beetle6038.java store test fails on Mac OS X
Beetle6038.java store test fails on Mac OS X
--------------------------------------------
Key: DERBY-417
URL: http://issues.apache.org/jira/browse/DERBY-417
Project: Derby
Type: Test
Components: Test
Versions: 10.1.1.0, 10.2.0.0
Environment: Mac OS X 10.4.1 with JDK 1.4.2
Reporter: Andrew McIntyre
Priority: Trivial
Fix For: 10.2.0.0
Beetle6038.java test in the storemore suite fails on Mac OS X because the test attempts to set the encryption provider for the test based on the value of the system property java.vm.vendor. It assumes that if java.vm.vendor does not start with "Sun" that the IBM JCE encryption provider should be used. See org.apache.derbyTesting.functionTests.tests.store.Beetle6038, lines 42-49.
Since, in most cases, Derby can choose the correct encryption provider, I think the best solution to this particular issue is to not specify a particular implementation of the JCE provider, regardless of the JVM vendor. i.e. lines 42-49 can probably be wholly replaced by:
dburl="jdbc:derby:Beetle6038Db;create=true;dataEncryption=true;bootPassword=Thursday;encryptionAlgorithm=DES/CBC/NoPadding";
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-417) Beetle6038.java store test fails on
Mac OS X
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-417?page=all ]
Andrew McIntyre resolved DERBY-417:
-----------------------------------
Resolution: Fixed
Committed revision 380287.
> Beetle6038.java store test fails on Mac OS X
> --------------------------------------------
>
> Key: DERBY-417
> URL: http://issues.apache.org/jira/browse/DERBY-417
> Project: Derby
> Type: Test
> Components: Test
> Versions: 10.1.1.0, 10.2.0.0
> Environment: Mac OS X 10.4.1 with JDK 1.4.2
> Reporter: Andrew McIntyre
> Assignee: Andrew McIntyre
> Priority: Trivial
> Fix For: 10.2.0.0
>
> Beetle6038.java test in the storemore suite fails on Mac OS X because the test attempts to set the encryption provider for the test based on the value of the system property java.vm.vendor. It assumes that if java.vm.vendor does not start with "Sun" that the IBM JCE encryption provider should be used. See org.apache.derbyTesting.functionTests.tests.store.Beetle6038, lines 42-49.
> Since, in most cases, Derby can choose the correct encryption provider, I think the best solution to this particular issue is to not specify a particular implementation of the JCE provider, regardless of the JVM vendor. i.e. lines 42-49 can probably be wholly replaced by:
> dburl="jdbc:derby:Beetle6038Db;create=true;dataEncryption=true;bootPassword=Thursday;encryptionAlgorithm=DES/CBC/NoPadding";
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-417) Beetle6038.java store test fails on Mac OS X
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-417?page=all ]
Andrew McIntyre reassigned DERBY-417:
-------------------------------------
Assign To: Andrew McIntyre
> Beetle6038.java store test fails on Mac OS X
> --------------------------------------------
>
> Key: DERBY-417
> URL: http://issues.apache.org/jira/browse/DERBY-417
> Project: Derby
> Type: Test
> Components: Test
> Versions: 10.1.1.0, 10.2.0.0
> Environment: Mac OS X 10.4.1 with JDK 1.4.2
> Reporter: Andrew McIntyre
> Assignee: Andrew McIntyre
> Priority: Trivial
> Fix For: 10.2.0.0
>
> Beetle6038.java test in the storemore suite fails on Mac OS X because the test attempts to set the encryption provider for the test based on the value of the system property java.vm.vendor. It assumes that if java.vm.vendor does not start with "Sun" that the IBM JCE encryption provider should be used. See org.apache.derbyTesting.functionTests.tests.store.Beetle6038, lines 42-49.
> Since, in most cases, Derby can choose the correct encryption provider, I think the best solution to this particular issue is to not specify a particular implementation of the JCE provider, regardless of the JVM vendor. i.e. lines 42-49 can probably be wholly replaced by:
> dburl="jdbc:derby:Beetle6038Db;create=true;dataEncryption=true;bootPassword=Thursday;encryptionAlgorithm=DES/CBC/NoPadding";
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-417) Beetle6038.java store test fails on Mac
OS X
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-417?page=all ]
Andrew McIntyre closed DERBY-417:
---------------------------------
> Beetle6038.java store test fails on Mac OS X
> --------------------------------------------
>
> Key: DERBY-417
> URL: http://issues.apache.org/jira/browse/DERBY-417
> Project: Derby
> Type: Test
> Components: Test
> Versions: 10.1.1.0, 10.2.0.0
> Environment: Mac OS X 10.4.1 with JDK 1.4.2
> Reporter: Andrew McIntyre
> Assignee: Andrew McIntyre
> Priority: Trivial
> Fix For: 10.2.0.0
>
> Beetle6038.java test in the storemore suite fails on Mac OS X because the test attempts to set the encryption provider for the test based on the value of the system property java.vm.vendor. It assumes that if java.vm.vendor does not start with "Sun" that the IBM JCE encryption provider should be used. See org.apache.derbyTesting.functionTests.tests.store.Beetle6038, lines 42-49.
> Since, in most cases, Derby can choose the correct encryption provider, I think the best solution to this particular issue is to not specify a particular implementation of the JCE provider, regardless of the JVM vendor. i.e. lines 42-49 can probably be wholly replaced by:
> dburl="jdbc:derby:Beetle6038Db;create=true;dataEncryption=true;bootPassword=Thursday;encryptionAlgorithm=DES/CBC/NoPadding";
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira