Scriptrunner(validator) stacktrace on workflow transition. Normal?

[Brent Webster]

In Jira 5.2.2, I'm using Scriptrunner 2.1.3 to create various workflow transition validators. Works great. When the conditions evaluates true no issues but if the condition evaluates to false then from a workflow it works fine but if I check the catalina.out log file, large stack traces are generated. It generates an InvalidInputException

Here's an example of the condition code:

cfValues['Planned For'] == null || cfValues['Planned For']*.getName() == ["main"]

If the Planned For is set to another version, the expected error message is generated in the Jira pop up window but the following stack trace is generated. Can I disable or minimize the size of this outputi.e.

2013-05-27 19:32:25,851 http-bio-8080-exec-291 ERROR ebreweb 1172x200671x1 o443jb 142.133.244.72,127.0.0.1 /secure/CommentAssignIssue.jspa [atlassian.jira.workflow.OSWorkflowManager] Caught exception while attempting to perform action 261 from workflow 21754 on issue 'TBN-34'
[InvalidInputException: [Error map: [{assignee=An Issue can only be assigned to yourself else management will assign it.}]] [Error list: [[]]]
at sun.reflect.GeneratedConstructorAccessor1662.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77)
at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:71)
at org.codehaus.groovy.runtime.callsite.ConstructorSite.callConstructor(ConstructorSite.java:42)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:194)
at com.onresolve.jira.groovy.canned.workflow.validators.SimpleScriptedValidator.doScript(SimpleScriptedValidator.groovy:63)
at com.onresolve.jira.groovy.canned.CannedScript$doScript.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at com.onresolve.jira.groovy.canned.CannedScript$doScript.call(Unknown Source)

..... more text deleted

[JamieA · Accepted solution]

This is a jira issue... in fact this q has already been asked: https://answers.atlassian.com/questions/40838/how-to-avoid-invalidinputexception-stacktrace-in-log-using-custom-validators