Skip to content

Application Fails to Start

These problems may prevent Reflection X applications from launching:

No Java Runtime Environment (JRE) was found

Reflection X applications require a JRE on your system. On Windows systems, the JRE is included as a separate feature in the installation -- called Java Runtime Environment (JRE). If this feature has not been installed and no additional JRE is available on your system, you see a message saying that the application "failed to start because no Java Runtime Environment was found." To resolve this, install the JRE using the procedure below.

If the JRE feature is not installed and an alternate JRE is found on your system, Reflection X will start using the alternate JRE, but you will see errors or warning messages in the log files if this JRE is not correctly configured. For information about these messages, see Changing the JRE.

To install the default JRE

  1. To open the Programs and Features control panel go to Start > Control Panel > Programs and Features. (On older Windows systems, this Control Panel is called Add or Remove Programs.)

  2. Select your Reflection product and click Change.

  3. On the Feature Selection tab, click the icon to the left of Java Runtime Environment (JRE) and select Feature will be installed on local hard drive.

  4. Click Continue.

Insufficient Memory

When Reflection X applications start, they request a block of memory from the computer system. If your system's memory is limited or fragmented, you may see an error saying "Application failed to start due to insufficient memory." For more information, see Technical Information Document 7021829.

Insufficient Entropy on Linux Systems

When Reflection X applications and services start, they request random number generators from the Operating System. If the Operating System does not have enough entropy to generate secure random numbers, the application or service does not start. A proper initialization sequence for the random generators adds the following two lines to the log:

Initializing FIPS approved SecureRandom. 

SecureRandom Initialized. PRNG algorithm used by SecurityFactory is : XYZ

If the system does not have enough entropy, the log includes only the following line without the second message:

Initializing FIPS approved SecureRandom.

Entropy issues are common with virtual machines and machines that are not physically interacted with. A solution to this issue is to install the HAVEGED service on your linux system. This third party service replenishes the entropy pool of the Operating System: https://www.issihosts.com/haveged/

Back to top