 Print-friendly Version
Deploying JBoss Application Server on Sun Fire T2000 ServersViet Pham (Sun Microsystems) and Phillip Thurmond (JBoss), April 2007 Contents
IntroductionThis document serves as a starting point for the deployment of the JBoss Application Server (JBoss AS) on Sun Fire T2000 server systems. Since general documents about JBoss AS and the Sun Fire T2000 server already exist, only links to those documents will be provided. The rest of this document provides tuning recommendations specific to JBoss AS on the Sun Fire T2000 server. JBoss AS is a Java 2 Platform, Enterprise Edition (J2EE) certified platform for developing and deploying enterprise Java applications, web applications, and portals. JBoss AS provides the full range of J2EE 1.4 features as well as extended enterprise services, including clustering, caching, and persistence. Sun Fire T2000 Server Introduction Here is an excerpt of sun.com's description of the Sun Fire T2000 server:
For more information on the Sun Fire T2000 server, including benchmarks and the SwaP (Space, Watts and Performance) metric, see sun.com. Deployment TasksJBoss AS Installation Instructions One of the strengths offered by JBoss AS is its ease of installation. To install JBoss AS, do the following: 1. Download the latest revision at http://labs.jboss.com/portal/jbossas/download. JBoss AS is distributed in the form of a 2. Unzip the distribution to the desired location. Recommended installation directories are
root@host# unzip jboss-4.0.4.GA.zip That's it! You should now have a directory called JBoss AS Configuration Instructions JBoss AS stores its configuration under
After you have chosen the configuration you will be using, you should probably make a working copy of it where you can make your changes. # cp -r default myconfig Now you can use the command Another of the strengths that JBoss AS can offer is the extensive number of possible configurations. Because every feature in JBoss AS is a pluggable module, you can remove or add features as needed. For advanced configuration, see the JBoss Application Server Guide at http://labs.jboss.com/portal/jbossas/docs. PerformancePlease make sure the following parameters are set in set pcie:pcie_aer_ce_mask=0x1 set segmap_percent=60 set smallfile=1572864 set maxpgio=128 set rlim_fd_max=260000 set rlim_fd_cur=260000 set shmsys:shminfo_shmax=0xffffffff set tune_t_fsflushr = 1 set autoup = 60 set sq_max_size = 10000 set ip:ip_squeue_bind = 0 Note: These tuning settings might not be optimal if the system is shared by other applications. Please run the following commands to tune TCP on client systems: ndd -set /dev/tcp tcp_smallest_anon_port 2048 ndd -set /dev/tcp tcp_max_buf 8388608 ndd -set /dev/tcp tcp_recv_hiwat 131072 Interrupt Coalescence Tuning on the Sun Fire T2000 Server Please run the following command in a shell to force the server to use only virtual CPUs 29, 30, and 31 for interrupts. (Note: Type the command all on one line.) psradm -i 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Afterwards, only virtual CPUs 29, 30, and 31 serve the interrupts. Please use the following script to tune the network port on the Sun Fire T2000 server:
#!/bin/bash
INSTS="0 1 2 3"
NIC=ipge
for port in $INSTS ; do
ndd -set /dev/$NIC instance $port
ndd -set /dev/$NIC rx_intr_pkts 600
ndd -set /dev/$NIC rx_intr_time 600
done
Tuning Considerations for JBoss AS Because J2EE applications are so diverse, a tuning that works very well for one application might not work so well for another. There are, however, some basic changes you can make that will have benefits in almost any situation. Java Virtual Machine (JVM) options: Edit JAVA_OPTS="-server -Xms2650m -Xmx2650m -Xss128k -verbosegc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+DisableExplicitGC -XX:+UseParallelGC -XX:ParallelGCThreads=8 -XX:LargePageSizeInBytes=256m" Tomcat options: Edit JBoss options: On Sun Fire T2000 Server systems, it's recommended that you run JBoss AS in the
FX class using the following command. You will need root privileges to execute /usr/bin/priocntl -e -c FX ./run.sh <jboss options> Check out http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossASTuningSliming for more tuning and slimming options. Advanced DeploymentsJBoss AS has been tested and certified inside non-global zones in the Solaris OS. Because non-global zones behave almost identically to a normal Solaris system, no JBoss AS configuration changes need to be made to take advantage of Solaris zones. Simply copy the JBoss AS installation to the zone. You can then start JBoss AS from inside the zone as usual. As you increase the load on your server, you will likely run into some resource
limits. JBoss AS has many resource pools that can be tuned according to your application
needs. The Tomcat thread pool was discussed previously, but there are also many
internal pools, for Message Driven Beans (MDB), for example. Many of these can be found in the configuration
file If you have saturated the CPU on one server, you can continue to scale up using clustering.
Simply use the JBoss AS offers several options for monitoring. Here are the most common.
Also included is a small tool called Generally, JBoss AS doesn't require any special network configuration. By default,
JBoss AS binds to all local interfaces. If you would like to bind to a specific interface,
you should use the ContactsViet Pham can be reached at viet.pham@sun.com. Another contact at Sun Microsystems is Robert Lor, who can be reached at robert.lor@sun.com. At JBoss, Phillip Thurmond can be contacted at phillip.thurmond@jboss.com. References
Unless otherwise licensed, code in all technical manuals herein (including articles, FAQs, samples) is provided under this License. |
 |
 | |