Weblogic 12.1.3.0执行config.sh创建域时立即退出，请求技术支持

Let’s walk through practical fixes for this silent exit issue—since the script isn’t throwing visible errors, we need to dig into logs and environment checks first:

1. Verify Java Environment Compatibility #

Weblogic 12.1.3.0 requires JDK 7u51+ or JDK 8u20+ (JRE alone won’t work, as domain creation depends on JDK tools like javac). Run these commands to confirm your setup:

echo $JAVA_HOME
java -version
javac -version

Ensure JAVA_HOME points directly to a valid JDK directory (not a JRE), and that the JDK version meets the minimum requirement. Adjust your environment variables if needed.

2. Check Config Logs for Hidden Errors #

The config.sh script generates a log file by default, but it’s often stored in a non-obvious location. Force it to write to a visible path with:

./config.sh -mode=console -log=/tmp/weblogic_config.log

Open /tmp/weblogic_config.log afterward—this will almost always reveal why the script exited early (e.g., missing permissions, invalid environment paths, or component conflicts).

3. Fix File/Directory Permissions #

Make sure your user has full read/write/execute access to the Weblogic installation directory and the config.sh script itself. Check permissions with:

# Replace with your actual Weblogic bin path
ls -ld /opt/weblogic/oracle_common/common/bin/
ls -l /opt/weblogic/oracle_common/common/bin/config.sh

If the script isn’t executable, fix it:

chmod +x /opt/weblogic/oracle_common/common/bin/config.sh

Also, ensure the /tmp directory has enough space and write permissions—Weblogic uses it for temporary files during domain creation.

4. Clear or Unset the DISPLAY Variable #

Even in console mode, some Java-based installers might still check for a DISPLAY variable (a holdover from GUI mode). Try unsetting it before running the script:

unset DISPLAY
./config.sh -mode=console

Or set it to an empty value:

export DISPLAY=
./config.sh -mode=console

5. Run the Java Launcher Directly (Bypass the Shell Script) #

The config.sh is just a wrapper around a Java JAR. Bypass the script to see raw error output from the Java process. Navigate to the config.sh directory and run:

# Replace paths with your actual Weblogic installation paths
$JAVA_HOME/bin/java -jar $COMMON_COMPONENTS_HOME/common/lib/config-launcher.jar -mode=console

This will print any uncaught exceptions or missing dependencies directly to your terminal, which the shell script might be suppressing.

6. Install Missing System Libraries #

Some Weblogic components rely on basic X11 libraries (even in console mode). If your server is missing these, the Java process might exit silently. Install them based on your distro:

CentOS/RHEL: #

yum install libXtst.x86_64 libXext.x86_64 libX11.x86_64

Ubuntu/Debian: #

apt-get install libxtst6 libxext6 libx11-6

Start with checking the logs first—9 times out of 10, the log file will tell you exactly what’s wrong.

内容的提问来源于stack exchange，提问作者Sreejith