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 "Mike Matrigali (JIRA)" <de...@db.apache.org> on 2006/09/20 17:38:24 UTC
[jira] Created: (DERBY-1871) testSecMec failing with what looks
like just a error message change diff
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.2 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
[jira] Commented: (DERBY-1871) testSecMec failing with what looks
like just a error message change diff
Posted by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-1871) testSecMec failing with what looks
like just a error message change diff
Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (DERBY-1871) testSecMec failing with what looks
like just a error message change diff
Posted by "Andrew McIntyre (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew McIntyre updated DERBY-1871:
-----------------------------------
Fix Version/s: (was: 10.1.4.0)
Unsetting Fix Version on Unassigned issues. Sending mail for these because these should be reviewed to see if they are still valid issues.
> testSecMec failing with what looks like just a error message change diff
> ------------------------------------------------------------------------
>
> Key: DERBY-1871
> URL: https://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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1871) testSecMec failing with what looks
like just a error message change diff
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1871?page=all ]
Mike Matrigali updated DERBY-1871:
----------------------------------
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 ***
was:
The nightly tinderbox runs against 10.2 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 ***
> 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
[jira] Updated: (DERBY-1871) testSecMec failing with what looks
like just a error message change diff
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1871?page=all ]
Mike Matrigali updated DERBY-1871:
----------------------------------
what confused me was that it seems to pass in the 10.2 nightly tinderbox but fail in the 10.1 nightly tinderbox. So either the environment is different or there is some fix that was already made that could be backported to 10.1. Anyone recognize this issue?
> 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
[jira] Resolved: (DERBY-1871) testSecMec failing with what looks
like just a error message change diff
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-1871.
-----------------------------------
Resolution: Won't Fix
The 10.1 tinderbox tests are no longer being run. Resolving as won't fix.
> testSecMec failing with what looks like just a error message change diff
> ------------------------------------------------------------------------
>
> Key: DERBY-1871
> URL: https://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
>
> 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.
-
You can reply to this email to add a comment to the issue online.