[jira] [Commented] (FLUME-3246) Validate flume configuration to prevent larger source batch size than the channel transaction capacity

[ https://issues.apache.org/jira/browse/FLUME-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598203#comment-16598203 ] Hudson commented on FLUME-3246: --- SUCCESS: Integrated in Jenkins build Flume-trunk-hbase-1 #354 (See

[jira] [Updated] (FLUME-3271) Update User Guide to follow log4j2 upgrade changes

[ https://issues.apache.org/jira/browse/FLUME-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Turcsanyi updated FLUME-3271: --- Description: Flume logging has been upgraded from logj4 1.2.x to 2.x (FLUME-2050), but the

[jira] [Updated] (FLUME-3271) Update User Guide to follow log4j2 upgrade changes

[ https://issues.apache.org/jira/browse/FLUME-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Turcsanyi updated FLUME-3271: --- Fix Version/s: 1.9.0 > Update User Guide to follow log4j2 upgrade changes >

[jira] [Created] (FLUME-3271) Update User Guide to follow log4j2 upgrade changes

Peter Turcsanyi created FLUME-3271: -- Summary: Update User Guide to follow log4j2 upgrade changes Key: FLUME-3271 URL: https://issues.apache.org/jira/browse/FLUME-3271 Project: Flume Issue

[jira] [Updated] (FLUME-3270) Close JMS resources in JMSMessageConsumer constructor in case of failure

[ https://issues.apache.org/jira/browse/FLUME-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Turcsanyi updated FLUME-3270: --- Status: Patch Available (was: In Progress) > Close JMS resources in JMSMessageConsumer