Groovy custom operations in Butterfly SP15 are getting stuck in In-Progress state.
Worker logs “GroovyEngine:executeOperation| Now executing script” , however the script does not gets executed and and operation gets stuck. After worker restart -> if we trigger the same operation, it works fine. But the issue is persistent. There are no pending items in activeMQ, enough wildfly threads available. Could it be related to groovy pool size allocated or max connections made to DB. Is there any standard guidelines to follow specific to ignio while writing custom codes other than standard language guidelines. Not able to trace root cause.
This question can not be answer generically. This might be performance issue or improper design of the usecase. We have document for coding standard to be followed while writing groovy SOs or Operators. Please refer below link.
The issue was due to node not available in Blueprint. Groovy operation forwarded null node details to operator and it got hung in queue as workflow could not find networkid.
