[ http://issues.apache.org/jira/browse/DERBY-1695?page=comments#action_12428847 ] Kathey Marsden commented on DERBY-1695: ---------------------------------------
Well I did see this pass once with the upped timeout, but now seem to reliably get: > FAIL: Server failed to respond to ping - ending test with firewall turned on and ping time set to 120. I am sorry I won't be able to update the masters for this issue. Kathey > 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 > > 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
