You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/01/04 09:33:00 UTC
[jira] [Commented] (NIFI-5921) ConsumeJMS: Allow user to set
timeout length
[ https://issues.apache.org/jira/browse/NIFI-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733969#comment-16733969 ]
ASF subversion and git services commented on NIFI-5921:
-------------------------------------------------------
Commit cd91197a45a94465874cbaf68ffa11df8bc63011 in nifi's branch refs/heads/master from Ryan Whittington
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=cd91197 ]
NIFI-5921 - Added property to allow a user to define a timeout on the ConsumeJMS processor
Co-Authored-By: rwhittington <ry...@gmail.com>
Signed-off-by: Pierre Villard <pi...@gmail.com>
This closes #3240.
> ConsumeJMS: Allow user to set timeout length
> --------------------------------------------
>
> Key: NIFI-5921
> URL: https://issues.apache.org/jira/browse/NIFI-5921
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Ryan Whittington
> Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The ConsumeJMS processor has a hardcoded timeout when retrieving messages. This can cause problems when consuming lots of messages or large messages.
> I've fixed this locally by adding a new processor property to specify a timeout.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)