topic Re: Could not initialize class org.codehaus.groovy.runtime.InvokerHelper in Alfresco Archive

Could not initialize class org.codehaus.groovy.runtime.InvokerHelper

aggiepilot04 — Mon, 18 Aug 2014 22:15:53 GMT

Back in May, upgraded to Activiti 5.15.1. We have a 60 day expiration timer on some of our workflow tasks, and we recently noticed that they started failing. Everything works fine with our workflows so long as a user is at the keyboard processing a task. However, when a task progresses as a resul

Re: Could not initialize class org.codehaus.groovy.runtime.InvokerHelper

martin_grofcik — Wed, 20 Aug 2014 04:43:58 GMT

Hi,


Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.codehaus.groovy.runtime.InvokerHelper

is InvokerHelper in your classpath?

Regards
Martin

Re: Could not initialize class org.codehaus.groovy.runtime.InvokerHelper

aggiepilot04 — Wed, 20 Aug 2014 15:17:25 GMT

Thanks for the response. I think I have it figured out. We only use activiti-explorer for deploying new process definitions…everything else we do via the REST API. Most of my investigation was directed at activiti-rest for this reason. It turns out that the activiti-explorer deployment is processing some of these timer jobs though, and that deployment had duplicate groovy-all's (and different versions) in the classpath. I can't easily recreate in a test environment, but this will go into production tonight. I'm fairly confident that it will resolve our problems.