db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomohito Nakayama (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-273) The derbynet/dataSourcePermissions_net.java test fails intermittently
Date Mon, 20 Jun 2005 12:46:36 GMT
    [ http://issues.apache.org/jira/browse/DERBY-273?page=comments#action_12314045 ] 

Tomohito Nakayama commented on DERBY-273:

To accomplish plan-2,
count of session need to be polled to know wheter all session was closed ...

There are next two option.

Adding NetworkServerControl#getCountOfSession() method , which retrieve count of sessions
from NetworkServerControl.

Using getRuntimeInfo() method and parse result of it.

In a glance , option1 seems to be straight answer.
However , NetworkServerControl#getCountOfSession() have wrong impact to make confusion in
Because count of session would be vary after the value is retrieved , accessd by other threads.

I think count of session is very private information in NetworkServerControl , 
and should not be retrieved directly from NetworkServerControl.

I think it is moderate to take option2 ,
regarding user checking state of connection seeing getRuntimeInfo ...

> 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
> *** 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:
For more information on JIRA, see:

View raw message