[
https://issues.apache.org/jira/browse/DERBY-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492825
]
Myrna van Lunteren commented on DERBY-1496:
-------------------------------------------
Dan had suggested on the list, that this test be rewritten to use the testSetup
mechanism to start and shutdown the server.
I have attempted this approach but it's not as appropriate with this particular
test - starting the server (with each security mechanism, invalid, or not) is
part of the test.
Also, once the server is started with a particular mechanism, connections need
to specify that mechanim or fail - and so teardown fails.
Finally, for each security mechanism, the expected values of each check is
different.
In the end, the test got really, really complicated and messy,
I then attempted to create new databases for each security mechanism, but that
also got very messy.
In the end the solution was simple: shutdown the database in all cases (already
happened for 2 of the security mechanism settings). before shutting down the
server. Then, no wait was needed before attempting connections.
So, after revision 533889, the NSSecurityMechanismTest should run a bit faster.
> 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
> Fix For: 10.3.0.0
>
> Attachments: authtest_clear_prop.txt, DERBY-1496_20070306.diff,
> DERBY-1496_20070306.stat, DERBY-1496_20070321.diff,
> 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.
