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 "Sunitha Kambhampati (JIRA)" <de...@db.apache.org> on 2006/09/20 23:40:22 UTC
[jira] Commented: (DERBY-1871) testSecMec failing with what looks
like just a error message change diff
[ http://issues.apache.org/jira/browse/DERBY-1871?page=comments#action_12436360 ]
Sunitha Kambhampati commented on DERBY-1871:
--------------------------------------------
Some notes:
1) This test (testSecMec.java on DerbyNetClient framework) passes OK on windows using Sun JCE as
well as IBMJCE. Works fine with 10.1.3.2 on Sun vms 1.3.1,1.4.2,1.5, IBM jvms - 1.3.1,1.4.2,1.5
2) The diff as shown in the description is a error message difference only. My guess is that maybe the
JCE provider on the tinderbox solaris machine is not the same as the Sun JCE.
One possible solution is trying to sed' this out or better -convert this test to a junit test ( derby1496).
fwiw, the Sun jdk1.5.0 version that I tested with is
java version "1.5.0_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09)
Java HotSpot(TM) Client VM (build 1.5.0_02-b09, mixed mode)
> 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
> Fix For: 10.1.3.2
>
>
> 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