Treatment of some faults in WebLogic installation process

This article involves the implementation of the installation process problems, and can not cover all the problems in the installation process, I hope that readers forgive me, if there are difficult problems, please contact me directly.
When you install WebLogic, the following error frequently occurs:
A fatal error has occurred. This application would terminate.
At this time, a lot of inexperienced people will not be able to start. In fact, WebLogic provides a good way to record the details of the installation process during the installation process to help us solve the problem during the installation process.
On the installation of the command line, we can add a-log parameter and specify the path to the installation log, complete with an example of the following command line:
Java-xmx1024m-jar Wls1032_generic.jar-mode=console-log=install.log-log_priority=debug

-xmx1024m at some point, the error message can be found in the installation log because of an installation error caused by a lack of memory in the Java heap installation process.
Log_priority is the level of the log file, and debug is the most detailed.

The following is the process by which I troubleshoot an installation problem by installing the log.
# Java-xmx1024m-jar Wls1032_generic.jar-mode=console-log=install.log-log_priority=debug
A fatal error has occurred. This application would terminate.
# more Install.log
2011-03-18 09:18:47,539 DEBUG [main] com.bea.plateng.wizard.wizardcontroller-wizard Controller Version 4.0.0.0 ( Saruman) started.
。。。。。。
2011-03-18 09:18:48,657 ERROR [Wizardcontroller] Com.bea.plateng.wizard.wizardcontroller-uncaught Exception
Java.lang.NullPointerException
At Java.security.SecureRandom.nextBytes (securerandom.java:292)
At Java.security.SecureRandom.next (securerandom.java:311
At Java.util.Random.nextLong (random.java:247)
At Java.io.File.generateFile (file.java:1682)
At Java.io.File.createTempFile (file.java:1791)
At Com.bea.plateng.wizard.installer.silent.tasks.SelfExtractionTask.doBefore (selfextractiontask.java:66
。。。。。。。
2011-03-18 09:18:48,667 DEBUG [Wizardcontroller] com.bea.plateng.wizard.wizardcontroller-terminating.
Due to the failure to perform multiple Java-related operations, it began to suspect that the JDK was not installed correctly. Require the host engineer to reinstall the JDK. The above phenomenon still occurs after the host engineer upgrades the virtual machine to IBM Jdk64bit SR7.
By error message "Java.lang.NullPointerException
At Java.security.SecureRandom.nextBytes "with hints from Metalink and Google Docs, sensory issues appear on components related to JDK security." There are three main solutions on the Web:
Need to change JDK environment variables;
To view the installation files under the Jre/lib/ext path
Modify the security files under Jre/lib/security
In another test environment for the customer, WebLogic can run normally. The version of the virtual machine is also consistent with the server being operated on. Begins a comparison of the Java Virtual Machine environment for both environments, mainly comparing files under Jre/lib/ext and jre/lib/security.
Several files in the jre/lib/security environment under the fault environment are found by comparison. After the normal environment files are copied to the environment, the WebLogic can start normally and all functions are back to normal.

The cause of the failure is suspected to be an upgrade of the JDK, failed to upgrade properly caused.

Reprint Please specify: http://blog.csdn.net/woohooli/archive/2011/04/26/6364914.aspx