[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (77 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2713  Provide an option to log out contents of the localized jar files
https://issues.apache.org/jira/browse/OOZIE-2713
OOZIE-2709  Log the substituted pig script by expanding macros
https://issues.apache.org/jira/browse/OOZIE-2709
OOZIE-2694  Add logging for FsActionExecutor 
https://issues.apache.org/jira/browse/OOZIE-2694
OOZIE-2693  SimpleHCatDependencyCache.removeMissingDependency can throw NPE
https://issues.apache.org/jira/browse/OOZIE-2693
OOZIE-2692  Oozie job submit doesn't report error message to user if there is 
any issue with job conf
https://issues.apache.org/jira/browse/OOZIE-2692
OOZIE-2691  Show workflow action retry count to UI
https://issues.apache.org/jira/browse/OOZIE-2691
OOZIE-2690  OOZIE NPE while executing kill()
https://issues.apache.org/jira/browse/OOZIE-2690
OOZIE-2684  Bad database schema error for WF_ACTIONS table
https://issues.apache.org/jira/browse/OOZIE-2684
OOZIE-2670  Upgrade Hbase to 1.2
https://issues.apache.org/jira/browse/OOZIE-2670
OOZIE-2668  Status update and recovery problems when coord action and its 
children not in sync
https://issues.apache.org/jira/browse/OOZIE-2668
OOZIE-2666  Support embedding Jetty into Oozie
https://issues.apache.org/jira/browse/OOZIE-2666
OOZIE-2662  DB migration fails if DB is too big
https://issues.apache.org/jira/browse/OOZIE-2662
OOZIE-2654  Zookeeper dependent services should not depend on Connectionstate 
to be valid before cleaning up
https://issues.apache.org/jira/browse/OOZIE-2654
OOZIE-2652  Skip trash while deleting hive table partition
https://issues.apache.org/jira/browse/OOZIE-2652
OOZIE-2650  Retry coord start on database exceptions
https://issues.apache.org/jira/browse/OOZIE-2650
OOZIE-2644  Skip queuing Notification Commands when there's nothing to notify
https://issues.apache.org/jira/browse/OOZIE-2644
OOZIE-2641  rerunning an oozie coordinator job stucks on waiting
https://issues.apache.org/jira/browse/OOZIE-2641
OOZIE-2630  Oozie Coordinator EL Functions to get first day of the week/month
https://issues.apache.org/jira/browse/OOZIE-2630
OOZIE-2619  Make  Hive action defaults to match hive defaults when running from 
command line
https://issues.apache.org/jira/browse/OOZIE-2619
OOZIE-2618  Include hive-common in hive-beeline as compile component for 
hive-server2 (hive2 action)
https://issues.apache.org/jira/browse/OOZIE-2618
OOZIE-2616  Add Tez profile for Hive and Pig sharelibs
https://issues.apache.org/jira/browse/OOZIE-2616
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues.apache.org/jira/browse/OOZIE-2585
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues.apache.org/jira/browse/OOZIE-2573
OOZIE-2568  SSH  action pretends to retry automaticly when it failed
https://issues.apache.org/jira/browse/OOZIE-2568
OOZIE-2564  Create new log4j config for unit tests so that logged messages 
contain threads
https://issues.apache.org/jira/browse/OOZIE-2564
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues.apache.org/jira/browse/OOZIE-2534
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues.apache.org/jira/browse/OOZIE-2528
OOZIE-2518  Oozie is creating many files and directories in /tmp per day
https://issues.apache.org/jira/browse/OOZIE-2518
OOZIE-2513  log.scan.duration should not be used for error and audit logs
https://issues.apache.org/jira/browse/OOZIE-2513
OOZIE-2499  map-reduce launcher does not need distributed files, archives 
except  jar of input/outputformat class
https://issues.apache.org/jira/browse/OOZIE-2499
OOZIE-2495  change action status from  ErrorType.NON_TRANSIENT to TRANSIENT 
when SSH action occurs AUTH_FAILED occasionally
https://issues.apache.org/jira/browse/OOZIE-2495
OOZIE-2473  Connection pool for SMTP connection
https://issues.apache.org/jira/browse/OOZIE-2473
OOZIE-2461  Workflow, Coordinator and Bundle job querying should have last 
modified filter
https://issues.apache.org/jira/browse/OOZIE-2461
OOZIE-2457  Oozie log parsing regex consume more than 90% cpu
https://issues.apache.org/jira/browse/OOZIE-2457
OOZIE-2427  With Kerberos enabled, the authentication failure for the 
javascript resources under /ext-2.2 
https://issues.apache.org/jira/browse/OOZIE-2427
OOZIE-2396  oozie compile with hadoop 2.7.1 failed
https://issues.apache.org/jira/browse/OOZIE-2396

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (86 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2619  Make  Hive action defaults to match hive defaults when running from 
command line
https://issues-test.apache.org/jira/browse/OOZIE-2619
OOZIE-2618  Include hive-common in hive-beeline as compile component for 
hive-server2 (hive2 action)
https://issues-test.apache.org/jira/browse/OOZIE-2618
OOZIE-2617  Read properties files in action configurations
https://issues-test.apache.org/jira/browse/OOZIE-2617
OOZIE-2616  Add Tez profile for Hive and Pig sharelibs
https://issues-test.apache.org/jira/browse/OOZIE-2616
OOZIE-2606  Set spark.yarn.jars to fix Spark 2.0 with Oozie
https://issues-test.apache.org/jira/browse/OOZIE-2606
OOZIE-2589  CompletedActionXCommand priority param is of no effect
https://issues-test.apache.org/jira/browse/OOZIE-2589
OOZIE-2588  Support getting credentials for same cluster hcat when credentials 
config is empty
https://issues-test.apache.org/jira/browse/OOZIE-2588
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues-test.apache.org/jira/browse/OOZIE-2585
OOZIE-2584  Eliminate Thread.sleep() calls in TestMemoryLocks
https://issues-test.apache.org/jira/browse/OOZIE-2584
OOZIE-2583  oozie throws EL Exception when reference variable name containing 
dot
https://issues-test.apache.org/jira/browse/OOZIE-2583
OOZIE-2582  Populating external child Ids for action failures
https://issues-test.apache.org/jira/browse/OOZIE-2582
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues-test.apache.org/jira/browse/OOZIE-2573
OOZIE-2572  SLA DURATION miss not shown when job is running for longer than 
expected time
https://issues-test.apache.org/jira/browse/OOZIE-2572
OOZIE-2571  Add scala.binary.version Maven property so that Scala 2.11 can be 
used
https://issues-test.apache.org/jira/browse/OOZIE-2571
OOZIE-2569  Adding yarn-site, core-site, hdfs-site and mapred-site into spark 
launcher 
https://issues-test.apache.org/jira/browse/OOZIE-2569
OOZIE-2568  SSH  action pretends to retry automaticly when it failed
https://issues-test.apache.org/jira/browse/OOZIE-2568
OOZIE-2564  Create new log4j config for unit tests so that logged messages 
contain threads
https://issues-test.apache.org/jira/browse/OOZIE-2564
OOZIE-2552  Update ActiveMQ version for security and other fixes
https://issues-test.apache.org/jira/browse/OOZIE-2552
OOZIE-2538  Update HttpClient versions to close security vulnerabilities
https://issues-test.apache.org/jira/browse/OOZIE-2538
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues-test.apache.org/jira/browse/OOZIE-2534
OOZIE-2530  Remove jline from parent and sharelib pig pom
https://issues-test.apache.org/jira/browse/OOZIE-2530
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues-test.apache.org/jira/browse/OOZIE-2528
OOZIE-2521  Filter options are case sensitive for jobtye=bundle
https://issues-test.apache.org/jira/browse/OOZIE-2521
OOZIE-2518  Oozie is creating many files and directories in /tmp per day
https://issues-test.apache.org/jira/browse/OOZIE-2518
OOZIE-2517  Add support for startCreatedTime and endCreatedTime filters for 
coord and bundles
https://issues-test.apache.org/jira/browse/OOZIE-2517
OOZIE-2513  log.scan.duration should not be used for error and audit logs
https://issues-test.apache.org/jira/browse/OOZIE-2513
OOZIE-2512  ShareLibservice returns incorrect path for jar
https://issues-test.apache.org/jira/browse/OOZIE-2512
OOZIE-2508  Documentation change for Coord action rerun [OOZIE-1735]
https://issues-test.apache.org/jira/browse/OOZIE-2508
OOZIE-2501  ZK reentrant lock doesn't work for few cases
https://issues-test.apache.org/jira/browse/OOZIE-2501
OOZIE-2500  -DtestJarSimple option mentioned in minioozie doc does not work
https://issues-test.apache.org/jira/browse/OOZIE-2500
OOZIE-2499  map-reduce launcher does not need distributed files, archives 
except  jar of input/outputformat class
https://issues-test.apache.org/jira/browse/OOZIE-2499
OOZIE-2498  Oozie CallerId configuration for downstream components 
https://issues-test.apache.org/jira/browse/OOZIE-2498
OOZIE-2495  change action status from  ErrorType.NON_TRANSIENT to TRANSIENT 
when SSH action occurs AUTH_FAILED occasionally
https://issues-test.apache.org/jira/browse/OOZIE-2495
OOZIE-2491  oozie acl cannot specify group,it does`t work
https://issues-test.apache.org/jira/browse/OOZIE-2491
OOZIE

[jira] [Commented] (OOZIE-1986) Add FindBugs report to pre-commit build

[Robert Kanter (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606926#comment-15606926
 ] 

Robert Kanter commented on OOZIE-1986:
--

[~andras.piros], thanks for working on the amend patch.  Two things:
# Can you look into the RAT warning?  You may need to add another file to the 
exclusions.
# This line seems odd to me, though I'm not a bash expert so it could be 
correct:
{code}
done <   <(find "${sourceFolder}" -name ${FINDBUGS_XML_NAME} -print0)
{code}
In particular, the {{done <   <(}} part.  What does two {{<}} separated like 
that do?
#- This makes me think of Kirby {{<('o'<)}} :)

> Add FindBugs report to pre-commit build
> ---
>
> Key: OOZIE-1986
> URL: https://issues.apache.org/jira/browse/OOZIE-1986
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: Robert Kanter
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-1986-amend.001.patch, OOZIE-1986.001.patch, 
> OOZIE-1986.002.patch, OOZIE-1986.003.patch, OOZIE-1986.004.patch, 
> OOZIE-1986.005.patch, OOZIE-1986.006.patch, OOZIE-1986.007.patch, 
> OOZIE-1986.008.patch, OOZIE-1986.009.patch, OOZIE-1986.010.patch, summary.txt
>
>
> Now that we have OOZIE-1793, it will be really useful to have the pre-commit 
> build generate a findbugs report.  It should probably before and after the 
> patch and only complain it there are more after.  And it should link to the 
> report.  Ideally, this would do some kind of diff (like Hadoop does) so it's 
> easy to identify the new findbugs items.
> You can generate the findbugs reports by running:
> {noformat}
> mvn verify -DskipTests
> {noformat}
> This also runs checkstyle



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2317) Figure out what to do about Tomcat 6 End of Life

[Robert Kanter (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606713#comment-15606713
 ] 

Robert Kanter commented on OOZIE-2317:
--

+1 on [~asasvari]'s suggestion.

>From a user's perspective, switching from what we do today with Tomcat to 
>using embedded Jetty won't change much because of how Oozie was managing 
>Tomcat.  The user would still use the same startup script to run Oozie.  The 
>only things that would change would be that the SSL and other web server 
>config properties would all be defined in oozie-site.xml instead of many of 
>them being CLI changes.  In fact, it would be simpler because you wouldn't 
>need to deal with any war repackaging scripts, or special scripts for turning 
>on SSL.

Also, the current way Oozie uses Tomcat isn't correct.  We download the Tomcat 
tarball and Oozie manages it.  The correct way to do this would be to use 
Tomcat jars from maven and set it up more like what we're doing with embedded 
Jetty.  But given that we're going to use embedded Jetty, I don't see much 
reason to bother also supported embedded Tomcat.  Trying to maintain support 
for both embedded Jetty and embedded Tomcat is probably not something we want 
to do.

We can still support building a WAR file for users who want to deploy Oozie in 
their own (not embedded) Tomcat or Jetty.  So if someone wants to use Tomcat, 
they can deploy a Tomcat server and use the WAR file.

With that in mind, I think we only need one maven profile:
- *(default):* Oozie standalone mode powered by embedded Jetty
- *war:* Oozie builds a WAR file like today, but without downloading Tomcat

[~asasvari] probably has more insight into the easiest way to do this given 
he's been working on this a lot more, but off the top of my head, the simplest 
way to do this is to probably make the oozie-distro module do the embedded 
Jetty stuff, and then have a new WAR packaging module that is off by default.

> Figure out what to do about Tomcat 6 End of Life
> 
>
> Key: OOZIE-2317
> URL: https://issues.apache.org/jira/browse/OOZIE-2317
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>
> [Tomcat 6 will be end of life on Dec 31 
> 2016.|https://tomcat.apache.org/tomcat-60-eol.html]
> Even though that's a quite a while from now, it's best to stay ahead of 
> things, so it would be good if we looked into a plan for this.  
> Here are some options:
> # Upgrade to Tomcat 7
> # Upgrade to Tomcat 8
> # Switch to embedded Jetty 9
> I imagine upgrading to Tomcat 7/8 would be the easiest solution.  I haven't 
> looked into it much, but I imagine the build and deploy process could remain 
> relatively the same; though we'd probably have to tweak some config files and 
> things.  As for which version, Tomcat has [this 
> page|https://tomcat.apache.org/whichversion.html] to help.
> Switching to embedded Jetty 9 would require changing the build and deploy 
> process, though that might be a good thing given how that can be 
> complicated/confusing for users.  And I know Tomcat makes things difficult 
> for our packaging team in Cloudera.  Many other Hadoop projects use embedded 
> Jetty as well.  We do know that Oozie runs properly in Jetty because our unit 
> tests use Jetty.
> As part of this JIRA, the assignee should probably look into more specific 
> pros/cons of the options and we should all reach a consensus before moving 
> forward.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2714) Detect conflicting resources during class loading

[Peter Bacsko (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606696#comment-15606696
 ] 

Peter Bacsko commented on OOZIE-2714:
-

Hi Robert

1. Yes, it definitely introduces some overhead because we have to open every 
jar and check them. Having this feature off by default is probably a good 
thing, but we might encourage users to try this out at least once to make sure 
their classpath is clean.

2. I can imagine that two different classes are compatible on API level and 
only the class versions are different. Another scenario is that their public 
API is almost the same but one method differs from another. I would simply say 
that if two classes are different in their binary representation it should mean 
that they're candidates for potential conflict and we signal an error, even if 
a particular method call could complete without errors.

3. Custom classloader - I think it depends on how the custom loader works. If 
it loads a distinct set jars in an isolated fashion (which is normally the 
case) and only ask ours (the parent) to load the rest then it's probably fine - 
but yeah, we have to think about this.

In general, as long as it can be switched off completely, I think we are good.

There is a tricky thing that I found out recently: a lot of libs are added from 
multiple folders from different hadoop projects (like hadoop-yarn, hadoop-hdfs, 
hadoop-whatever). But those are jars are the same (hopefully :)). This probably 
necessitates the compare-based approach (unless we exclude certain 
paths/path-pairs from being checked).

> Detect conflicting resources during class loading
> -
>
> Key: OOZIE-2714
> URL: https://issues.apache.org/jira/browse/OOZIE-2714
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Reporter: Peter Bacsko
>
> There are a bunch of issues in Oozie which are related to class loading. 
> The main problem is that the classpath is constructed in a way which is very 
> specific to Oozie:
> - Hadoop lib jars
> - Sharelib jars
> - User-defined jars
> Sometimes there is a conflict between sharelib and hadoop lib version. Also, 
> users can add their own jars which sometimes contain a different version of 
> popular libraries such as Guava, Apache commons, etc.
> We should be able to detect these conflicts and print exact error message so 
> that Oozie users can take appropriate actions to resolve the problem.
> A possible approach is the following:
> * start the execution of an action on a different thread
> * replace the thread's context classloader with a classloader which can 
> detect conflicts
> * when the JVM invokes the {{loadClass()}} method of the classloader, it  
> scans through the jars (which are available as {{URLClassPath}} objects). If 
> it finds the given resource in at least two jars, it can do different things 
> depending on the setup:
> ** throws an error immediately, mentioning the conflicting jars (this is 
> probably too strict - but still an option)
> ** loads the two resource into a byte array and compares them - it only 
> throws an error if there is difference
> ** compares the jars but only emits an error message if there is a conflict
> ** something else (user defined action?)
> Implementing such a classloader is not difficult and would greatly enhance 
> the supportability of Oozie. It could work in multiple modes depending on the 
> setup - perhaps being able to control it from a workflow config is desirable. 
> If there's any problem, we should be able to turn it off completely, too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-2317) Figure out what to do about Tomcat 6 End of Life

[Attila Sasvari (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606390#comment-15606390
 ] 

Attila Sasvari commented on OOZIE-2317:
---

[~rkanter], [~jaydeepvishwakarma], [~rohini]: I am wondering if it is worth to 
update to latest version by the end of 2016. Oozie is working with embedded 
Jetty and would require less configuration (most of the things can be 
configured via oozie-site.xml / oozie-default.xml, using only a few environment 
variables). Plus, we already use Jetty in Oozie tests. 

Long story short, what I propose is to drop embedded Tomcat in favor of 
embedded Jetty. It would make packaging (and starting scripts) cleaner and 
simpler and we could remove the tomcat profile completely that OOZIE-2666 would 
introduce.  In my opinion supporting both embedded Oozie and Tomcat would make 
things unnecessarily complicated.

If someone still wants to employ Tomcat or other servlet / web containers, they 
still can - for example by deploying the war containing the proper web.xml 
(i.e. web.xml or ssl-web.xml if HTTPS is a requirement).

> Figure out what to do about Tomcat 6 End of Life
> 
>
> Key: OOZIE-2317
> URL: https://issues.apache.org/jira/browse/OOZIE-2317
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>
> [Tomcat 6 will be end of life on Dec 31 
> 2016.|https://tomcat.apache.org/tomcat-60-eol.html]
> Even though that's a quite a while from now, it's best to stay ahead of 
> things, so it would be good if we looked into a plan for this.  
> Here are some options:
> # Upgrade to Tomcat 7
> # Upgrade to Tomcat 8
> # Switch to embedded Jetty 9
> I imagine upgrading to Tomcat 7/8 would be the easiest solution.  I haven't 
> looked into it much, but I imagine the build and deploy process could remain 
> relatively the same; though we'd probably have to tweak some config files and 
> things.  As for which version, Tomcat has [this 
> page|https://tomcat.apache.org/whichversion.html] to help.
> Switching to embedded Jetty 9 would require changing the build and deploy 
> process, though that might be a good thing given how that can be 
> complicated/confusing for users.  And I know Tomcat makes things difficult 
> for our packaging team in Cloudera.  Many other Hadoop projects use embedded 
> Jetty as well.  We do know that Oozie runs properly in Jetty because our unit 
> tests use Jetty.
> As part of this JIRA, the assignee should probably look into more specific 
> pros/cons of the options and we should all reach a consensus before moving 
> forward.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is back to normal : oozie-trunk-find-patches-available #137603

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-find-patches-available #137602

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1bf91be7b3f824ca4a9fb3e705764574f5dae4da 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1bf91be7b3f824ca4a9fb3e705764574f5dae4da
 > git rev-list 1bf91be7b3f824ca4a9fb3e705764574f5dae4da # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson9161511544860650572.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100  210k0  210k0 0   207k  0 --:--:--  0:00:01 --:--:--  207k
100  536k0  536k0 0   264k  0 --:--:--  0:00:02 --:--:--  264k
100  851k0  851k0 0   279k  0 --:--:--  0:00:03 --:--:--  279k
100 1237k0 1237k0 0   306k  0 --:--:--  0:00:04 --:--:--  306k
100 1632k0 1632k0 0   325k  0 --:--:--  0:00:05 --:--:--  325k
100 1808k0 1808k0 0   319k  0 --:--:--  0:00:05 --:--:--  344k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605939#comment-15605939
 ] 

Hadoop QA commented on OOZIE-2666:
--

Testing JIRA OOZIE-2666

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 9 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:red}-1 RAT{color}
.{color:red}-1{color} the patch seems to introduce 2 new RAT warning(s)
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:red}-1{color} FindBugs diff JAR has a weird MD5 sum, rejecting.
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1822
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3408/

> Support embedding Jetty into Oozie
> --
>
> Key: OOZIE-2666
> URL: https://issues.apache.org/jira/browse/OOZIE-2666
> Project: Oozie
>  Issue Type: Sub-task
>  Components: core
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2666.PATCH-01.patch, OOZIE-2666.PATCH-02.patch, 
> OOZIE-2666.PATCH-03.patch, OOZIE-2666.PATCH-05.patch, 
> OOZIE-2666.PATCH-06.patch, OOZIE-2666.PATCH-07.patch, 
> OOZIE-2666.PATCH-09.patch, OOZIE-2666.PATCH-10.patch, 
> OOZIE-2666.PATCH-11.patch, OOZIE-2666.PATCH-12.patch, 
> OOZIE-2666.PATCH-13.patch, OOZIE-2666.PATCH-14.patch, 
> OOZIE-2666.PATCH-15.patch, OOZIE-2666.PATCH-16.patch, 
> OOZIE-2666.PATCH-17.patch, OOZIE-2666.PATCH-18.patch, 
> OOZIE-2666.PATCH-19.patch, OOZIE-2666.PATCH-20.patch, 
> OOZIE-2666.PATCH-21.patch, OOZIE-2666.PATCH-22.patch
>
>
> The purpose of this task is to allow Oozie to run as a standalone application 
> rather than being deployed to a container inside a WAR file.
> - Build embedded jetty enabled Oozie by default
> - Allow building Tomcat based Oozie by specifying the 'tomcat' profile
> - Starting Oozie with oozied.sh detect webserver type based on the build info
> - Oozie Web UI is working with JDK 8 if using embedded jetty 
> - If using Jetty, allow the user to configure the following settings via 
> oozie-default / oozie-site xml:
> -- request / response header size
> -- allowed HTTPS protocols
> -- excluded / weak cipher suites
> -- threadpool size



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: oozie-trunk-precommit-build #3408

[Apache Jenkins Server]

See 

--
[...truncated 8194 lines...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionTimeOutXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordCommandUtils.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordPauseXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordRerunXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordPushDependencyCheckXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordStatusTransitXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordUpdateXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordSubmitXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/SLAEventsXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordSLAChangeXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordChangeXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordJobXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordSLAAlertsDisableXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordinatorXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionInputCheckXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordResumeXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordSLAAlertsXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordSLAAlertsEnableXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionCheckXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionsKillXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordUnpauseXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordSuspendXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionReadyXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionStartXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordActionUpdateXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/command/coord/CoordKillXCommand.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/or

Re: Review Request 52399: OOZIE-2666 Support embedding Jetty into Oozie

[Attila Sasvari]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52399/
---

(Updated Oct. 25, 2016, 3:42 p.m.)


Review request for oozie, András Piros, Peter Cseh, Peter Bacsko, and Robert 
Kanter.


Changes
---

Refactoring - use guice for dependency injection


Repository: oozie-git


Description (updated)
---

Embedding jetty into Oozie so that it can run as a standalone application. The 
changes also try to address OOZIE-2317 (i.e. Tomcat 6 is EOL). Jetty 9.2 is 
used as it works with Java 7; see 
http://www.eclipse.org/jetty/documentation/current/what-jetty-version.html.

New functionality
- By default build Oozie with embedded jetty. 'tomcat' profile can be used to 
build Oozie with embedded Tomcat.
- New module (server) is added that sets up an embedded Jetty server and start 
Oozie services. Servlet mapping is done by reading web.xml of webapp at 
runtime. JSP is handled with custom code. Server version is not revealed in 
server repsonses.
- SSL protocols and cipher suites, thread pool's size can be configured via 
oozie-default.xml for jetty. 
   
Changes
- Excluded jetty 6 dependencies from core and updated tests accordingly  
- Refactored assembly. Extracted distro-tomcat.xml 
- New profile in root pom: 'tomcat'. It is used to build Oozie with tomcat
- Refactored scripts: extracted tomcat and jetty starter scripts.
- oozie.sh is modified so that it starts Oozie with embedded jetty by default. 
If someone would like to use tomcat for any reason, they can build with profile 
'tomcat'.

TODOs:
- More code reviews
- Update Oozie Documentation
- Add more tests if needed
 
Cannot get rid of the Eclipse jdt compiler for compiling JSP (see 
https://github.com/eclipse/jetty.project/issues/706)


Diffs (updated)
-

  bin/mkdistro.sh 1ccd495bd5d49446e91250fd71eca5a6a723524a 
  core/src/main/conf/oozie-env.sh 390c955c0e9ef8b4c50226a4a50188d0b047af60 
  core/src/main/java/org/apache/oozie/util/ConfigUtils.java 
a56c5a295052fc7099c77be1409d4a89bcfc09e8 
  core/src/main/java/org/apache/oozie/util/Instrumentation.java 
99d64acec76a7f23a0d5b7fc98a2b9620b3b9a7d 
  core/src/main/resources/oozie-default.xml 
e71ebe3b7a85e6b23176ef30713af63847144498 
  distro/pom.xml c50572c57a376b28963d4e7da8ac7df777fe0480 
  distro/src/main/bin/oozie-jetty-server.sh PRE-CREATION 
  distro/src/main/bin/oozie-setup.sh 79b049bccceb2690f8a673a885a615c8d4d9578c 
  distro/src/main/bin/oozie-sys.sh 97d55a2b69c34ede007d4f65cdfc66f1ac2cfd13 
  distro/src/main/bin/oozie-tomcat-server.sh PRE-CREATION 
  distro/src/main/bin/oozied.sh a869c3da177c863a068f2af45c7bca9d5cb771ac 
  pom.xml 83a1d4254787c2a810e9db37a5d1433b96e01986 
  server/pom.xml PRE-CREATION 
  server/src/main/assemblies/empty.xml PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/EmbeddedOozieServer.java 
PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/HttpConfigurationWrapper.java 
PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/JspHandler.java PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/OozieFilterMapper.java 
PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/OozieRewriteHandler.java 
PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/OozieServletMapper.java 
PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/SSLServerConnectorFactory.java 
PRE-CREATION 
  
server/src/main/java/org/apache/oozie/server/guice/ConstraintSecurityHandlerProvider.java
 PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/guice/JettyServerProvider.java 
PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/guice/OozieGuiceModule.java 
PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/guice/ServicesProvider.java 
PRE-CREATION 
  server/src/main/resources/checkstyle-header.txt PRE-CREATION 
  server/src/main/resources/checkstyle.xml PRE-CREATION 
  server/src/test/java/org/apache/oozie/server/TestEmbeddedOozieServer.java 
PRE-CREATION 
  
server/src/test/java/org/apache/oozie/server/TestSSLServerConnectorFactory.java 
PRE-CREATION 
  src/main/assemblies/distro-jetty.xml PRE-CREATION 
  src/main/assemblies/distro-tomcat.xml PRE-CREATION 
  src/main/assemblies/distro.xml 1ffbfd6d2ba33b390999e9094cbb336fbce45c21 
  webapp/src/main/webapp/403.html PRE-CREATION 
  webapp/src/main/webapp/404.html PRE-CREATION 

Diff: https://reviews.apache.org/r/52399/diff/


Testing
---

- Tested basic functionality by executing a workflow that uses the sample 
JavaAction
- without SSL - on a 2.4.0 pseudo Hadoop cluster
- SSL with Kerberos is using a test CDH cluster 
- Added new unit tests that check
- If oozie.ssl.enabled is not specified in oozie-default.xml or in 
oozie-size.xml, server starts without SSL settings 
- If oozie.ssl.enabled is specified in oozie-default.xml or in 
oozie-size.xml, server starts with SSL settings
- SSL pro

[jira] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

[Attila Sasvari (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-22.patch

> Support embedding Jetty into Oozie
> --
>
> Key: OOZIE-2666
> URL: https://issues.apache.org/jira/browse/OOZIE-2666
> Project: Oozie
>  Issue Type: Sub-task
>  Components: core
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2666.PATCH-01.patch, OOZIE-2666.PATCH-02.patch, 
> OOZIE-2666.PATCH-03.patch, OOZIE-2666.PATCH-05.patch, 
> OOZIE-2666.PATCH-06.patch, OOZIE-2666.PATCH-07.patch, 
> OOZIE-2666.PATCH-09.patch, OOZIE-2666.PATCH-10.patch, 
> OOZIE-2666.PATCH-11.patch, OOZIE-2666.PATCH-12.patch, 
> OOZIE-2666.PATCH-13.patch, OOZIE-2666.PATCH-14.patch, 
> OOZIE-2666.PATCH-15.patch, OOZIE-2666.PATCH-16.patch, 
> OOZIE-2666.PATCH-17.patch, OOZIE-2666.PATCH-18.patch, 
> OOZIE-2666.PATCH-19.patch, OOZIE-2666.PATCH-20.patch, 
> OOZIE-2666.PATCH-21.patch, OOZIE-2666.PATCH-22.patch
>
>
> The purpose of this task is to allow Oozie to run as a standalone application 
> rather than being deployed to a container inside a WAR file.
> - Build embedded jetty enabled Oozie by default
> - Allow building Tomcat based Oozie by specifying the 'tomcat' profile
> - Starting Oozie with oozied.sh detect webserver type based on the build info
> - Oozie Web UI is working with JDK 8 if using embedded jetty 
> - If using Jetty, allow the user to configure the following settings via 
> oozie-default / oozie-site xml:
> -- request / response header size
> -- allowed HTTPS protocols
> -- excluded / weak cipher suites
> -- threadpool size



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OOZIE-2681) fix javadoc to compile on JDK8 again

[Abhishek Bafna (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek Bafna reassigned OOZIE-2681:
-

Assignee: Abhishek Bafna

> fix javadoc to compile on JDK8 again
> 
>
> Key: OOZIE-2681
> URL: https://issues.apache.org/jira/browse/OOZIE-2681
> Project: Oozie
>  Issue Type: Bug
>  Components: build
>Affects Versions: 4.3.0
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
>Priority: Critical
> Fix For: 5.0.0
>
>
> We have a lot of Javadoc build failures, which causes Oozie to fail to build 
> on Java 8, which is more strict than Java 6 or 7 was.  OOZIE-2178 fixed all 
> of these that existed at that time, but we've since introduced a lot more.  
> OOZIE-2487 made a workaround to prevent this from causing the build to fail, 
> but we should fix these (again) and remove the OOZIE-2487 workaround.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is back to normal : oozie-trunk-find-patches-available #137567

[Apache Jenkins Server]

See 

[jira] [Commented] (OOZIE-1986) Add FindBugs report to pre-commit build

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604565#comment-15604565
 ] 

Andras Piros commented on OOZIE-1986:
-

Those are flaky tests.

> Add FindBugs report to pre-commit build
> ---
>
> Key: OOZIE-1986
> URL: https://issues.apache.org/jira/browse/OOZIE-1986
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: Robert Kanter
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-1986-amend.001.patch, OOZIE-1986.001.patch, 
> OOZIE-1986.002.patch, OOZIE-1986.003.patch, OOZIE-1986.004.patch, 
> OOZIE-1986.005.patch, OOZIE-1986.006.patch, OOZIE-1986.007.patch, 
> OOZIE-1986.008.patch, OOZIE-1986.009.patch, OOZIE-1986.010.patch, summary.txt
>
>
> Now that we have OOZIE-1793, it will be really useful to have the pre-commit 
> build generate a findbugs report.  It should probably before and after the 
> patch and only complain it there are more after.  And it should link to the 
> report.  Ideally, this would do some kind of diff (like Hadoop does) so it's 
> easy to identify the new findbugs items.
> You can generate the findbugs reports by running:
> {noformat}
> mvn verify -DskipTests
> {noformat}
> This also runs checkstyle



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1986) Add FindBugs report to pre-commit build

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604563#comment-15604563
 ] 

Andras Piros commented on OOZIE-1986:
-

Done.

> Add FindBugs report to pre-commit build
> ---
>
> Key: OOZIE-1986
> URL: https://issues.apache.org/jira/browse/OOZIE-1986
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: Robert Kanter
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-1986-amend.001.patch, OOZIE-1986.001.patch, 
> OOZIE-1986.002.patch, OOZIE-1986.003.patch, OOZIE-1986.004.patch, 
> OOZIE-1986.005.patch, OOZIE-1986.006.patch, OOZIE-1986.007.patch, 
> OOZIE-1986.008.patch, OOZIE-1986.009.patch, OOZIE-1986.010.patch, summary.txt
>
>
> Now that we have OOZIE-1793, it will be really useful to have the pre-commit 
> build generate a findbugs report.  It should probably before and after the 
> patch and only complain it there are more after.  And it should link to the 
> report.  Ideally, this would do some kind of diff (like Hadoop does) so it's 
> easy to identify the new findbugs items.
> You can generate the findbugs reports by running:
> {noformat}
> mvn verify -DskipTests
> {noformat}
> This also runs checkstyle



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 52399: OOZIE-2666 Support embedding Jetty into Oozie

[András Piros]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52399/#review153780
---




server/src/main/java/org/apache/oozie/server/EmbeddedOozieServer.java (line 92)


TODO: use Guice for dependency injection and get rid of `setup()` method.



server/src/main/java/org/apache/oozie/server/EmbeddedOozieServer.java (lines 
145 - 161)


Should be put to separate class.



server/src/main/java/org/apache/oozie/server/EmbeddedOozieServer.java (line 214)


Could be done by Guice's `Injector`.



server/src/main/java/org/apache/oozie/server/OozieFilterMapper.java (lines 41 - 
49)


What is used in more than one places, e.g. `versions`, `v0` etc., can and 
should be put to constants.



server/src/main/java/org/apache/oozie/server/OozieServletMapper.java (lines 47 
- 50)


What is used in more than one places, e.g. `versions`, `v0` etc., can and 
should be put to constants.



server/src/main/java/org/apache/oozie/server/OozieServletMapper.java (lines 72 
- 77)


What is used in more than one places, e.g. `versions`, `v0` etc., can and 
should be put to constants.



webapp/src/main/webapp/WEB-INF/web.xml (lines 218 - 221)


Dead code, pls. remove.


- András Piros


On Oct. 24, 2016, 4:32 p.m., Attila Sasvari wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/52399/
> ---
> 
> (Updated Oct. 24, 2016, 4:32 p.m.)
> 
> 
> Review request for oozie, András Piros, Peter Cseh, Peter Bacsko, and Robert 
> Kanter.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Embedding jetty into Oozie so that it can run as a standalone application. 
> The changes also try to address OOZIE-2317 (i.e. Tomcat 6 is EOL). Jetty 9.2 
> is used as it works with Java 7; see 
> http://www.eclipse.org/jetty/documentation/current/what-jetty-version.html.
> 
> New functionality
> - By default build Oozie with embedded jetty. 'tomcat' profile can be used to 
> build Oozie with embedded Tomcat.
> - New module (server) is added that sets up an embedded Jetty server and 
> start Oozie services. Servlet mapping is done by reading web.xml of webapp at 
> runtime. JSP is handled with custom code. Server version is not revealed in 
> server repsonses.
> - SSL protocols and cipher suites, thread pool's size can be configured via 
> oozie-default.xml for jetty. 
>
> Changes
> - Excluded jetty 6 dependencies from core and updated tests accordingly  
> - Refactored assembly. Extracted distro-tomcat.xml 
> - New profile in root pom: 'tomcat'. It is used to build Oozie with tomcat
> - Refactored scripts: extracted tomcat and jetty starter scripts.
> - oozie.sh is modified so that it starts Oozie with embedded jetty by 
> default. If someone would like to use tomcat for any reason, they can build 
> with profile 'tomcat'.
> 
> TODOs:
> - More code reviews
> - Maven clean up
> - Packaging code clean up
> - Update Oozie Documentation
> - Add more tests if needed
> - Figure out how to get rid of the Eclipse jdt compiler for compiling JSP 
> (official documentation does not seem to work as expected for some reason)
> 
> 
> Diffs
> -
> 
>   bin/mkdistro.sh 1ccd495bd5d49446e91250fd71eca5a6a723524a 
>   core/src/main/conf/oozie-env.sh 390c955c0e9ef8b4c50226a4a50188d0b047af60 
>   core/src/main/java/org/apache/oozie/store/StoreStatusFilter.java 
> fb1db29cdfe1dbe37c8e2176079f39f841232ee3 
>   core/src/main/java/org/apache/oozie/util/Instrumentation.java 
> 99d64acec76a7f23a0d5b7fc98a2b9620b3b9a7d 
>   core/src/main/resources/oozie-default.xml 
> e71ebe3b7a85e6b23176ef30713af63847144498 
>   distro/pom.xml c50572c57a376b28963d4e7da8ac7df777fe0480 
>   distro/src/main/bin/oozie-jetty-server.sh PRE-CREATION 
>   distro/src/main/bin/oozie-setup.sh 79b049bccceb2690f8a673a885a615c8d4d9578c 
>   distro/src/main/bin/oozie-sys.sh 97d55a2b69c34ede007d4f65cdfc66f1ac2cfd13 
>   distro/src/main/bin/oozie-tomcat-server.sh PRE-CREATION 
>   distro/src/main/bin/oozied.sh a869c3da177c863a068f2af45c7bca9d5cb771ac 
>   pom.xml 83a1d4254787c2a810e9db37a5d1433b96e01986 
>   server/pom.xml PRE-CREATION 
>   server/src/main/assemblies/empty.xml PRE-CREATION 
>   server/src/main/java/org/apache/oozie/server/EmbeddedOozieServer.java 
> PRE-CREATION 
>   server/src/main/java/org/apache/oozie/server/HttpConfigurationWrapper.java 
> PRE-CREATION 
>   server/src/main/java/org/apache/o

Build failed in Jenkins: oozie-trunk-find-patches-available #137566

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1bf91be7b3f824ca4a9fb3e705764574f5dae4da 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1bf91be7b3f824ca4a9fb3e705764574f5dae4da
 > git rev-list 1bf91be7b3f824ca4a9fb3e705764574f5dae4da # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson1171775469998800199.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100  272k0  272k0 0   203k  0 --:--:--  0:00:01 --:--:--  203k
100  561k0  561k0 0   237k  0 --:--:--  0:00:02 --:--:--  237k
100  808k0  808k0 0   241k  0 --:--:--  0:00:03 --:--:--  241k
100  965k0  965k0 0   245k  0 --:--:--  0:00:03 --:--:--  245k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Jenkins build is back to normal : oozie-trunk-find-patches-available #137560

[Apache Jenkins Server]

See 

Build failed in Jenkins: oozie-trunk-find-patches-available #137559

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1bf91be7b3f824ca4a9fb3e705764574f5dae4da 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1bf91be7b3f824ca4a9fb3e705764574f5dae4da
 > git rev-list 1bf91be7b3f824ca4a9fb3e705764574f5dae4da # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson4567602098754467373.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100  272k0  272k0 0   208k  0 --:--:--  0:00:01 --:--:--  208k
100  536k0  536k0 0   208k  0 --:--:--  0:00:02 --:--:--  208k
100  720k0  720k0 0   217k  0 --:--:--  0:00:03 --:--:--  217k
100  833k0  833k0 0   218k  0 --:--:--  0:00:03 --:--:--  218k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure