Also the following changes needs to be done in project for AMQPReceiveMessage activity after installing this hotfix. 

* Stop and close all running BW applications in studio or in TEA wherever the BW application is deployed.

* AMQP SharedResource config property needs to enable the Connection Recovery option and provide the network recovery interval value in msec. Please see attached screenshot (AMQP278.png) for reference.

* If you need to override the default prefetch count value of 20, then you need to add below java property for the prefetch count in the BWCE environment:
                  
       -Dcom.tibco.plugin.amqp.rabbitmq.prefetch=<value they would like, e.g. 30>

* Below is the procedure of setting the BW_JAVA_OPTS property in BWCE env.
                        
        Set JAVA properties in BWCE runtime. e.g. BW_JAVA_OPTS :  "-Dname=value -Dname=value", BW_JAVA_OPTS: "-javaagent:\\/home\\/vcap\\/app\\/agent\\/javaagent.jar -Dappdynamics.controller.hostName=<hostname> -Dappdynamics.controller.port=<Port Number> -Dappdynamics.agent.applicationName=<App-Name> -Dappdynamics.agent.tierName=<tier Name> -Dappdynamics.agent.nodeName=<node Name>

* If the you are running the BW application in BW studio, then you need to add above property in the run configuration under vm arguments of the studio.

* Restart the BW application and run, when the broker goes down, it will reconnect and will start receiving messages again.

Listed below is a summary of updates included. Refer to the associated readme document for any additional information.