Supported Configurations for WebLogic Server 5.1
![]() |
![]() |
![]() |
![]() |
![]() |
Get Adobe Reader |
export _JVM_ARGS="inline_instrs_jit=0"
directive.This is due to Sun's bugs: #4333396 (JVM crash during JIT) and #4333696. The error message reads: SIGABRT and JIT coredump: panic: Unexpected operand kind(10) in j86OpndImage
. These also affect 1.2.1_04, so that you must Disable aggressive inlining by the jit with: export _JIT_ARGS=novinline
. /etc/hosts
file, which, unfortunately, 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. 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 of the incorrect IP number. You can run the command java utils.netAddresses
to see if you have this problem on your Solaris computer. 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.
This section lists the releases supported for this platform. Unless otherwise noted, all service packs for each release are also supported.
If you have problems with OutOfMemory errors and the JVM crashing with JDK 1.3, try setting: -XX:MaxPermSize=128m. There is currently an open bug on Sun's bug parade that describes this problem. See http://developer.java.sun.com/developer/bugParade/bugs/4390238.html.
BEA recommends using the 1.2.2_05a version with the directive export _JVM_ARGS="inline_instrs_jit=0
". This will disable aggressive inlining by the JIT while allowing it to perform other performance enhancing tasks. The 1.2.2_05a version has been supported by BEA. There is a known garbage collection related deadlock condition, bug #4351991, with JDK 1.2.2_06. If you wish to use the 1.2.2_06 version, emergency relief that fixes bug #4351991 will be available through Sun, up until the release of 1.2.2_07 or the full BEA qualification of a later Sun JDK. Please contact your Sun support representative with any questions regarding this relief.
BEA recommends using the 1.2.2_05a version with the directive export _JVM_ARGS="inline_instrs_jit=0"
.This disables aggressive inlining by the JIT while allowing it to perform other performance enhancing tasks.
The wrapper script for the Solaris JDK 1.2.2 ignores the value of $THREADS_FLAG
and defaults to using green threads unless you supply the -native option. WebLogic Server is not supported with green threads. Please specify the -native
option on all of your java commands.
You must disable aggressive inlining by the JIT with: export _JIT_ARGS=novinline
Bug ID 4134584 in Sun's Bug Parade, describes a bug in JDK 1.1.7 on Solaris. This bug will occasionally cause a server crash with the error "*** panic: 16-bit string hash table overflow"
. Because of this, we recommend that you use JDK 1.2 on Solaris.)
|
WebLogic 5.1 was certified with SunSoft SDK 1.3.1 and will support any service pack of SDK 1.3.1. |
|
|
WebLogic 5.1 was certified with SunSoft SDK 1.3.1 and will support any service pack of SDK 1.3.1. |
|
These Oracle jDriver shared libraries are supported: |
||
These shared libraries are supported:
The
The file
For Apache+FastStart installations the The |
Warning: Do not modify these parameters before first consulting your Solaris Administrator.
This section presents suggested values for some Solaris TCP and VM-related tunable parameters.
For more information about Solaris configuration, see the Solaris FAQ: http://www.science.uva.nl/pub/solaris/solaris2/index.html.
On Solaris, each user account has a certain limited number of file descriptors. Use the ulimit
command to print or set resource limits. A resource limit is a pair of values that specify the current (soft) limit and the maximum (hard) limit. You can modify the hard limit in /etc/system
. You must reboot your machine anytime you modify /etc/system
.
Note: Do not change the default soft limit. It has the potential to affect many processes on the server and will not affect WebLogic Server.
You must have adequate permissions to use the ulimit
command. Any user may lower a hard limit. Only a super-user may raise a hard limit.
To view and adjust file descriptor limits:
set rlim_fd_max=4096 /* hard limit */
<Jul 30, 2001 9:16:11 AM EDT> <Info> <Posix Performance Pack> <System has file descriptor limits of - soft: '256', hard: '4096'>
<Jul 30, 2001 9:16:11 AM EDT> <Info> <Posix Performance Pack> <Using effective file descriptor limit of: '4096' open sockets/files.>
Set the following TCP tuning parameters with the ndd command. Use the following syntax:
ndd -set driver parameter
ndd -set /dev/ip ip_ignore_redirect 1
Set parameters followed with an asterisk based on the number of concurrent connections against the web server.
For Solaris 2.6, tcp_time_wait_interval
has changed to:
ndd -set /dev/tcp tcp_close_wait_interval 60000
The tcp_close_wait_interval
parameter determines the time interval that a TCP socket is kept alive after issuing a close call. The default value of this parameter on Solaris is four minutes. When a large number of clients connect for a short amount of time, holding these socket resources can have a significant negative impact on performance. Setting this parameter to a value of 60000 (60 seconds) has shown a significant throughput enhancement when running benchmark JSP tests on Solaris.
You might want to reduce this setting further if the server gets backed up with a queue of half-opened connections.
Use netstat -sP tcp
to view the following parameters:
You must reboot your machine anytime you modify /etc/system
parameters. Set the value of the tcp_conn_hash_size
parameter in the /etc/system
file:
set tcp:tcp_conn_hash_size=8192
On JDK 1.2.2_05a, set the following parameter in the java command line:
java <other command line options>
-Xgenconfig:64m,64m,semispaces:64m,512m,markcompact weblogic.Server
See also "Tuning Java Virtual Machines" in the BEA WebLogic Server Performance and Tuning guide:
For a detailed explanation of the JDK 1.3 VM, see:
http://java.sun.com/j2se/docs/PerformanceFAQ.html
![]() ![]() |
![]() |
![]() |