Hi,

We manually close issues in Jira before they have reached the closed
state in V1 as there is a long delay between the time we have retested
these issues and the time they are eventually closed by release
engineering in V1.

This however results in an enormous amount of logging being written to
the ServiceHost log file... (see example below which occurs for every
issue)

What is the best way to control the amount of logging from the
ServiceHost.exe application? Ideally I'd like to reduce it to the
minimum output or perhaps switch off logging altogether, turning it on
only when a problem needs to be investigated...

Another way to control logging might be to rotate the log file on a nightly basis allowing the opportunity to remove old no longer required log files without the need to restart the service.

Kind Regards,
Colin.

[Error] 10/25/2009 5:56:22 PM Error updating MPOS-29
'customfield_10000' to 'V1_Closed':
System.Web.Services.Protocols.SoapException:
com.atlassian.jira.rpc.exception.RemoteValidationException: Fields not
vali
d for issue:
Errors: {}
Error Messages: [You do not have permission to edit issues in this
project.]
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse
(SoapClientMessage message, WebResponse response,
Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
(String methodName, Object[] parameters)
at VersionOne.Jira.SoapProxy.Jira.JiraSoapService.updateIssue
(String in0, String in1, RemoteFieldValue[] in2)
at VersionOne.Jira.SoapProxy.JiraSoapProxy.UpdateIssue(String
loginToken, String issueKey, String fieldName, String f
ieldValue)
at VersionOne.Jira.JiraIssueReaderUpdater.OnDefectStateChange
(DefectStateChangeResult stateChangeResult)

by: Colin O. | over a year ago | Integration