db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1496) testSecMec fails with jcc2.8 with 131 jvms
Date Fri, 28 Jul 2006 00:39:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1496?page=comments#action_12423968 ] 
            
Daniel John Debrunner commented on DERBY-1496:
----------------------------------------------

I think issue with the permissions is that calls to privilege actions are not in privlege
blocks.
WIth the test harness that was ok because it was granted the permission and was at the top
of the calling stack.
With JUnit, the JUnit code is at the top of the stack and so either it needs to be granted
the permissions, or ther cleaner
approach is to have the calls in a privilege block, e.g. see BaseTestCase.setSystemProperty.

> testSecMec fails with jcc2.8 with 131 jvms
> ------------------------------------------
>
>                 Key: DERBY-1496
>                 URL: http://issues.apache.org/jira/browse/DERBY-1496
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.2.0.0
>            Reporter: Sunitha Kambhampati
>         Assigned To: Myrna van Lunteren
>            Priority: Minor
>         Attachments: 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.
-
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

        

Mime
View raw message