[
https://issues.apache.org/jira/browse/CLOUDSTACK-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006564#comment-14006564
]
Kelven Yang commented on CLOUDSTACK-6595:
-----------------------------------------
After Darren made the change to use Spring proxy mode. @ActionEvent facility is
no longer to fully work in all scenarios: when it is annotated in a method that
may be called from methods that are at same class, @ActionEvent will NOT be
triggered.
This is the limitation from Spring proxy-based injection mode. Unfortunately we
can't go back, therefore, @ActionEvent facility can only be used in limited
situations now, if developer who relies on it but does not work under his/her
scenarios, the developer needs to do it programmatically instead of using
@ActionEvent
> Action event EVENT_VM_EXPUNGE is not generated when vm is expunged by the
> background expunge thread
> ---------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6595
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6595
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.4.0
> Reporter: Alena Prokharchyk
> Assignee: Kelven Yang
> Priority: Critical
> Fix For: 4.4.0
>
>
> When expungeVm is called using client API, EVENT_VM_EXPUNGE event is
> generated.
> When vm is destroyed through the API, but expunged by the background expunge
> thread, the event is missing. The event should be generated regardless of
> which way the expunge was triggered.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
