The JVM could not be started. The maximum heap size (-Xmx) might be too large or an antivirus or firewall tool could block the execution.

book

Article ID: 224132

calendar_today

Updated On:

Products

Automic Automation Intelligence

Issue/Introduction

When trying to start the AAI application from a windows command prompt by running \<Install Dir>\"Automic_Automation_Intelligence (application).exe, the error below is seen.

There are also no log directory or logs under the  \<Install Dir>\jboss\standalone\ directory.

"The JVM could not be started. The maximum heap size (-Xmx) might be too large or an antivirus or firewall tool could block the execution."

 

Environment

Release : 6.3.0

Component :

Resolution

We found that the installation was run without a full Java JDK version installed on the server.

Instead the only Java on the server was the JRE which is embedded in the Autosys agent directory on the server.

 

Advised to download a full Java JDK and follow the steps below:

 

1. Drop the database you created originally.

 

2. Uninstall AAI again and delete the leftover directory.

 

3. Get JAVA JDK 1.8 installed under C:\Program Files\ or somewhere other then the Desktop.

 

4. Set JAVA_HOME to the base java directory.

 

5. Add %JAVA_HOME%\bin to the PATH Variable and move it to the top of the list of path variables.

 

6. Send me the output of the two commands below:

set > set.txt

path > path.txt

 

7. Once that looks ok, run the installer again.

 

8. The Oracle createDevices.sql sql script should be run as a DB user with admin rights.

 

9. The createDevices.sql script should be run as the user that was created in the createDevices.sql script.

 

10. Make sure the Oracle ojdbc8.jar is in the \jboss\standalone\deployments directory.  

https://docs.automic.com/documentation/webhelp/english/ALL/components/TERMA/latest/AAI%20Guides/Content/AAI_Topics/Release_Notes_6_0_0/Support-for-Non-Redistributable-Database-Drivers.htm

 

11. Start the config tool and verify the db can connect and that the configtool.log is clean.

 

12. Try to start the Automic Automation Intelligence service is able to start.