geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Viet Hung Nguyen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-3524) monitoring server has problems with stop/starting snapshot
Date Wed, 10 Oct 2007 01:08:50 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Viet Hung Nguyen updated GERONIMO-3524:
---------------------------------------

    Attachment: geronimo-3524.patch

the patch stops snapshots by setting a flag to 'true' as opposed to setting the snapshot duration
to Long.MAX_VALUE.

it also interrupts() the sleep() so that the thread will die soon thereafter as opposed to
having an upper bound of the duration time as the time it takes to die.

> monitoring server has problems with stop/starting snapshot
> ----------------------------------------------------------
>
>                 Key: GERONIMO-3524
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3524
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: monitoring
>         Environment: windows
>            Reporter: Viet Hung Nguyen
>         Attachments: geronimo-3524.patch
>
>
> the thread that executes the snapshots is using Thread.sleep(x). A condition is checked
in between these sleeps to know whether or not to continue the thread. This means that the
thread is not stopped immediately. In fact, it can take up to X (the duration between snapshots)
seconds before it comes to a full stop. As a result, this affects the starting feature because
it is restricted to have only one thread running at any given time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message