db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1871) testSecMec failing with what looks like just a error message change diff
Date Fri, 08 Dec 2006 20:40:21 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1871?page=all ]

Andrew McIntyre updated DERBY-1871:
-----------------------------------

    Fix Version/s: 10.1.4.0
                       (was: 10.1.3.2)
         Priority: Minor  (was: Major)

Marking minor, difference in exception text between jvms, consolidating with 10.1.4 bugs.

> testSecMec failing with what looks like just a error message change diff
> ------------------------------------------------------------------------
>
>                 Key: DERBY-1871
>                 URL: http://issues.apache.org/jira/browse/DERBY-1871
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.1.3.2
>            Reporter: Mike Matrigali
>            Priority: Minor
>             Fix For: 10.1.4.0
>
>
> 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 ***

-- 
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

        

Mime
View raw message