And strange enough, there is no such error in another node. See image below.
One of the reasons this happen is the web container of the 1st OpenAM instance is not restarted when the 2nd OpenAM instance is added.
How to resolve this? Restart the web container of the 1st OpenAM instance immediately after configuring the 2nd OpenAM instance.