[ http://issues.apache.org/jira/browse/DERBY-1496?page=all ]
Myrna van Lunteren reassigned DERBY-1496:
-----------------------------------------
Assign To: Myrna van Lunteren
> testSecMec fails with jcc2.8 with 131 jvms
> ------------------------------------------
>
> Key: DERBY-1496
> URL: http://issues.apache.org/jira/browse/DERBY-1496
> Project: Derby
> Type: Improvement
> Components: Test
> Versions: 10.2.0.0
> Reporter: Sunitha Kambhampati
> Assignee: Myrna van Lunteren
> Priority: Minor
>
> derbynet/testSecMec.java fails with jcc2.8 with 131 vms. I have checked the
> diff and it is a master update with difference in the exception, message
> string.
> diff snippet:
> 8 del
> < T5:
> jdbc:derby:net://xxxFILTERED_HOSTNAMExxx:xxxFILTEREDPORTxxx/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)'
> 8a8
> > T5:
> > jdbc:derby:net://xxxFILTERED_HOSTNAMExxx:xxxFILTEREDPORTxxx/wombat:user=neelima;password=lee;securityMechanism=9;
> > - EXCEPTION java.security.NoSuchAlgorithmException is caught when
> > initializing EncryptionManager 'DH KeyPairGenerator not available'
> 14 del
> ----------------
> There is difference in the exception message and will require lot of jvm
> specific master files which can become difficult to maintain. Myrna
> suggested that this might be a good test to convert to junit.
--
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
