Skip to main content
Question

Could not connect to FME Core after running a failover test

  • November 29, 2017
  • 1 reply
  • 14 views
rob_datavision
Contributor
Forum|alt.badge.img+1

I have set up a active passive architecture as per the guide

https://docs.safe.com/fme/2016.1/html/FME_Server_Documentation/Content/AdminGuide/Active-Passive-Basic-Architecture.htm

Everything on the system runs as expected - no problems for a couple of weeks since installation.

I then run a failover test as per the guide

http://docs.safe.com/fme/html/FME_Server_Documentation/Content/AdminGuide/Test_for_Failover.htm

After that I can no longer access FME core even the the logs say it is running. I have checked everything but despite all my efforts, I cannot connect to the core via the web app server.

Has anyone had this problem? Can anyone provide some guidance on how to fix this please?

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

rob_datavision
Contributor
Forum|alt.badge.img+1
  • rob_datavisionContributor
  • Author
  • Contributor
  • November 29, 2017

I just solved my own problem. I reviewed all setup steps - particularly the configuration file settings. I misread one word.

On this page https://docs.safe.com/fme/2016.1/html/FME_Server_Documentation/Content/AdminGuide/Install_the_FME_Server_Services.htm

Under the heading Configure the FME Server Services for Failover it says

  1. Open each web application properties file located at:

<WebAppDir>\\<fmeServiceName>\\WEB-INF\\conf\\propertiesFile.properties

Initially I found one file and changed that. I didn't realize there were more!

I just did a search on files with name propertiesFile.properties in the installation folder and found 9!

6 needed to be updated. 1 had been updated and 2 did not have the setting.

I made the changes in ALL the files, restarted the service and everything was back to normal.

The failover test then succeeded.

What a relief. Big impact from a simple mistake.

Perhaps in Australia we are divided by a common language. I might have worded it "Open all web application property files located at". I might also have listed the possible <fmeSrviceName> folders to make it clearer.

Community Stats

32,128
Posts
121,966
Replies
39,779
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.