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 https://issues.apache.org/jira/browse/NIFI-9239?jql=project%20%3D%20NIFI%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20text%20~%20%22JMS%22%20AND%20fixVersion%20%3E%201.11.0%20ORDER%20BY%20fixVersion%20DESC Thanks On Thu, Jan 13, 2022 at 8:29 AM nayan sharma <[email protected]> wrote: > NiFi 1.11 .0 > > On Thu, 13 Jan 2022 at 18:27, Juan Pablo Gardella < > [email protected]> wrote: > >> Which Nifi version are you using? >> >> On Thu, 13 Jan 2022 at 09:14, nayan sharma <[email protected]> >> 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 *SYSTEM_LOGGING_LOST_EVENT* alerts on solace >>> production appliance leading to buffer pool is exhausted. >>> >>> >>> >>> >>> >>> We have seen that high *CLIENT_CLIENT_UNBIND* requests from >>> applications and that leads to very high solace logging events. >>> >>> >>> Any suggestion would be appreciated. >>> >>> >>> Thanks & Regards, >>> Nayan Sharma >>> *+91-8095382952* >>> >>> <https://www.linkedin.com/in/nayan-sharma> >>> <http://stackoverflow.com/users/3687426/nayan-sharma?tab=profile> >>> >> -- > Thanks & Regards, > Nayan Sharma > *+91-8095382952* > > <https://www.linkedin.com/in/nayan-sharma> > <http://stackoverflow.com/users/3687426/nayan-sharma?tab=profile> >
