-
Bug
-
Resolution: Fixed
-
Low
-
3.0.5
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Summary:
There will be multiple WARN stack traces in the logs in regards of JIRA Service Desk Automation.
Steps to Reproduce.
- Create two Service Desk Project, e.g. SD A and SD B.
- On "SD B" navigate to the Project Administration > Automation.
- Create a "Reopen on Customer Comment" rule and confirm.
- Run the following Query:
select p.id,p.pname,pr."PROJECT_ID",rl."NAME",rl."DESCRIPTION",wh."MODULE_KEY" from "project" p right join "AO_9B2E3B_RSETREV_PROJ_CONTEXT" pr on (p.id = pr."PROJECT_ID") join "AO_9B2E3B_RULESET_REVISION" rl on (pr."RULESET_REVISION_ID" = rl."RULE_SET_ID") join "AO_9B2E3B_WHEN_HANDLER_CONFIG" wh on (rl."ID" = wh."ID");
- There will be a result for each project Automation Rule.
- Navigate to "SD B" project administration and delete the project.
- Create a Request in "SD A" and Resolved the ticket.
- As the Reporter, access the ticket in "Customer Portal" view and comment on the ticket.
Expected Result:
- Nothing happen as there is no "Reopen on Customer Comment" rule in "SD A" without any stack trace in the logs.
Actual Result:
- Nothing happen as well but there will be a WARN stack trace like below written in the logs.
2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project' 2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project' 2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project'
Notes:
- Run the same query below and there will be an automation rule that did not have any project specified as it is deleted:
select p.id,p.pname,pr."PROJECT_ID",rl."NAME",rl."DESCRIPTION",wh."MODULE_KEY" from "project" p right join "AO_9B2E3B_RSETREV_PROJ_CONTEXT" pr on (p.id = pr."PROJECT_ID") join "AO_9B2E3B_RULESET_REVISION" rl on (pr."RULESET_REVISION_ID" = rl."RULE_SET_ID") join "AO_9B2E3B_WHEN_HANDLER_CONFIG" wh on (rl."ID" = wh."ID");
- If we delete an existing Automation Rule while the Project is still exist, the row about that automation rule will still be exist.
- Tried to do the same for an Automation Rule that is deleted while the Project is still exist could not replicate the same stack trace to be thrown.
- This is WARN stack trace, it should not affect JIRA operations as it is a WARNING.
- has a regression in
-
JSDSERVER-6341 This is a regression bug of JSDSERVER-3232
-
- Closed
-
- relates to
-
JSDCLOUD-3232 Automation throws 'error.retrieving.project' WARN stack traces in the logs.
-
- Closed
-
-
JSDSERVER-3131 Warning messages on automation rule events in the log file
-
- Closed
-
-
JSMDC-3966 You do not have permission to view this issue
- mentioned in
-
Page Failed to load
- was cloned as
-
DESK-4594 Loading...
Form Name |
---|
[JSDSERVER-3232] Automation throws 'error.retrieving.project' WARN stack traces in the logs.
Remote Link | Original: This issue links to "JSDS-3966 (Bulldog)" [ 421054 ] | New: This issue links to "JSMDC-3966 (JIRA Server (Bulldog))" [ 421054 ] |
Remote Link | New: This issue links to "JSDS-3966 (Bulldog)" [ 421054 ] |
Link |
New:
This issue has a regression in |
Remote Link | New: This issue links to "Page (Confluence)" [ 420522 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304791 ] | New: JAC Bug Workflow v3 [ 3125496 ] |
Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
Workflow | Original: JSD Bug Workflow v5 [ 2059203 ] | New: JSD Bug Workflow v5 - TEMP [ 2304791 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056613 ] | New: JSD Bug Workflow v5 [ 2059203 ] |
Workflow | Original: JSD Bug Workflow v5 [ 1956275 ] | New: JSD Bug Workflow v5 - TEMP [ 2056613 ] |
Workflow | Original: JSD Bug Workflow v4 [ 1614838 ] | New: JSD Bug Workflow v5 [ 1956275 ] |
Description |
Original:
h3. Summary:
There will be multiple WARN stack traces in the logs in regards of JIRA Service Desk Automation. h3. Steps to Reproduce. # Create two Service Desk Project, e.g. SD A and SD B. # On "SD B" navigate to the _Project Administration > Automation_. # Create a "Reopen on Customer Comment" rule and confirm. # Run the following Query: {code:sql} select p.id,p.pname,pr."PROJECT_ID",rl."NAME",rl."DESCRIPTION",wh."MODULE_KEY" from "project" p right join "AO_9B2E3B_RSETREV_PROJ_CONTEXT" pr on (p.id = pr."PROJECT_ID") join "AO_9B2E3B_RULESET_REVISION" rl on (pr."RULESET_REVISION_ID" = rl."RULE_SET_ID") join "AO_9B2E3B_WHEN_HANDLER_CONFIG" wh on (rl."ID" = wh."ID"); {code} # There will be a result for each project Automation Rule. # Navigate to "SD B" project administration and delete the project. # Create a Request in "SD A" and Resolved the ticket. # As the Reporter, access the ticket in "Customer Portal" view and comment on the ticket. h3. Expected Result: * Nothing happen as there is no "Reopen on Customer Comment" rule in "SD A" without any stack trace in the logs. h3. Actual Result: * Nothing happen as well but there will be a WARN stack trace like below written in the logs. {code} 2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project' 2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project' 2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project' {code} h3. Notes: * Run the same query below and there will be an automation rule that did not have any project specified as it is deleted: {code:sql} select p.id,p.pname,pr."PROJECT_ID",rl."NAME",rl."DESCRIPTION",wh."MODULE_KEY" from "project" p right join "AO_9B2E3B_RSETREV_PROJ_CONTEXT" pr on (p.id = pr."PROJECT_ID") join "AO_9B2E3B_RULESET_REVISION" rl on (pr."RULESET_REVISION_ID" = rl."RULE_SET_ID") join "AO_9B2E3B_WHEN_HANDLER_CONFIG" wh on (rl."ID" = wh."ID"); {code} !Screen Shot 2016-01-01 at 6.25.49 PM.png|thumbnail! * If we delete an existing Automation Rule while the Project is still exist, the row about that automation rule will still be exist. * Tried to do the same for an Automation Rule that is deleted while the Project is still exist could not replicate the same stack trace to be thrown. * This is WARN stack trace, it should not affect JIRA operations as it is a WARNING. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-3232]. {panel} h3. Summary: There will be multiple WARN stack traces in the logs in regards of JIRA Service Desk Automation. h3. Steps to Reproduce. # Create two Service Desk Project, e.g. SD A and SD B. # On "SD B" navigate to the _Project Administration > Automation_. # Create a "Reopen on Customer Comment" rule and confirm. # Run the following Query: {code:sql} select p.id,p.pname,pr."PROJECT_ID",rl."NAME",rl."DESCRIPTION",wh."MODULE_KEY" from "project" p right join "AO_9B2E3B_RSETREV_PROJ_CONTEXT" pr on (p.id = pr."PROJECT_ID") join "AO_9B2E3B_RULESET_REVISION" rl on (pr."RULESET_REVISION_ID" = rl."RULE_SET_ID") join "AO_9B2E3B_WHEN_HANDLER_CONFIG" wh on (rl."ID" = wh."ID"); {code} # There will be a result for each project Automation Rule. # Navigate to "SD B" project administration and delete the project. # Create a Request in "SD A" and Resolved the ticket. # As the Reporter, access the ticket in "Customer Portal" view and comment on the ticket. h3. Expected Result: * Nothing happen as there is no "Reopen on Customer Comment" rule in "SD A" without any stack trace in the logs. h3. Actual Result: * Nothing happen as well but there will be a WARN stack trace like below written in the logs. {code} 2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project' 2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project' 2016-01-01 20:44:14,471 http-nio-8705-exec-4 WARN admin 1244x2604x1 1rreza0 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk/customer/comment [c.a.s.p.a.i.e.whenhandler.event.AllEventListenerEventWhenHandlerVisitor] Event when handler execution of com.atlassian.servicedesk.plugins.automation.servicedesk-automation-modules-plugin:servicedesk-commented-automation-rule-event-when-handler failed with error error.retrieving.project : 'error.retrieving.project' {code} h3. Notes: * Run the same query below and there will be an automation rule that did not have any project specified as it is deleted: {code:sql} select p.id,p.pname,pr."PROJECT_ID",rl."NAME",rl."DESCRIPTION",wh."MODULE_KEY" from "project" p right join "AO_9B2E3B_RSETREV_PROJ_CONTEXT" pr on (p.id = pr."PROJECT_ID") join "AO_9B2E3B_RULESET_REVISION" rl on (pr."RULESET_REVISION_ID" = rl."RULE_SET_ID") join "AO_9B2E3B_WHEN_HANDLER_CONFIG" wh on (rl."ID" = wh."ID"); {code} !Screen Shot 2016-01-01 at 6.25.49 PM.png|thumbnail! * If we delete an existing Automation Rule while the Project is still exist, the row about that automation rule will still be exist. * Tried to do the same for an Automation Rule that is deleted while the Project is still exist could not replicate the same stack trace to be thrown. * This is WARN stack trace, it should not affect JIRA operations as it is a WARNING. |