Probabl you faced https://issues.apache.org/jira/browse/NIFI-7563. Check a
newer version.
On Thu, 13 Jan 2022 at 13:02, Joe Witt wrote:
> Solace is a commonly used JMS provider with NIFi and it is very likely
> such an issue has been addressed. Please test/attempt this on a newer
> version of
Solace is a commonly used JMS provider with NIFi and it is very likely such
an issue has been addressed. Please test/attempt this on a newer version
of NiFi.
Fixed related to JMS since 1.11
NiFi 1.11 .0
On Thu, 13 Jan 2022 at 18:27, Juan Pablo Gardella <
gardellajuanpa...@gmail.com> wrote:
> Which Nifi version are you using?
>
> On Thu, 13 Jan 2022 at 09:14, nayan sharma
> wrote:
>
>> Hi All,
>>
>>
>>
>> We are using consumeJMS to consume messages from the Solaxce system from
>>
Which Nifi version are you using?
On Thu, 13 Jan 2022 at 09:14, nayan sharma wrote:
> Hi All,
>
>
>
> We are using consumeJMS to consume messages from the Solaxce system from
> multiple queues but we are getting multiple bind/unbind requests.
>
> As we are getting alerts
Hi All,
We are using consumeJMS to consume messages from the Solaxce system from
multiple queues but we are getting multiple bind/unbind requests.
As we are getting alerts *SYSTEM_LOGGING_LOST_EVENT* alerts on solace
production appliance leading to buffer pool is exhausted.
We have seen
