Hi Mona,Thanks for your response. Yes, I did use "<propagate-configuration />"
for each of the sub-workflow. Something like this:
<action name="export-data"> <sub-workflow>
<app-path>${oozieWfAppPath}/data/workflow-export-data.xml</app-path>
<propagate-configuration /> <configuration>
<property>
<name>etlBatchNumber</name>
<value>${wf:actionData('etl')['batch.number']}</value>
</property> </configuration> </sub-workflow>
<ok to="join-export-decision" /> <error
to="killAction-etl" /> </action>
I have something like that for 3 different types and I'm calling them from a
fork.
> From: [email protected]
> To: [email protected]
> Subject: Re: Action it is not running its in [PREP] state
> Date: Wed, 17 Sep 2014 23:04:43 +0000
>
> Hi,
> Did you use the <propagate-configuration/> tag to make sure configuration
> given at workflow level (if any) is propagated to the sub-workflow?
>
>
>
> On 9/17/14, 3:46 PM, "Tanzir Musabbir" <[email protected]> wrote:
>
> >Hello everyone,
> >I am having an issue when using Oozie Subworkflow with fork. If I don't
> >use sub-workflow and execute the action (which is in sub-workflow) it
> >works, but it doesn't work with sub-workflow.
> >I have a parent workflow which has a fork and each of them has a
> >sub-workflow (3 in total). So in run-time, 3 workflow executes in
> >parallel. I tried with running a single sub-workflow, but I still faced
> >the same problem.
> >I'm getting the following errors:
> >org.apache.oozie.command.CommandException: E0800: Action it is not
> >running its in [PREP] state, action
> >[0000087-140827124522380-oozie-oozi-W@export-data] at
> >org.apache.oozie.command.wf.CompletedActionXCommand.eagerVerifyPreconditio
> >n(CompletedActionXCommand.java:85) at
> >org.apache.oozie.command.XCommand.call(XCommand.java:248) at
> >org.apache.oozie.service.CallableQueueService$CallableWrapper.run(Callable
> >QueueService.java:175) at
> >java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
> >1145) at
> >java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
> >:615) at java.lang.Thread.run(Thread.java:724)
> >Can anyone please tell me what's the primary reason for getting this kind
> >of error? Or any workaround?
> >Any information will be highly appreciated.
> >
> >Thanks in advance.Tanzir
>
