Class does exit,
is it not oozie that places jar files in the task tracker or Im missing
something?


On Sat, Jun 23, 2012 at 12:21 PM, Chaitanya Sharma <[email protected]>wrote:

> Looks like second class, "aggregator.Driver" is not on the class path.
> It would help to confirm that.
>
>
> Chaitanya
>
>
> On Sat, Jun 23, 2012 at 12:48 PM, Akhtar Muhammad Din
> <[email protected]> wrote:
> > Hi,
> > I have defined 2 actions in the workflow, for each action there is a
> > separate jar under lib directory. First action completes successfully and
> > when second action starts i get class not found exception (class exists
> in
> > the second jar file ). Here is my workflow definition:
> >
> > <workflow-app name='TestWorkflow' xmlns="uri:oozie:workflow:0.2">
> >  <start to='action1'/>
> > <action name='action1'>
> > <java>
> > <job-tracker>${jobTracker}</job-tracker>
> > <name-node>${nameNode}</name-node>
> > <configuration>
> > <property>
> > <name>mapred.job.queue.name</name>
> > <value>${queueName}</value>
> > </property>
> > </configuration>
> > <main-class>mapper.ParserDriver</main-class>
> > </java>
> > <ok to='action2/>
> > <error to='fail'/>
> > </action>
> >
> > <action name='action2'>
> > <java>
> > <job-tracker>${jobTracker}</job-tracker>
> > <name-node>${nameNode}</name-node>
> > <configuration>
> > <property>
> > <name>mapred.job.queue.name</name>
> > <value>${queueName}</value>
> > </property>
> > </configuration>
> > <main-class>aggregator.Driver</main-class>
> > </java>
> > <ok to='end'/>
> > <error to='fail'/>
> > </action>
> >    <kill name='fail'>
> > <message>Java failed, error
> > message[${wf:errorMessage(wf:lastErrorNode())}]</message>
> > </kill>
> > <end name='end'/>
> > </workflow-app>
> >
> >
> > Would anybody please help me out, thanks in advance
>



-- 
Regards
Akhtar Muhammad Din

Reply via email to