Unable to trigger the workflow created using XCP Designer

Hi All, We recently upgraded our Process engine from 2.1 to 2.3. So far we use Process builder to create workflow process. Now we have started using XCP designer to create workflows and deployed successfully. However when we start the process through DA, we are receiving the following error " org.apache.commons.io.IOUtils.closeQuietly(Ljava/io/Closeable;)Vjava.lang.NoSuchMethodError: org.apache.commons.io.IOUtils.closeQuietly (Ljava/io/Closeable;)V at com.emc.xcp.artifactmanager.internal.runtime.DarArtifactContainer.isArtifactExists(DarArtifactContainer.java:257) at com.emc.xcp.artifactmanager.internal.ArtifactIndexer.initIndexes(ArtifactIndexer.java:29) at com.emc.xcp.artifactmanager.internal.ArtifactIndexer.(ArtifactIndexer.java:25) at com.emc.xcp.artifactmanager.internal.ArtifactManager.init(ArtifactManager.java:98) at com.emc.xcp.artifactmanager.internal.ArtifactManager.(ArtifactManager.java:83) at com.emc.xcp.artifactmanager.runtime.ArtifactManagerService.createArtifactLocator(ArtifactManagerService.java:159) at com.emc.xcp.artifactmanager.runtime.ArtifactManagerService.createArtifactLocator(ArtifactManagerService.java:141) at com.emc.xcp.artifactmanager.runtime.ArtifactManagerService.createArtifactLocator(ArtifactManagerService.java:108) at com.emc.xcp.runtime.artifact.locator.Utils.getArtifactLocator(Utils.java:156) at com.emc.xcp.runtime.artifact.locator.Utils.getArtifactBundle(Utils.java:39) at com.emc.xcp.runtime.artifact.locator.ArtifactLocatorCache.getApplicationArtifactBundle(ArtifactLocatorCache.java:49) at com.emc.xcp.runtime.artifact.locator.RuntimeArtifactLocator.getApplicationArtifactBundle(RuntimeArtifactLocator.java:25) at com.emc.xcp.runtime.engine.workflowRuntime.ActivityCache.loadProcessAndActivitiesModel(ActivityCache.java:137) at com.emc.xcp.runtime.engine.workflowRuntime.ActivityCache.loadProcessModelFromRepository(ActivityCache.java:100) at com.emc.xcp.runtime.engine.workflowRuntime.ActivityCache.getProcessModel(ActivityCache.java:64) at com.emc.xcp.runtime.engine.workflowRuntime.AbstractRuntimeWorkflowHandler.init(AbstractRuntimeWorkflowHandler.java:30) at com.emc.xcp.runtime.engine.workflowRuntime.RuntimeWorkflowStartHandler.(RuntimeWorkflowStartHandler.java:18) at com.documentum.bpm.impl.WorkflowHandlerFactory.getWorkflowStartHandler(WorkflowHandlerFactory.java:20) at com.documentum.bpm.impl.DfWorkflowEx.execute(DfWorkflowEx.java:269) at com.documentum.bpm.impl.DfWorkflowEx___PROXY.execute(DfWorkflowEx___PROXY.java) at com.documentum.services.workflow.startworkflow.StartWorkflowImpl.runWorkflow(Unknown Source) at com.documentum.services.workflow.startworkflow.StartWorkflow.startWorkflow(Unknown Source) at com.documentum.webcomponent.library.workflow.startworkflow.StartWorkflowState.runWorkflow(StartWorkflowState.java:777) at com.documentum.webcomponent.library.workflow.startwfcontainer.StartWorkflowContainer$StartWorkflowTask.execute(StartWorkflowContainer.java:336) at com.documentum.job.async.AsyncJobManager$AsyncTimerJob.executeJob(AsyncJobManager.java:236) at com.documentum.job.async.AsyncJobManager$AsyncTimerJob.run(AsyncJobManager.java:215) at java.util.TimerThread.mainLoop(Unknown Source) at java.util.TimerThread.run(Unknown Source)" Appreciate if anyone can help me fixing this.

Find more posts tagged with

Comments

ravsom

It could be that the Process Engine runtime does not have the right version of org.apache.commons.io

Along with upgrading the Process Engine jars, did you get a chance to upgrade the apache jars. The closeQuietly API has been there since org.apache.commons.io_2.0

stephenk

Upgrading the apache jar -- Does you mean upgrading the commons.io jar available under "C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\da\WEB-INF\lib". I see the current version of DA 7.1. Also current version of Commons.io is 1.2. How do I upgrade only Apache jars. Is there any documents available for upgrade?

tgp

Did you ever resolve this issue? Getting the same error ....

stephenk

Commons.io jar mismatch is the cause for the issue. In my case, we used DFS 7.3 to interact with Documentum. I noticed there is a difference in commons.io.jar version between App server (DFS/WebINF/Lib Folder) & Content server (BPM WEBNF/Lib folder). I took the latest version commons.io-2.4.jar from BPM WEBNF/Lib folder and replaced it under (DFS/WebINF/Lib Folder). Restarted Tomcat service and that fixed the issue. Your case might be different. All you need to do is to make sure Your Client application library has latest version of Commons.io jar.

tgp

I actually found that in the meantime as well based on the previous comments ... we're actually using a custom WDK app that is based on a pre7.x Webtop/WDK version. Once I replaced the commons.io.jar I was able to process WFs as well.

Do you think we would have any issues just replacing this new commons.io.jar in the WDK app? Would you expect it to cause other issues?

Thanks for your response ....

stephenk

I believe it should not create any issue until unless any of the methods used in previous version of commons.io.jar got deprecated in newer version and you are invoking such method in your code. We have those updated in our production and its been an year we did not face any issue . Better you can raise a ticket and get confirmation with OpenText.