[ http://issues.apache.org/jira/browse/DERBY-324?page=comments#action_12313813 ]
Olav Sandstaa commented on DERBY-324: ------------------------------------- This patch fixes a problem in the AES test when running it on Solaris 10. The problem occurred due to a exception message text has been changed on Solaris 10. The problem is fixed by extending the substitute section of the aes_sed.properties file. derbyall has been run on Solaris10 (sparc and x86) to verify that the problem is gone and on Solaris9 (sparc and x86) and Linux to verify that the change does not influence on JVM producing the original error message text. Although some tests failed none of these seems related to this fix. > AES encryption test fails on Solaris 10 > --------------------------------------- > > Key: DERBY-324 > URL: http://issues.apache.org/jira/browse/DERBY-324 > Project: Derby > Type: Bug > Components: Test > Versions: 10.1.0.0 > Environment: Solaris 10 (both Sparc and x86) jdk 1.4 and 1.5. > Reporter: Olav Sandstaa > Assignee: Olav Sandstaa > Priority: Minor > Attachments: aes_sol10.diff, aes_sol10.stat > > The store/aes.sql test on Solaris 10 produces the following diff report: > *** Start: aes jdk1.4.2_02 2005-05-30 12:13:17 *** > 206 del > < ERROR XJ001: Java exception: 'Wrong keysize: must be equal to 128, 192 or > 256: java.security.InvalidParameterException'. > 206a206 > > ERROR XJ001: Java exception: 'AES key length must be 128, 192, or 256 bits: > > java.security.InvalidParameterException'. > Test Failed. > *** End: aes jdk1.4.2_02 2005-05-30 12:14:06 *** > The cause of this problem is that on most OSs, the > java.security.InvalidParameterException thrown by the JVM when an invalid > encryption key length is requested contains a message with the following text: > Wrong keysize: must be equal to 128, 192 or 256 > while on Solaris 10 the message contained in the exception has been changed > to: > AES key length must be 128, 192, or 256 bits > The reason for this is most likely that a different encryption library is > included in Solaris 10 compared > to the other OSs, either as part of the JVM or as a native library. > The problem occurs on Solaris 10 running on both x86 and Sparc processors. It > occurs both with jdk 1.4 and jdk 1.5. -- 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
