[
https://issues.apache.org/jira/browse/OOZIE-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mona Chitnis updated OOZIE-1932:
--------------------------------
Attachment: OOZIE-1932-4-amendment.patch
{code}
2014-09-22 22:02:34,148 INFO ShareLibService:539 [main] - USER[-] GROUP[-]
oozie-hadoop-utils-2.3.0.oozie-4.4.1.1.jar uploaded to
hdfs:/tmp/hdfs_shared_lib_path/launcher_20140922220233/oozie
2014-09-22 22:02:34,198 INFO ShareLibService:539 [main] - USER[-] GROUP[-]
oozie-sharelib-hcatalog-4.4.1.1.jar uploaded to
hdfs:/tmp/hdfs_shared_lib_path/launcher_20140922220233/oozie
2014-09-22 22:02:34,199 ERROR ShareLibService:536 [main] - USER[-] GROUP[-]
Sharelib initialization fails
java.lang.NullPointerException
at
org.apache.oozie.service.ShareLibService.setupLauncherLibPath(ShareLibService.java:178)
at
org.apache.oozie.service.ShareLibService.updateLauncherLib(ShareLibService.java:158)
at
org.apache.oozie.service.ShareLibService.init(ShareLibService.java:111)
at
org.apache.oozie.service.Services.setServiceInternal(Services.java:368)
ShareLibService is dependent on ActionService.
private void setupLauncherLibPath(FileSystem fs, Path tmpLauncherLibPath)
throws IOException {
ActionService actionService = Services.get().get(ActionService.class);
List<Class> classes = JavaActionExecutor.getCommonLauncherClasses();
Path baseDir = new Path(tmpLauncherLibPath,
JavaActionExecutor.OOZIE_COMMON_LIBDIR);
copyJarContainingClasses(classes, fs, baseDir,
JavaActionExecutor.OOZIE_COMMON_LIBDIR);
Set<String> actionTypes = actionService.getActionTypes();
{code}
Attaching amendment patch
> Services should load CallableQueueService after MemoryLocksService
> ------------------------------------------------------------------
>
> Key: OOZIE-1932
> URL: https://issues.apache.org/jira/browse/OOZIE-1932
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: 4.1.0
>
> Attachments: OOZIE-1932-2.patch, OOZIE-1932-3.patch,
> OOZIE-1932-4-amendment.patch, OOZIE-1932-4.patch, OOZIE-1932-addendum.patch,
> OOZIE-1932.patch
>
>
> This is not a problem during startup but is during shutdown, as services are
> destroyed in reverse order of initialization. Hence, when MemoryLocksService
> destroy sets it to null, and commands are still executing due to
> CallableQueueService still active, they all encounter NPEs during locking.
> This is a simple fix in oozie-default.xml to set MemoryLocksService before in
> the order of services loading.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
