db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4418) derbyall/encryptionAll/encryptionAll/aes fails on 10.4, 10.3 and 10.2 with Sun JVM 1.6.0_15 on Solaris
Date Sun, 11 Jul 2010 21:11:49 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali updated DERBY-4418:
----------------------------------


it looks like we should just accept the different error message for the new sun jvm.  I think
if you just add the new master file to the jdk16 directory in the master directory it should
be fine.  I would do it but don't have the new sun jvm on my machine to try it out.

> derbyall/encryptionAll/encryptionAll/aes fails on 10.4, 10.3 and 10.2 with Sun JVM 1.6.0_15
on Solaris
> ------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4418
>                 URL: https://issues.apache.org/jira/browse/DERBY-4418
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>         Environment: OS:
> Solaris 10 5/08 s10x_u5wos_10 X86 64bits
> SunOS 5.10 Generic_127128-11
> JVM:
> Sun Microsystems Inc.
> java version "1.6.0_15"
> Java(TM) SE Runtime Environment (build 1.6.0_15-b03)
> Java HotSpot(TM) Server VM (build 14.1-b02, mixed mode)
> Derby:
> 10.4.2.1 - (828072)
> 10.3.3.1 - (827984)
> 10.2.2.1 - (828222)
>            Reporter: Ole Solberg
>
> derbyall/encryptionAll/encryptionAll/aes fails on 10.4, 10.3 and 10.2 with Sun JVM 1.6.0_15
on Solaris with a diff like this:
> ********* Diff file derbyall/encryptionAll/encryptionAll/aes.diff
> *** Start: aes jdk1.6.0_15 encryptionAll:encryptionAll 2009-10-21 20:37:04 ***
> 222 del
> < ERROR XJ001: Java exception: 'Wrong keysize: must be equal to 128, 192 or 256: java.security.InvalidParameterException'.
> 222a222,223
> > ERROR XJ001: Java exception: ': java.security.InvalidParameterException'.
> > ERROR XJ001: Java exception: 'Key length must be between 128 and 256 bits: java.security.InvalidAlgorithmParameterException'.
> Test Failed.
> *** End:   aes jdk1.6.0_15 encryptionAll:encryptionAll 2009-10-21 20:37:14 ***
> See e.g.
> http://dbtg.foundry.sun.com/derby/test/tinderbox_10.4_16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/828072-derbyall_diff.txt
> http://dbtg.foundry.sun.com/derby/test/tinderbox_10.3_16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/827984-derbyall_diff.txt
> http://dbtg.foundry.sun.com/derby/test/tinderbox_10.2_16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/828222-derbyall_diff.txt
> It seems this was caused by going from Sun JVM 1.6.0_06 to Sun JVM 1.6.0_15, build and
run.
> I will investigate further...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message