Build failed in Jenkins: flume-trunk #487

2013-08-07 Thread Apache Jenkins Server 
See https://builds.apache.org/job/flume-trunk/487/

--
[...truncated 905 lines...]
Aug 7, 2013 2:13:41 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-clean-plugin:2.4.1:clean (default-clean) @ flume-ng-channels ---
[INFO] Deleting 
https://builds.apache.org/job/flume-trunk/ws/flume-ng-channels/target
Aug 7, 2013 2:13:41 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 7, 2013 2:13:41 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-remote-resources-plugin:1.1:process (default) @ 
flume-ng-channels ---
Aug 7, 2013 2:13:41 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 7, 2013 2:13:41 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- apache-rat-plugin:0.7:check (verify.rat) @ flume-ng-channels ---
[INFO] Exclude: .idea/
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/nb-configuration.xml
[INFO] Exclude: .git/
[INFO] Exclude: patchprocess/
[INFO] Exclude: .gitignore
[INFO] Exclude: .repository/
[INFO] Exclude: **/*.diff
[INFO] Exclude: **/*.patch
[INFO] Exclude: **/*.avsc
[INFO] Exclude: **/*.avro
[INFO] Exclude: **/docs/**
[INFO] Exclude: **/test/resources/**
[INFO] Exclude: **/.settings/*
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.project
[INFO] Exclude: **/target/**
Aug 7, 2013 2:13:42 PM org.apache.maven.cli.event.ExecutionEventLogger 
projectStarted
INFO: 
Aug 7, 2013 2:13:42 PM org.apache.maven.cli.event.ExecutionEventLogger 
projectStarted
INFO: 
Aug 7, 2013 2:13:42 PM org.apache.maven.cli.event.ExecutionEventLogger 
projectStarted
INFO: Building Flume NG JDBC channel 1.5.0-SNAPSHOT
Aug 7, 2013 2:13:42 PM org.apache.maven.cli.event.ExecutionEventLogger 
projectStarted
INFO: 
Downloading: 
http://repo1.maven.org/maven2/commons-dbcp/commons-dbcp/1.4/commons-dbcp-1.4.pom
Downloaded: 
http://repo1.maven.org/maven2/commons-dbcp/commons-dbcp/1.4/commons-dbcp-1.4.pom
 (11 KB at 2174.8 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/commons-pool/commons-pool/1.5.4/commons-pool-1.5.4.pom
Downloaded: 
http://repo1.maven.org/maven2/commons-pool/commons-pool/1.5.4/commons-pool-1.5.4.pom
 (12 KB at 2805.2 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/org/apache/derby/derby/10.8.2.2/derby-10.8.2.2.pom
Downloaded: 
http://repo1.maven.org/maven2/org/apache/derby/derby/10.8.2.2/derby-10.8.2.2.pom
 (3 KB at 656.5 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/org/apache/derby/derby-project/10.8.2.2/derby-project-10.8.2.2.pom
Downloaded: 
http://repo1.maven.org/maven2/org/apache/derby/derby-project/10.8.2.2/derby-project-10.8.2.2.pom
 (7 KB at 1674.6 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/commons-dbcp/commons-dbcp/1.4/commons-dbcp-1.4.jar
Downloading: 
http://repo1.maven.org/maven2/commons-pool/commons-pool/1.5.4/commons-pool-1.5.4.jar
Downloading: 
http://repo1.maven.org/maven2/org/apache/derby/derby/10.8.2.2/derby-10.8.2.2.jar
Downloaded: 
http://repo1.maven.org/maven2/commons-dbcp/commons-dbcp/1.4/commons-dbcp-1.4.jar
 (157 KB at 14250.6 KB/sec)
Downloaded: 
http://repo1.maven.org/maven2/commons-pool/commons-pool/1.5.4/commons-pool-1.5.4.jar
 (94 KB at 7830.5 KB/sec)
Downloaded: 
http://repo1.maven.org/maven2/org/apache/derby/derby/10.8.2.2/derby-10.8.2.2.jar
 (2609 KB at 32612.0 KB/sec)
Aug 7, 2013 2:13:42 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 7, 2013 2:13:42 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-clean-plugin:2.4.1:clean (default-clean) @ flume-jdbc-channel 
---
[INFO] Deleting 
https://builds.apache.org/job/flume-trunk/ws/flume-ng-channels/flume-jdbc-channel/target
Aug 7, 2013 2:13:42 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 7, 2013 2:13:42 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-remote-resources-plugin:1.1:process (default) @ 
flume-jdbc-channel ---
Aug 7, 2013 2:13:43 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 7, 2013 2:13:43 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-resources-plugin:2.4.3:resources (default-resources) @ 
flume-jdbc-channel ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/flume-trunk/ws/flume-ng-channels/flume-jdbc-channel/src/main/resources
[INFO] Copying 3 resources
Aug 7, 2013 2:13:43 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 7, 2013 2:13:43 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 
flume-jdbc-channel ---
[INFO] Compiling 15 source files to

[jira] [Commented] (FLUME-2140) Support diverting bad events from pipeline

2013-08-07 Thread Arvind Prabhakar (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13732732#comment-13732732
 ] 

Arvind Prabhakar commented on FLUME-2140:
-

[Discussion 
thread|http://flume.markmail.org/thread/y3cks6hdgof3kxu6#query:+page:1+mid:rx3zm53t4dhmqskk+state:results]
 on this subject in the user-list for reference.

 Support diverting bad events from pipeline
 --

 Key: FLUME-2140
 URL: https://issues.apache.org/jira/browse/FLUME-2140
 Project: Flume
  Issue Type: New Feature
  Components: Node
Reporter: Arvind Prabhakar

 A *bad event* can be any event that causes persistent sink side processing 
 failure due to the inherent nature of the event itself. Note that failures 
 that are not related to the inherent nature of the event such as network 
 communication failure, downstream capacity failure etc., do not make the 
 event a bad-event.
 The presence of a bad event in a channel can cause the entire pipleline to 
 choke and become unusable. Flume should therefore be able to identify bad 
 events and provide a facility to route them out of the pipleline in order to 
 ensure the transport of other events continues uninterrupted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLUME-2151) Windows: Update TestExecSource to use native commands on Windows

2013-08-07 Thread Roshan Naik (JIRA) 

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

Roshan Naik updated FLUME-2151:
---

Summary: Windows:  Update TestExecSource to use native commands on Windows  
(was: Windows:  Fix testExecSource to use alternative commands on Windows)

 Windows:  Update TestExecSource to use native commands on Windows
 -

 Key: FLUME-2151
 URL: https://issues.apache.org/jira/browse/FLUME-2151
 Project: Flume
  Issue Type: Bug
  Components: Windows
Affects Versions: v1.4.0
Reporter: Roshan Naik
Assignee: Roshan Naik
  Labels: windows
 Attachments: FLUME-2151.patch


 The test invokes unix commands like 'ps' etc.
 Need to use Windows alternatives.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FLUME-2151) Windows: Update TestExecSource to use native commands on Windows

2013-08-07 Thread Roshan Naik (JIRA) 

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

Roshan Naik updated FLUME-2151:
---

Attachment: (was: FLUME-2151.patch)

 Windows:  Update TestExecSource to use native commands on Windows
 -

 Key: FLUME-2151
 URL: https://issues.apache.org/jira/browse/FLUME-2151
 Project: Flume
  Issue Type: Bug
  Components: Windows
Affects Versions: v1.4.0
Reporter: Roshan Naik
Assignee: Roshan Naik
  Labels: windows

 The test invokes unix commands like 'ps' etc.
 Need to use Windows alternatives.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira