This script opens a new, small, floating window and puts TOC<name>.html and IX<name>.html files in it and sets a generic popup window code to enable the display of some viewlets in the WebLogic Platform Tour.
Skip navigation.
Product Documentation

dev2dev Home > dev2dev WebLogic Server > WebLogic Server 5.1 Documentation > Supported Configurations for WebLogic Server 5.1 > Sun Microsystems/Fujitsu SPARC with Solaris 2.6

Supported Configurations for WebLogic Server 5.1

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF  
Get
Adobe Reader

Sun Microsystems/Fujitsu SPARC with Solaris 2.6

 

General Information

 

Supported Releases

This section lists the releases supported for this platform. Unless otherwise noted, all service packs for each release are also supported.

 

Known JDK Issues

Problems with JDK 1.3 crashing

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.

JDK 1.2.2_06

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.

JDK 1.2.2_05a

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.

JDK 1.2.2

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.

JDK 1.2.1_04

You must disable aggressive inlining by the JIT with: export _JIT_ARGS=novinline

JDK 1.1.7_08a

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

Operating System

Solaris 2.6


Required OS Patches

None


CPU

UltraSPARC 168MHz or better


RAM

64 MB minimum


Disk Space

64 MB


Supported Client JVM

  • SunSoft SDK 1.3.1
    with Java HotSpotTM Client VM

  • SunSoft SDK 1.3.0
    JavaTM 2 SDK Runtime Environment, Standard Edition (build 1.3.0), with Java HotSpotTM Client VM (build 1.3.0, mixed mode)

  • JDK 1.2.2_09 (build Solaris_JDK_1.2.2_09, native threads, sunwjit)

  • JDK 1.2.2_07 (build Solaris_JDK_1.2.2_07, native threads, sunwjit)

  • SunSoft JDK 1.2.1_04
    See BEA recommendations at JDK 1.2.1_04.

  • SunSoft JDK 1.1.8_12

WebLogic 5.1 was certified with SunSoft SDK 1.3.1 and will support any service pack of SDK 1.3.1.

Supported Server JVM

  • SunSoft SDK 1.3.1
    with Java HotSpotTM Client VM

  • SunSoft SDK 1.3.0
    JavaTM 2 SDK Runtime Environment, Standard Edition (build 1.3.0), with Java HotSpotTM Client VM (build 1.3.0, mixed mode)

  • JDK 1.2.2_09 (build Solaris_JDK_1.2.2_09, native threads, sunwjit)

  • JDK 1.2.2_07 (build Solaris_JDK_1.2.2_07, native threads, sunwjit)

  • SunSoft JDK 1.1.8_12

WebLogic 5.1 was certified with SunSoft SDK 1.3.1 and will support any service pack of SDK 1.3.1.

Performance Pack

Included.


Node Manager

None.


Oracle jDriver

For this Oracle Server version:

Oracle 8.1.7

Requires Service Pack 10 or higher

These Oracle jDriver shared libraries are supported:

lib/solaris/oci817_8/libweblogicoci37.so

lib/solaris/oci817_8/libweblogicoxa37.so

NSAPI Plug-ins

For this plugin:

iPlanet 3.6

This shared library is supported:

weblogic/lib/solaris/libproxy.so

iPlanet 4.0

weblogic/lib/solaris/libproxy.so

iPlanet 4.1.x

weblogic/lib/solaris/libproxy.so

Sun One 6.0

WebLogic 5.1 Service Pack 11 and later

weblogic/lib/solaris/libproxy.so

Apache Plug-ins

For this Apache version:

1.3.x

These shared libraries are supported:

weblogic/lib/solaris/mod_wl.so

The mod_wl.so is a shared object for standard Apache (non EAPI).


weblogic/lib/solaris/mod_wl_ssl.so

The file mod_wl_ssl.so is used for Apache + SSL/EAPI installations (Stronghold, modssl etc). It is available beginning with WLS 5.1.0 Service Pack 4.


weblogic/lib/solaris/mod_wl_ssl_raven.so

For Apache+FastStart installations the mod_wl_ssl_raven.so is used.

The mod_wl_ssl_raven.so file was required because FastStart applies frontpage patches which makes it incompatible with mod_wl_ssl.so. It is available beginning with WLS 5.1.0 Service Pack 4)


 

 

Solaris Tunable Parameters

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.

Tuning Solaris File Descriptor Limits

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.

Viewing and Adjusting File Descriptor Limits

To view and adjust file descriptor limits:

  1. Use the ulimit command to print current resource limits.
    ulimit
  2. Set the hard limit value in /etc/system, according to your needs. For example:
    set rlim_fd_max=4096 /* hard limit */
  3. Restart WebLogic Server. A message similar to the following appears in the startup log:
    <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.>

Setting TCP Parameters with the ndd Command

Set the following TCP tuning parameters with the ndd command. Use the following syntax:

ndd -set driver parameter

For example:

ndd -set /dev/ip ip_ignore_redirect 1

Table 14-1 Suggested TCP Parameter Values

Parameter

Suggested Value

/dev/ip ip_ignore_redirect

1

/dev/tcp tcp_conn_grace_period

500

/dev/tcp tcp_conn_req_max_q

8096 (*)

/dev/tcp tcp_conn_req_max_q0

8096 (*)

/dev/tcp tcp_conn_req_min

1

/dev/tcp tcp_cwnd_max

65534

/dev/tcp tcp_fin_wait_2_flush_interval

16000

/dev/tcp tcp_ip_abort_cinterval

60000

/dev/tcp tcp_ip_abort_interval

60000

/dev/tcp tcp_keepalive_interval

90000

/dev/tcp tcp_recv_hiwat

32768

/dev/tcp tcp_rexmit_interval_initial

3000

/dev/tcp tcp_rexmit_interval_max

10000

/dev/tcp tcp_rexmit_interval_min

3000

/dev/tcp tcp_slow_start_initial

2

/dev/tcp tcp_time_wait_interval

60000 (**)

/dev/tcp tcp_xmit_hiwat

32768

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.

Viewing TCP Parameters with the netstat -sP tcp Command

Use netstat -sP tcp to view the following parameters:

Table 14-2 Viewable TCP Parameter Values

Parameter

Suggested Value

tcpActiveOpens

413995

tcpAttemptFails

15937

tcpCurrEstab

13

tcpEstabResets

621691

tcpHalfOpenDrop

0

tcpInAckBytes

4290207863

tcpInAckSegs

43347796

tcpInAckUnsent

0

tcpInClosed

1700

tcpInDupAck

1230270

tcpInDupBytes

12551831

tcpInDupSegs

7023

tcpInInorderBytes

3228433225

tcpInInorderSegs

42175934

tcpInPartDupBytes

4690354

tcpInPartDupSegs

7023

tcpInPastWinBytes

486243985

tcpInPastWinSegs

178

tcpInSegs

64462930

tcpInUnorderBytes

258926562

tcpInUnorderSegs

206376

tcpInWinProbe

7584

tcpInWinUpdate

2754

tcpListenDrop

123865

At run time, if tcpListenDrop is non-zero and increasing, use the ndd command to increase tcp_conn_req_max_q.

tcpListenDropQ0

0

If tcpListenDropQ0 is non-zero and increasing, use the ndd command to increase tcp_conn_req_max_q0.

tcpMaxConn

-1

tcpOutAck

12416786

tcpOutAckDelayed

3223013

tcpOutControl

4296229

tcpOutDataBytes

4290849539

tcpOutDataSegs

55577630

tcpOutFastRetrans

42726

tcpOutRsts

2735468

tcpOutSackRetrans

223

tcpOutSegs

68076290

tcpOutUrg

221

tcpOutWinProbe

4193

tcpOutWinUpdate

13576

tcpPassiveOpens

655052

tcpRetransBytes

148287157

tcpRetransSegs

242760

tcpRtoAlgorithm

4

tcpRtoMax

60000

tcpRtoMin

200

tcpRttNoUpdate

95781

tcpRttUpdate

42878526

tcpTimKeepalive

12798

tcpTimKeepaliveDrop

13

tcpTimKeepaliveProbe

2408

tcpTimRetrans

150215

tcpTimRetransDrop

526

Setting tcp_conn_hash_size Parameter in /etc/system

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

VM Parameters

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

http://java.sun.com/j2se/docs/VMOptions.html

 

Skip navigation bar  Back to Top Previous Next