cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangeetha Hariharan (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CLOUDSTACK-1664) Action Events are not logged due to spring changes
Date Wed, 27 Mar 2013 20:17:15 GMT

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

Sangeetha Hariharan reopened CLOUDSTACK-1664:
---------------------------------------------


Tested with latest build form 4.1:

I do see events for Create User being generated as part creating Account as well as creating
a user:


| 167 | 99c24cff-9ed3-4c12-812d-bf06f71d8ab2 | USER.CREATE | Completed | Successfully completed
creating User. Account Name: tan, Domain Id:1 | 2 | 1 | 1 | 2013-03-27 20:06:52 | INFO | 0
| NULL |
| 168 | 0e446154-5db9-4607-8494-7a6f9e4cb220 | ACCOUNT.CREATE | Completed | Successfully completed
creating Account. Account Name: tan, Domain Id:1 | 2 | 1 | 1 | 2013-03-27 20:06:52 | INFO
| 0 | NULL |




But I still do not see events being generated for the following actions:

1. Generating keys for user - registerUserKeys() API
2. Enabling account
3. Editing account 

Reopening this issue to fix the even generation for these activities.
                
> Action Events are not logged due to spring changes
> --------------------------------------------------
>
>                 Key: CLOUDSTACK-1664
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1664
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>         Environment: Build from 4.1
>            Reporter: Sangeetha Hariharan
>            Assignee: Kelven Yang
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> ActionEvent annotations are in manager Impl. Spring proxies the interface and not the
implementing class. Since there are not annotations at the interface level, needToIntercept
method in ActionEventInterceptor always returns false.
> TransactionContextBuilder intercepts by getting the implementing class and going through
all the methods in it to match the method name. Going through all the methods every time may
not be efficient. There could be multiple methods with same name, so matching by method name
could be error prone aswell.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message