Supported Configurations: Sun Solaris

BEA WebLogic Server 9.0 and Related Products on Solaris 8

This section provides the following information:

Related Information

For information about supported database configurations, Web servers, browsers, and interoperability tools, plus BEA product support for AquaLogic Service Bus 2.0 and WebLogic Server 9.0, see:

For information about the Solaris operating system, see the following Sun Web site: http://www.sun.com/solaris.
For information about Sun's support services—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, JDK problems). See http://www.sun.com/service/support.

Configuration Requirements

Table 17-1 Requirements for Solaris 10 on SPARC Using Sun 32-bit JDK

Operating System Version and Patches	Solaris 8
Chip Architecture and Minimum Processor Speed	UltraSPARC (168 MHz)
JDK	Sun Java 2 JDK 5.0 with the Java HotSpot^TM Client and Server VMs (32-bit) and all later service packs of 5.0
RAM	1 GB minimum
Performance Pack	`server/native/solaris/sparc/libmuxer.so`
BEA Product Support	WebLogic Server 9.0 AquaLogic Service Bus 2.0
Design and Development Tools	BEA Workshop for WebLogic Platform 9.0: Not supported The AquaLogic Service Bus 2.0 Data Transformation Tools: Not supported.

Known Issues

Incorrect Port Numbers

BEA has discovered that some Solaris JVMs report an incorrect IP number. The reported IP number for the machine is the first number in the /etc/hosts file. Unfortunately, the first number in /etc/hosts is frequently 127.0.0.1, the standard loopback network address for the machine. This problem affects licenses, where a license is granted for a specific IP number.

This problem also occurs in a cluster in which 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 of the incorrect IP number.

To determine whether this problem exists on your Solaris system, 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.

Serial Version UID Mismatch

A Serial Version UID Mismatch Issue may be encountered if you deploy an application on a latest JVM, but compiled with an earlier JDK release.

Workaround: To be compatible with the serialization of previously compiled applications, modify the <BEA_HOME>/Weblogic90/common/bin/commEnv.sh file to include the following command:

JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0"

Alternatively, you can use the command line option:

export JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0"

Note: If you intend to deploy new applications with previously compiled applications, they must be recompiled as necessary to have the same Serial Version UID.

Known Issues for Other BEA Products

For more information about known issues with BEA products supported on this configuration, including available workarounds, see the appropriate Release Notes document.

Issues related to...	Are described in...
AquaLogic Service Bus	BEA AquaLogic Service Bus Release Notes: `http://download.oracle.com/docs/cd/E13171_01/alsb/docs20/relnotes/relnotes.html`
WebLogic Server	BEA WebLogic Server Known and Resolved Issues: `http://download.oracle.com/docs/cd/E13222_01/wls/docs90/issues/known_resolved.html`
Installation and configuration	BEA Products Installation and Configuration Release Notes: `http://download.oracle.com/docs/cd/E13179_01/common/docs90/relnotes/relnotes.html`