7.0 Supported Configurations: Sun Solaris 8 on SPARC

Sun Solaris 8 on SPARC with 7.0 SP5

Provides full support for WebLogic Server and run-time support for WebLogic Workshop, WebLogic Integration, and WebLogic Portal. See below for Design and Development Tools support.

This section provides the following information:

Related Information

For information about supported database configurations, Web servers, and browsers, plus support for interoperability tools and WebLogic Platform product support information, see WebLogic Platform 7.0 Supported Configurations.
For details about Sun Solaris 8, visit Sun's Solaris Web page at: http://www.sun.com/solaris.
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.

Configuration Requirements

Table 3-1 Requirements for 7.0 SP5 on Sun Solaris 8 on SPARC

Operating System Version and Patches	Solaris 8
Chip Architecture and Minimum Processor Speed	UltraSPARC (168 MHz)
SDK	Fully-supported
	Sun Java 2 SDK 1.3.1_10 (32 bit) and all later service packs of 1.3.1	Supports the Java HotSpot^TM Client and Server VMs. WebLogic Integration and WebLogic Portal are configured to use the Sun Java 2 SDK 1.3.1_10 with the Java HotSpot Server VM. For details, see "Using the HotSpot Virtual Machine" in "Performance Tuning" in "System Administration" in the WebLogic Portal Administration Guide at the following URL: `http://download.oracle.com/docs/cd/E13218_01/wlp/docs70/admin/sysadmin.htm`
	Client-only
	Sun Java 2 SDK 1.4.2_03 (32-bit) with Java HotSpot^TM Client VM and all later service packs of 1.4.2	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.
Design and Development Tools	Supports WebLogic Server development tools. For more information about WebLogic Platform design and development tools support, see Supported Configurations for Design and Development Tools in Version 7.0 SP5 in Supported Configurations for WebLogic Platform 7.0.
RAM	512 MB required; 1 GB recommended
Disk Space	For any components of WebLogic Platform or for the full WebLogic Platform product, see Disk Space Requirements.
Performance Pack	Included
Node Manager	Java
BEA jDrivers for Oracle	For this Oracle client version:	The following shared libraries are provided:
	Oracle 8.1.7	`lib/solaris/oci817_8/libweblogicoci38.so` `lib/solaris/oci817_8/libweblogicoxa38.so`
	Oracle 9.0.1	`lib/solaris/oci901_8/libweblogicoci38.so` `lib/solaris/oci901_8/libweblogicoxa38.so`
	Oracle 9.2.0	`lib/solaris/oci920_8/libweblogicoci38.so` `lib/solaris/oci920_8/libweblogicoxa38.so`

Known Issues

The JIT (Just-In-Time) Compiler is supported only for 1.2.2_05a when the export _JVM_ARGS="inline_instrs_jit=0" directive is being used.This is due to two Sun bugs: #4333396 (JVM crash during JIT) and #4333696. The error message reads:

SIGABRT and JIT coredump: panic: Unexpected operand kind(10) in j86OpndImage.

These bugs also affect 1.2.1_04, so you must Disable aggressive inlining by the JIT with: export _JIT_ARGS=novinline.

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. Subsequent calls to that machine time out because the IP number is incorrect.

To determine whether you have this problem on your Solaris computer, run the following command: java utils.netAddresses
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.

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 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.

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:

http://download.oracle.com/docs/cd/E13196_01/platform/docs70/interm/relnotes.html