nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Chermak (Jira)" <j...@apache.org>
Subject [jira] [Updated] (NIFI-6718) New JMS Session/Producer created for each message published
Date Thu, 26 Sep 2019 14:26:00 GMT

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

Tim Chermak updated NIFI-6718:
------------------------------
    Component/s:     (was: Core Framework)
                 Extensions

> New JMS Session/Producer created for each message published
> -----------------------------------------------------------
>
>                 Key: NIFI-6718
>                 URL: https://issues.apache.org/jira/browse/NIFI-6718
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Extensions
>    Affects Versions: 1.8.0
>         Environment: Linux. CENTOS 7
>            Reporter: Tim Chermak
>            Priority: Minor
>              Labels: performance
>
> When GetFile supplies flowfiles to PublishJMS we see one session and producer for all
JMS messages in the TIBCO log. When ConsumeJMS supplies flowfiles to PublishJMS we see a new
session and producer for each message in the TIBCO log. For all JMS processors we have a "Session
Cache Size" at the default of 1. Although, in the processor help it indicates this has been
deprecated and no longer has any effect on the processor.
> It appears that the Session Cache Size should allow a variable value in order to allow
for more efficient use of JMS. Shouldn't the JMS objects connection session consumer and producer
be reused (cached) as much as possible for efficiency?
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message