Restrict Workflow Validator error messages in the log file

Srinivas Patruni March 13, 2014

can we restrict the following error messages from the log file? These are the error messages from the workflow validators (required fields)

2014-03-14 11:12:39,084 http-bio-80-exec-6 ERROR spatruni 672x17018x2 1z10pjm 10.107.182.119 /secure/CommentAssignIssue.jspa [atlassian.jira.workflow.OSWorkflowManager] Caught exception while attempting to perform action 21 from workflow 560260 on issue 'BUG-713'
[InvalidInputException: [Error map: [{customfield_10080=Resolver is required.}]] [Error list: [[]]]
2014-03-14 11:07:48,096 http-bio-80-exec-5 ERROR spatruni 667x16491x2 uvyaht 10.107.182.119 /secure/CommentAssignIssue.jspa [atlassian.jira.workflow.OSWorkflowManager] Caught exception while attempting to perform action 21 from workflow 560260 on issue 'BUG-713'
[InvalidInputException: [Error map: [{fixVersions=Fix Version/s is required.}]] [Error list: [[]]]

2 answers

1 accepted

0 votes
Answer accepted
Boris Georgiev _Appfire_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 14, 2014

You can turn it off by adding a line (as shown below) to the log4j.properties file

log4j.logger.atlassian.jira.workflow.OSWorkflowManager = OFF

Find details about locating the log4j config file and changing logging levels here:

https://confluence.atlassian.com/display/JIRA/Logging+and+Profiling

Srinivas Patruni March 14, 2014

But that requires JIRA restart.. Is there a way to handle without restarting JIRA?

Boris Georgiev _Appfire_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 14, 2014

Just saw the package/class name was wrong.

Did you tried with com.atlassian.jira.workflow.OSWorkflowManager ?

Srinivas Patruni March 14, 2014

Thank you Boris, I have added the package name and set the logging level to off but the error messages in the log are still printing.

Srinivas Patruni March 14, 2014

Ok the problem was I had added the package name "log4j.logger.atlassian.jira.workflow.OSWorkflowManager" but I should add "com.atlassian.jira.workflow.OSWorkflowManager"

I have couple of questions.. How can we remove the first one (log4j.logger.atlassian.jira.workflow.OSWorkflowManager) from the list?

Is this temperory change or permanant change?

Boris Georgiev _Appfire_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 14, 2014

It's temporary and will be gone after the next restart and also it will not cause any problems.

To make it permanent edit the log4j.properties file

0 votes
Boris Georgiev _Appfire_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 14, 2014

Yes,

From the Logging anf Profiling page click Configure and for Package name put com.atlassian.jira.workflow.OSWorkflowManager
for
Logging Level put OFF

Here's how to get to the page:

  1. Log in as a user with the 'JIRA System Administrators'global permission.
  2. Choose >System. Select Troubleshooting and Support > Logging & Profilingto open the Logging page, which lists all defined log4j categories (as package names) and their current logging levels.
    (tick)Keyboard shortcut: 'g' + 'g' +start typing'logging & profiling'
  3. To change logging level of a category, click linked logging level associated with the relevant package name. To turn off logging of a category, click the 'OFF' link associated with the relevant package name.

Suggest an answer

Log in or Sign up to answer