Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
10.1.3.2
-
None
-
None
-
Regression Test Failure
Description
The nightly tinderbox runs against 10.1 are getting the following diff. Though minor it would be nice to fix as it looks like the last issue stopping
the runs from running with 0 diffs. This issue looks like it has been around since 5/5/06 (that is the latest history I found in the tinderbox reports).
tinderbox history is at:
http://www.multinet.no/~solberg/public/Apache/TinderBox-10.1/Limited/index_all.html
latest instance of the problem:
http://www.multinet.no/~solberg/public/Apache/TinderBox-10.1/testlog/SunOS-5.10_i86pc-i386/439213-derbyall_diff.txt
actual diff:
-
-
-
-
-
-
-
-
- Diff file derbyall/derbynetclientmats/DerbyNetClient/derbynetmats/derbynetmats/testSecMec.diff
-
-
-
-
-
- Start: testSecMec jdk1.5.0_04 DerbyNetClient derbynetmats:derbynetmats 2006-09-01 10:45:38 ***
6 del
< T5: jdbc:derby://localhost:20000/wombat;user=neelima;password=lee;securityMechanism=9 - EXCEPTION java.security.InvalidAlgorithmParameterException is caught when initializing EncryptionManager 'Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive)'
6a6
> T5: jdbc:derby://localhost:20000/wombat;user=neelima;password=lee;securityMechanism=9 - EXCEPTION java.security.InvalidAlgorithmParameterException is caught when initializing EncryptionManager 'Key size must be at least 512 bit'
10 del
< SECMEC_EUSRIDPWD:EXCEPTION testSecurityMechanism() java.security.InvalidAlgorithmParameterException is caught when initializing EncryptionManager 'Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive)'
10a10
> SECMEC_EUSRIDPWD:EXCEPTION testSecurityMechanism() java.security.InvalidAlgorithmParameterException is caught when initializing EncryptionManager 'Key size must be at least 512 bit'
Test Failed. - End: testSecMec jdk1.5.0_04 DerbyNetClient derbynetmats:derbynetmats 2006-09-01 10:45:48 ***
-
-