Hello @Alex Jiang,

Please be informed that the only currently supported version of JRFA 7.x is JRFA 7.6.1. Many issues have been fixed since JRFA 7.2, so the recommended approach would be to upgrade to the supported version of JRFA and confirm that the issue is still is happening.

Would like to share additional, optional, information, that I hope may be helpful.

From my experience, the super-safe approach to troubleshooting this type of issue would be to download JRFA 7.6 SDK, and first run the example Starter consumer that comes with it in your environment and test the failover via Starter consumer in your environment. Not via a webserver, but as is.

If the failover happens properly, next would try to test the same code, but via web server. This approach is certainly more work, but you can see what is being accomplished? We are aiming to pinpoint the exact source of the issue, and next try to address it at the source. If the failover happens, with standard example code, and via webserver as well, then upgrade the custom app to JRFA 7.6 as well and be done.

If however, the failover does not happen on the standard example as it should, at any point of the above investigation, I would first investigate why, at that point, via standard example, without involving custom code factor.

Hope this information helps

@zoya.farberov, yes, we are using JRFA 7.2. Recently, we upgraded the JDK from 1.6 to 1.8, and moved the service from Websphere 7 to Tomcat 9/Spring Boot 2 running on PCF. It happened since we moved it to the new platform.

Thanks, @zoya.farberov. We are going to try JRFA 7.6.1, and keep you posted