db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1496) testSecMec needs many masters - should convert to junit
Date Thu, 22 Mar 2007 00:22:32 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Myrna van Lunteren updated DERBY-1496:

    Attachment: DERBY-1496_20070321.diff

attaching a patch that does the following:

- uses ds.setConnectionAttributes rather than ds.setShutDownDatabase().
   The test DriverMgrAuthenticationTest ran into failures on tearDown in clientServer.  I
left the old mechanism commented out, with comments...I know normally we'd rely on the svn
logs, but I thought in this particular case it might
be helpful to have the alternative approach in the method.

- remove the system property setting in tearDown()
- test now sleeps a bit longer - on my system I was still getting 08001 
- resolve a javadoc problem
- suite() methods uses SystemPropertySetup in addition to DatabasePropertySetup.
- suite() and baseSuite() methods are streamlined.
- system level property removed via tearDown method.
-  (more) system shutdown testing done in a separate test case
- system shutdown calls are fixed to actually attempt to shutdown the system (my previous
problems with getting this to work properly were because I had only set the requireAuthentication
to true at databaselevel.)  
- added more comments to some of the methods

DriverMgrAuthenticationTest.java, PoolDSAuthenticationTest.java, XADSAuthenticationTest.java:
- adjusted suite, baseSuite, and systemshutdown methods to match AuthenticationTest changes.

- added 4 tests

- added NSSecurityMechanismTest

suites.All was successful with jdk14. 

I will commit this.

> 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:
>            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_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.

View raw message