TIBCO ActiveMatrix BusinessWorks Plug-in for AMQP 6.5.0 Hotfix 001 is released for all platforms. Please refer to the product Readme file for details regarding the supported platforms. 

Listed below is a summary of updates included in this Hotfix. Please refer to the Hotfix Readme for additional details and installation instructions.
===============================================================================================
Closed Issues in 6.5.0_HF-001  (This Release)

AMQP-524 :  RabbitMQ: Receiver stops receiving messages after receiving messages already sitting in the queue when flowlimit is set

NOTE: The following pointers should be taken care of while applying flow limit on the AMQP Receiver:
-- When the Flowlimit is applied in AMQP application, the Receiver will use the Pull API instead of Push API of RabbitMQ. This is because we don't have control over Push API in order to accept BW FlowLimit property.
-- If we use the Pull API on RabbitMQ console there would no consumers seen in the UI console as per RabbitMQ docs only Push API do subscribe as consumers which are seen in the UI console.
-- Since we do call Pull API continuously when BW Flowlimit is applied , we did set incremental backoff strategy way of calling in order to avoid performance issues . We can do set custom property "com.tibco.bw.amqp.rabbitmq.poll.delay.limit" as max delay which makes the application sleep for 500 ms incrementally upto custom property value or by default is 5 seconds.
-- The BW FlowLimit is applied at the application and component level i.e for one AMQP Receiver process etc., irrespective of Prefetch value.
-- Put sessioncount=1 when applying the Flowlimit for RabbitMQ connection.
If BW Flowlimit is applied at component level of the application then we need to set additional property which is mentioned as below
  --  To apply flowlimit at a component level for one process.
      --   Enable the flowlimit at component level and set this property <process_name>.job.flowlimit.enabled" to true. 
   --  To apply flowlimit at a component level for multiple processes. 
       -- Enable the flowlimit at component level and set this property "<process1-name>.<process2-name>.<process3-name>.job.flowlimit.enabled" to true.
    -- Note :-  <process_name> should be the name of the process in that component as it appears in the components view inside "Module Descriptors".
   Eg:
    -Dbw.application.job.flowlimit.testRabbitMQ.application=1
    -Dbw.application.job.flowlimit.testRabbitMQ.application.1.0=1
    -Dbw.application.job.flowlimit.testRabbitMQ.application.1.0.ComponentReceiver=1 

[Here "ComponentReceiver" is component name as it appears in the components view inside "Module Descriptors"]

--  It is mandatory to apply this property as well along with Component level FlowLevel Property   
     --    -Dtestrabbitmq.Receiver.job.flowlimit.enabled=true
===============================================================================================

This hotfix can be downloaded from TIBCO Support Customer Portal Web UI(https://support.tibco.com). You will need to provide your TIBCO Support Portal credentials. Once logged in you can download the hotfix by selecting the “Downloads” -> “Hotfixes” option under:

/AvailableDownloads/BusinessWorks/Plugins/AMQP/6.5.0/Hotfix 001

Product: TIBCO ActiveMatrix BusinessWorks Plug-in for AMQP
Version: 6.5.0
OS: All Supported Operating Systems

TIBCO ActiveMatrix BusinessWorks Plug-in for AMQP 6.5.0 Hotfix 001 is now available