[ https://issues.apache.org/jira/browse/OOZIE-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972559#comment-15972559 ]
Attila Sasvari commented on OOZIE-2795: --------------------------------------- Ran into this again: I attempted to install sharelib before starting the Oozie server. {noformat} Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/cli/ParseException at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.privateGetMethodRecursive(Class.java:3048) at java.lang.Class.getMethod0(Class.java:3018) at java.lang.Class.getMethod(Class.java:1784) at sun.launcher.LauncherHelper.validateMainClass(LauncherHelper.java:544) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:526) Caused by: java.lang.ClassNotFoundException: org.apache.commons.cli.ParseException at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 7 more {noformat} > Create lib directory or symlink for Oozie CLI during packaging > -------------------------------------------------------------- > > Key: OOZIE-2795 > URL: https://issues.apache.org/jira/browse/OOZIE-2795 > Project: Oozie > Issue Type: Bug > Reporter: Attila Sasvari > Assignee: Peter Cseh > Attachments: OOZIE-2795-001.patch, OOZIE-2795-002.patch, > OOZIE-2795-003.patch > > > After creating an Oozie distro, lib directory is not present in the distro > directory (e.g. oozie-4.4.0-SNAPSHOT) in the generated tar.gz . > > As a consequence, first run of theOozie CLI will fail if one tries to execute > it prior to server start: > {noformat} > $ bin/oozie > unzip: cannot find or open > /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war, > > /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.zip > or > /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.ZIP. > mv: rename > /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib/*.jar > to > /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/*.jar: > No such file or directory > rmdir: > /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib: > No such file or directory > rmdir: > /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF: > No such file or directory > Error: Could not find or load main class org.apache.oozie.cli.OozieCLI > {noformat} > If you start the server first however, a symlink is created (see > {{bin/oozie-jetty-server.sh}}), and this error will not be visible. > Earlier {{bin/oozie}} created this library by extracting it from the WAR file > used for Tomcat. Comment in the script: > {noformat} > #Create lib directory from war if lib doesn't exist > {noformat} > We could create a symlink to embedded-oozie-server/webapp/WEB-INF/lib/ or > copy that directory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)