[jira] Updated: (DERBY-1695) testSecMec.java fails with JCC 2.6 and JCC 2.8

["Sunitha Kambhampati (JIRA)" <de...@db.apache.org>]

     [ http://issues.apache.org/jira/browse/DERBY-1695?page=all ]

Sunitha Kambhampati updated DERBY-1695:
---------------------------------------

    Attachment: derby1695.diff.txt
                Derby1695.stat.txt

Updated the master files for jcc2.6 and jcc2.8, the diffs were being caused because of derby-528 checkin.

-- Ran the testSecMec test with jcc2.4, jcc2.6 and jcc2.8 on ibm131/ibm142/ibm15, jdk131/jdk142/jdk15 ok. 

Francois, it would be great if you could review these changes as they are related to the derby-528.

If this looks ok, can someone please commit this. 

Thanks. 

> testSecMec.java fails with JCC 2.6 and JCC 2.8
> ----------------------------------------------
>
>                 Key: DERBY-1695
>                 URL: http://issues.apache.org/jira/browse/DERBY-1695
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.2.1.0
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: derby1695.diff.txt, Derby1695.stat.txt
>
>
> After the checkin for DERBY-528 testSecMec fails with JCC 2.6 and 2.8.  My hope was to just wait until the masters were normalized with the conversion of this test to Junit, but I think that work has been deferred for a bit so I will look at the current test.
> I have had a problem with this test on my machine for sometime with DERBY-1114 like symptoms with all jvms and even with derbyclient.  I need to investigate that or run on another machine to resolve this issue.  

-- 
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