Presence of a corrupt jar in the environment (FGLAM_HOME/jre) caused the FglAM not to start up properly. In this particular case, when the FglAM was started as a stand alone process below errors were seen.
Replace the specific jar file (in this case rt.jar) from a working equivalent of FglAM installation.
Please ensure to make a backup of the corrupt jar on the problematic FglAM before making the copy from the working environment.
One the jar file has been replaced, restart the FglAM.