You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Diogo Sousa (JIRA)" <ji...@apache.org> on 2014/07/29 09:55:38 UTC

[jira] [Created] (DERBY-6679) Possible Atomicity Violation in BaseMonitor.shutdown()

Diogo Sousa created DERBY-6679:
----------------------------------

             Summary: Possible Atomicity Violation in BaseMonitor.shutdown()
                 Key: DERBY-6679
                 URL: https://issues.apache.org/jira/browse/DERBY-6679
             Project: Derby
          Issue Type: Bug
          Components: Services
    Affects Versions: 10.10.2.0
         Environment: all
            Reporter: Diogo Sousa
            Priority: Minor


In org.apache.derby.impl.services.monitor.BaseMonitor there might be an atomicity violation in method shutdown(), lines 181-206:

> 		for (;;) {
> 			synchronized (this) {
>   181:    		position = services.size()  - 1;
> 				if (position == 0)
> 					break;
>                                 ...
> 			}
>                         ...
> 		}
> 		...
>  206:	((TopService) services.get(0)).shutdown();

Between the execution of lines 181 and 206 a concurrent thread may remove the only remaining service, causing the access to "services" in line 206 to fail.



--
This message was sent by Atlassian JIRA
(v6.2#6252)