I need to fix this in the current production env and it wouldnt be
possible to do an upgrade in prod for this,
is there a work around to get over this issue
thanks
jabir
On 8/9/12 10:56 PM, Mona Chitnis wrote:
This seems to be a version of Oozie older than 3.2 when the part about
'Xcommands' vs 'Commands' was still around. Jabir, is it possible for you
to retry with the latest released version - 3.2.0-incubating?
Thanks,
--
Mona Chitnis
On 8/9/12 10:14 AM, "jabir ahmed" <[email protected]> wrote:
this is where its failing
@Override
public void init(Services services) {
Configuration conf = services.getConf();
Runnable purgeJobsRunnable = new PurgeRunnable(conf.getInt(
CONF_OLDER_THAN, 30), conf.getInt(COORD_CONF_OLDER_THAN, 7),
conf.getInt(BUNDLE_CONF_OLDER_THAN, 7),
conf.getInt(PURGE_LIMIT, 100));
services.get(SchedulerService.class).schedule(purgeJobsRunnable, 10,
conf.getInt(CONF_PURGE_INTERVAL, 3600),
SchedulerService.Unit.SEC);
if (Services.get().getConf().getBoolean(USE_XCOMMAND, true) == false) {
useXCommand = false;
} Thanks Jabir
On 8/9/12 10:33 PM, jabir ahmed wrote:
i enabled the purge service in oozie and i see this error in the logs
2012-08-09 16:59:57,625 FATAL Services:533 - USER[-] GROUP[-] null
java.lang.NullPointerException
at org.apache.oozie.service.PurgeService.init(PurgeService.java:92)
at
org.apache.oozie.service.Services.setServiceInternal(Services.java:310)
at org.apache.oozie.service.Services.setService(Services.java:296)
at org.apache.oozie.service.Services.init(Services.java:206)
at
org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader
.java:40)
which points to this piece of the code
091
092 if (Services.get().getConf().getBoolean(USE_XCOMMAND,
true) == false) {
093 useXCommand = false;
094 }
any idea how to get over this issue
Thanks
Jabir
