[ http://issues.apache.org/jira/browse/DERBY-273?page=comments#action_12313468 ]
Kathey Marsden commented on DERBY-273: -------------------------------------- I have two ideas, neither of which seem ideal but maybe they will give you a better idea. 1) If the exception is intermittent but not harmful you could specify an alternate consoleWriter when you call NetworkServerControl.start(). This way the exception does not print to System.out. This would mean that dataSourcePermissions_net.java would suffer the same deficiencey as the other tests, that the console is not monitored properly by the test. 2) The NetworkServerControl method getRuntimeInfo will show the connection info from the server's perspective. You could alternately sleep for a few seconds and call this method to see the connections from the server perspective. The output is a string that would need to be parsed. It has output that looks like: # Connection Threads : 2 # Active Sessions : 2 # Waiting Sessions : 0 And always includes one session for the runtimeinfo request. > The derbynet/dataSourcePermissions_net.java test fails intermittently > --------------------------------------------------------------------- > > Key: DERBY-273 > URL: http://issues.apache.org/jira/browse/DERBY-273 > Project: Derby > Type: Bug > Environment: 1.4.2 JVM (both Sun and IBM) > Reporter: Jack Klebanoff > Assignee: Tomohito Nakayama > > The test fails in the derbyall/derbynetclientmats/derbynetmats suite stack > with the following diff: > *** Start: dataSourcePermissions_net jdk1.4.2 DerbyNetClient > derbynetmats:derbynetmats 2005-05-11 04:24:11 *** > 17a18,19 > > org.apache.derby.iapi.services.context.ShutdownException: > > agentThread[DRDAConnThread_2,5,derby.daemons] > Test Failed. -- 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
