[ http://issues.apache.org/jira/browse/DERBY-1794?page=comments#action_12431981 ] Daniel John Debrunner commented on DERBY-1794: ----------------------------------------------
It would be good to have consistency in the way tests wait for the network server to start. A single method with the time set within the method not by the caller. In looking at htese related failures it seemed every test re-invented the way to wait for the network server and had a different amount of time to wait. Maybe indicates this functionality should be a utility method in the network server api itself. > Should create a test that verifies acceptable performance of network server > startup > ----------------------------------------------------------------------------------- > > Key: DERBY-1794 > URL: http://issues.apache.org/jira/browse/DERBY-1794 > Project: Derby > Issue Type: Test > Components: Test > Affects Versions: 10.3.0.0 > Reporter: Mike Matrigali > > A number of tests in the regression suite rely on starting up a network > server and subsequently connecting to it. Each tends to have some sort of > "wait" mechanism and may fail if the wait is "too" long. It is often sort > of cryptic to tell why these tests have failed if the real reason is the > network server did not start in a reasonable amount of time. It would be > good to develop a test that specifically looked at network server start up > time and verified from release to release that it was behaving correctly. -- 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
