1. Start flashback
Ideas:
- find the reason
- find startup log
- Check the cause of the startup failure according to the startup log
Second, find the startup log
- Start in debug mode
- Check the console – operate according to the console
-
Look at the generated startup log file
-
view log
DEBUG: Using PENTAHO_JAVA_HOME
DEBUG: _PENTAHO_JAVA_HOME=E:\java8
DEBUG: _PENTAHO_JAVA=E:\java8\bin\java.exe
E:\kettle\data-integration>"E:\java8\bin\java.exe" "-Xms1024m" "-Xmx2048m" "-Djava.library.path=libswt\win32;/bin" "-Djava.endorsed.dirs=E:\java8\jre\lib\endorsed;E:\java8\lib\endorsed;E:\kettle\data-integration\system\karaf\lib\endorsed" "-DKETTLE_HOME=" "-DKETTLE_REPOSITORY=" "-DKETTLE_USER=" "-DKETTLE_PASSWORD=" "-DKETTLE_PLUGIN_PACKAGES=" "-DKETTLE_LOG_SIZE_LIMIT=" "-DKETTLE_JNDI_ROOT=" -jar launcher\launcher.jar -lib ..\libswt\win32 /level:Debug
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
- translate
- Modify the spoon.bat file
and make it smaller
if "%PENTAHO_DI_JAVA_OPTIONS%"=="" set PENTAHO_DI_JAVA_OPTIONS="-Xms512m" "-Xmx512m"
- Start the debug mode again – check the log
8. Baidu
modify the following information:
Before modification
, check how many bits of jdk you have installed.
My jdk is 32 bits
. Change:
- next bug
- I checked the information and found no solution, but I was reminded that it may be a problem with the jdk version, so I re-downloaded jdk1.8 from the official website decisively
And modify the original configuration back
- Start successfully
3. Summary
- Many people will encounter the exception of memory overflow
- Environment variables are not configured properly
- The number of jdk digits is inconsistent with that used by kettle
- In other cases, it is largely a jdk version problem, you can uninstall and try another version