[
https://issues.apache.org/jira/browse/DERBY-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481303
]
Daniel John Debrunner commented on DERBY-1496:
----------------------------------------------
I'm a little confused on AuthenticationTest.assertSystemShutdownFail
The method name would indicate that it's asserting that an attempt to shutdown
the system should fail,
but the code is perfoming a database shutdown. There's some comment about not
using the database name in
the comment to the method causes some problems, but I'm not sure having the
code perform a different action is the correct solution.
I'd also assumed that to have a DataSource connect to the system a null
databaseName would be used, but this test uses a zero-length
database name. No idea which is correct or if it's documented one-way or
another.
> testSecMec needs many masters - should convert to junit
> -------------------------------------------------------
>
> Key: DERBY-1496
> URL: https://issues.apache.org/jira/browse/DERBY-1496
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Sunitha Kambhampati
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Attachments: authtest_clear_prop.txt, DERBY-1496_20070306.diff,
> DERBY-1496_20070306.stat, DERBY-1496_tmp_072206.diff,
> DERBY-1496_tmp_072206.stat
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
