I think Dell has had a similar impact on other computer vendors in the same server market because Dell was one of the first to come to customizable computers, so all other vendors have been hit with the same power of Sun Microsystems. Sun's supply chain now closely reflects Dell's PC series. Both are shorter.

Supported Configurations for WebLogic Server 5.1

• Is a leading provider of refurbished and used server, networking, and storage-related enterprise level equipment. We offer a large selection of used IBM, Sun Microsystems, HP/Compaq, Dell, and Cisco products and offer some of the best pricing in North America.
• FCC ID GWV415CPU GWV-415CPU, GWV 415CPU, GWV415CPU, GWV4I5CPU, GWV41SCPU Sun Microsystems Inc Desktop Computer 415CPU.
• According to Bloomberg the co-founder of Sun Microsystems purchased the beachfront property in 2008 and put up a gate to close the beach soon after the purchase. As per the 151-page petition, Khosla asks the highest court of the land to allow him to exercise his property rights.

• To download supported releases for this platform, see Download WebLogic Server for Your Platform.
• WebLogic supports Sun Solaris on Sun Microsystems/Fujitsu SPARC computers. For information on Solaris, see Sun's Solaris web page.
• For Sun's support services info 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 JavaSoft. BEA recommends using the latest BEA supported version of the JVM's available, except where noted on our Supported Configurations document.
• The JIT (Just-In-Time) Compiler is only supported for 1.2.2_05a while using the 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.
• 7.3.4 jDriver for Oracle is not supported with JDK 1.3.1.
• We have encountered a problem where some Solaris JVMs report an incorrect IP number. The reported IP number for the machine is the first number in the /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.
• For information on suggested values for some Solaris TCP and VM-related tunable parameters, see Solaris Tunable Parameters

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

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

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:

Use the ulimit command to print current resource limits.
ulimit
Set the hard limit value in /etc/system, according to your needs. For example:
set rlim_fd_max=4096 /* hard limit */
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:

For example:

Table 15-1 Suggested TCP Parameter Values

Set parameters followed with an asterisk based on the number of concurrent connections against the web server.

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 15-2 Viewable TCP Parameter Values

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:

VM Parameters

On JDK 1.2.2_05a, set the following parameter in the java command line:

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:

Sun Microsystems Laptops & Desktops Drivers

The Ultra 24 is a family of computer workstations by Sun Microsystems based on the Intel Core 2 processor.

The Sun Ultra 24 launched in 2007, and ships with Solaris 10 pre-installed. Other than Solaris, it is officially compatible with various flavours of Linux as well as Microsoft's Windows XP and Windows Vista.^[1]

Sun Microsystems Site

Features[edit]

• CPU: one Intel Core 2 processor, 2.0 GHz or higher:
  • Intel Core 2 Duo processor
  • Intel Core 2 Quad processor
  • Intel Core 2 Extreme processor^[2]
• Memory—ECC unbuffered DDR2-667 DIMMs, 4 DIMM slots, 8 GB maximum. Three DIMM sizes, 512 MB, 1 GB, and 2 GB
• Networking—Single Gigabit Ethernet integrated on motherboard, one RJ-45 port (rear)
• Hard Disk Drives—Up to four internal drives:
  • either up to four SATA drives, 3TB maximum: 250GB, 750GB (7,200 rpm)
  • or, with optional PCIe SASHBA: Up to four SAS drives, 1.2TB maximum: 146GB, 300GB (15,000 rpm)
• Graphics: provided by a PCIe card
• PCI Express Slots:
  • Two full-length x16 Gen-2 slots
  • One full-length x8 slot (Electrically x4)
  • One full-length x1 slot

References[edit]

Sun Microsystems Os

1. ^http://www.oracle.com/us/products/servers-storage/desktop-workstations/036092.pdf
2. ^'HCL for Oracle Solaris OS (Solaris 10 1/13, Ultra 24)'. 11 Oct 2007. Retrieved 2 September 2017.

External links[edit]

Sun Microsystems Stock

• System Specifications on the Oracle documentation website

See also[edit]

• Sun Ultra series: various Sun workstations and servers using SPARC, AMD or Intel processors.

Sun Microsystems Download Center