2 Replies Latest reply on Apr 1, 2011 1:47 AM by jc_installer

    Sub processes not found on deployed application

    jc_installer

      Hi,

       

      While modifying an application with a process that calls some subprocesses, we've noticed that sometimes its instances get stalled before calling a sub process. The log shows a warning and an error:

       

      • WARN  [com.adobe.workflow.AWS] ALC-DSC-012-000: com.adobe.idp.dsc.registry.ServiceNotFoundException: Service: /category name/1.0/subprocesses/process name.process not found. at com.adobe.idp.dsc.registry.service.impl.ServiceRegistryImpl.getService(ServiceRegistryImp l.java:1088)
      • ERROR [com.adobe.workflow.AWS] stalling action-instance: 15006 with message: ALC-DSC-012-000: com.adobe.idp.dsc.registry.ServiceNotFoundException: Service: /category name/1.0/subprocesses/process name.process not found. at com.adobe.idp.dsc.registry.service.impl.ServiceRegistryImpl.getService(ServiceRegistryImp l.java:1088)

       

      We had seen this issue before, but redeploying the application was enough to solve the problem.

       

      We've checked that all the assets of the application are listed in "Applications and Services - Application Management" in the adminui. On the workbench, when clicking on the activity calls show the expected subprocess, and if you right-click and select open subprocess, it is opened in the process designer. Removing and adding a new Suprocess activity that points to "process name" doesn't solve the error, but it seems that adding a new activity that calls the process as "category name/subprocesses/process name" works.

       

      Does someone know the reason why the server isn't finding the processes? I thought it would be better keeping related processes in the same application, and it would make the administration easier. Is it a bad practice to change the calls to "category name/subprocesses/process name" instead of "process name"? Our configuration is: LiveCycle ES2 and JBOSS.

       

      Thank you