Task Detail Form runtime error

Question

In SOA Suite 11.1.1.5, we have auto-generated an ADF task form. The form compiles and deploys successfully. In 2 environments, the form works as expected at runtime. In 1 environment, the form does not appear when the task is selected in the worklist. In the logs we find:
[APP: TestTaskForm] [URI: /workflow/TestTaskForm/faces/adf.task-flow] unable to dispatch JSP page: The following exception occurred:.[[
javax.el.ELException: java.lang.NoClassDefFoundError: org/codehaus/groovy/control/CompilerConfiguration
at javax.el.BeanELResolver.getValue(BeanELResolver.java:266)
at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:173)
at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:200)
at com.sun.el.parser.AstValue.getValue(Unknown Source)
at com.sun.el.ValueExpressionImpl.getValue(Unknown Source)
at org.apache.myfaces.trinidadinternal.taglib.ForEachTag.doStartTag(ForEachTag.java:117)
at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:43)
at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
The groovy-all-1.6.3.jar is in the classpath in all 3 environments.The classpaths are essentially identical between the environments. However, when we run the WLS-CAT (classpath analysis tool) and compare between the environments we see that, although the classpaths are the same,the working environments have many more groovy classes and some oracle classes that show up in the "Classes Loaded" list. For some reason, the groovy classes and some oracle classes are not get loading in the non-working environment. I should mention that the non-working environment is the only one of the 3 that is clustered. Also we have tried with more than one task form, none of them will work in the clustered environment.
Has anyone encountered similar or any ideas?

Answer 1

Oracle responded to the SR this afternoon. We added to the groovy-all jar file to the CLASSPATH in setDomainEnv.sh. This solved the problem! We are still not understanding why it works in the other environments without making this entry in the classpath.