7.0 Supported Configurations: Sun Solaris 7 on SPARC
Sun Solaris 7 on SPARC with WebLogic Server 7.0 SP3
Note: On December 31, 2005, BEA will end support for WebLogic Platform 7.0 on Solaris 7 configurations. BEA recommends that all customers currently running WebLogic Platform 7.0 on Solaris 7 upgrade to a version of Solaris for which support will be continued.
For Sun's support services information site, see http://www.sun.com/service/support. If you have a support contract for the use of Solaris platforms, you may be able to obtain support for general Java issues (for example, JVM problems).
You can run WebLogic software on Solaris using the SDK available from Sun Microsystems at: http://java.sun.com/products/?frontpage-main. BEA recommends using the latest available versions of the JVMs supported by BEA, except where noted otherwise in our Supported Configurations document.
Table 4-1 Requirements for 7.0 SP3 on Sun Solaris 7 on SPARC
Operating System Version and Patches
Chip Architecture and Minimum Processor Speed
UltraSPARC (168 MHz)
Sun Java 2 SDK 1.3.1_08 (32 bit) and all later service packs of 1.3.1
Supports the Java HotSpotTM Client and Server VMs
Sun Java 2 SDK 1.4.1_02 (32 bit) with Java HotSpotTM Client VM and all later service packs of 1.4.1
Supported only for WebLogic Server clients and the WebLogic Workshop IDE. Can be used to run WebLogic Server RMI or Web Services clients that remotely connect to a server running in a separate VM.
It is not supported by WebLogic Portal or WebLogic Integration clients and development tools. Is is also not supported by running server instances of WebLogic Server or other WebLogic Platform components.
The 7.3.4 jDriver for Oracle is not supported with JDK 1.3.1.
Some Solaris JVMs report an incorrect IP number. The IP number reported for the machine is the first number in the /etc/hosts file. Unfortunately, this number is frequently 127.0.0.1, the standard loopback network address for the machine. This problem affects licenses granted for specific IP numbers. We have also observed this problem in a cluster where an HTTP request is passed by a Web server or another WebLogic Server via the HttpClusterServlet, to a WebLogic Server running on a Solaris machine with this configuration problem. The 127.0.0.1 IP number is carried with the server's response.
To determine whether you have this problem on your Solaris computer, run the following command:
If you see 127.0.0.1 in the output, ask the system administrator to move the computer's network IP address to the beginning of the /etc/hosts file.
For information about suggested values for some Solaris TCP and VM-related tunable parameters, see Operating System Tuning in BEA WebLogic Server 7.0 Performance and Tuning.
If you have problems with OutOfMemory errors and the JVM crashing with JDK 1.3, try setting: -XX:MaxPermSize=128m. For WebLogic Integration, use the following setting: -XX:MaxPermSize=256m.
For more information about known issues with any components of this release, see the appropriate Release Notes document. For a complete list of Release Notes supporting WebLogic Platform 7.0, see: