Java Message Service Settings | Sun Microsystems 820434310 specs

Java Message Service Settings

than cache misses, then option B is an appropriate choice. You might still have to change the max-cache-size and cache-resize-quantity to get the best result.

If the cache hits are too low and cache misses are very high, then the application is not reusing the bean instances and hence increasing the cache size (using max-cache-size) will not help (assuming that the access pattern remains the same). In this case you might use commit option C. If there is no great difference between cache-hits and cache-misses then tune max-cache-size, and probably cache-idle-timeout-in-seconds.

Java Message Service Settings

The Type attribute that determines whether the Java Message Service (JMS) is on local or remote system affects performance. Local JMS performance is better than remote JMS performance. However, a remote cluster can provide failover capabilities and can be administrated together, so there may be other advantages of using remote JMS. For more information on using JMS, see Chapter 4, “Configuring Java Message Service Resources,” in Sun GlassFish Enterprise Server 2.1 Administration Guide.

Transaction Service Settings

The transaction manager makes it possible to commit and roll back distributed transactions.

A distributed transactional system writes transactional activity into transaction logs so that they can be recovered later. But writing transactional logs has some performance penalty.

Monitoring the Transaction Service

Transaction Manager monitoring is disabled by default. Enable monitoring of the transaction service with the Admin Console at Configurations > config-name> Monitoring.

You can also enable monitoring with these commands:

set serverInstance.transaction-service.monitoringEnabled=true

reconfig serverInstance

Viewing Monitoring Information

When you have enabled monitoring of the transaction service, view results

■With Admin Console at Standalone Instances > server-name(Monitor Monitor). Select transaction-servicefrom the View dropdown.

■With this command:

58	Sun GlassFish Enterprise Server 2.1 Performance Tuning Guide • January 2009

Image 58

Sun Microsystems 820434310 Java Message Service Settings, Transaction Service Settings, Monitoring the Transaction Service

Contents

Sun GlassFish Enterprise Server 2.1 Performance Tuning Guide Sun Microsystems, Inc Network Circle Santa Clara, CA 090304@21990 Contents Tuning the Enterprise Server 100 Tuning for High-Availability Figures Page Tables Page Examples Page Sun GlassFish Enterprise Server Documentation Set Table P-1Books in the Enterprise Server Documentation Set Default Paths and File Names Table P-2Default Paths and File Names Typographic Conventions Symbol ConventionsSymbol Conventions Table P-3Typographic Conventions Third-Party Web Site References Documentation, Support, and TrainingSun Welcomes Your Comments 1Performance Tuning Roadmap Process Overview Performance Tuning Sequence Performance Tuning Roadmap Understanding Operational Requirements Application Architecture Client-Side Presentation Security Requirements User Authentication and AuthorizationEncryption Hardware Resources General Tuning Concepts Administration Capacity Planning 2Factors That Affect Performance User Expectations To Determine Capacity Further Information Avoid Serialization and Deserialization Java Programming GuidelinesUse StringBuffer to Concatenate Strings Declare Methods as final Only If Necessary String str = testing str = str + abcAssign null to Variables That Are No Longer Needed Declare Constants as static final Declare Method Arguments final Java Server Page and Servlet TuningSynchronize Only When Necessary Use DataHandlers for Soap Attachments Avoid Shared Modified Class Variables Suggested Coding PracticesGeneral Guidelines Http Session Handling Disable Security Manager Configuration and Deployment TipsOptimize SSL Goals EJB Performance TuningMonitoring EJB Components Following is a sample of the monitoring output Asadmin get -m monitorableObject Monitoring Individual EJB Components Use High Performance Beans General GuidelinesUse Caching Use the Appropriate Stubs Using Local and Remote InterfacesCache and Pool Tuning Tips Remove Unneeded Stateful Session Beans Using Pass-By-Reference Semantics Prefer Local Interfaces Improving Performance of EJB Transactions Use the Least Expensive Transaction Attribute Using Special TechniquesConfigure Jdbc Resources as One-Phase Commit Resources Version Consistency Entity-mapping cmp-field-mapping Request Partitioning To enable request partitioningWhen new.VCVERSIONNUMBER = old.VCVERSIONNUMBER Declare Cmp-field-mapping consistency Entity Beans Tuning Tips for Specific Types of EJB ComponentsStateful Session Beans Stateless Session Beans Checkpoint only when neededRead-Only Entity Beans Pre-fetching Container Managed Relationship CMR Beans Refresh period OrderTable.OrderID = OrderLineTable.OrderLineOrderID Encapsulate Business Logic in Entity EJB Components Jdbc and Database AccessUse Jdbc Directly Close Connections Use getConnection Tuning Message-Driven BeansAsadmin set server.mdb-container.max-pool-size = value Tune the Message-Driven Bean’s Pool Size Cache Bean-Specific Resources Limit Use of JMS Connections Tuning the Enterprise Server Deployment Settings Disable Dynamic Application Reloading Logger SettingsDisable Auto-deployment Use Pre-compiled JavaServer Pages Session Properties Session Timeout Web Container SettingsGeneral Settings Log Levels Disable Dynamic JSP Reloading Manager Properties Reap Interval Monitoring the EJB Container EJB Container SettingsTuning the EJB Container Overview of EJB Pooling and Caching Tuning the EJB Pool EJB Pool Settings Tuning the EJB Cache EJB Cache Settings Pool and Cache Settings for Individual EJB Components Commit Option Determining the best commit option Monitoring the Transaction Service Java Message Service SettingsTransaction Service Settings Viewing Monitoring Information Disable Distributed Transaction Logging Tuning the Transaction ServiceAsadmin get -m serverInstance.transaction-service Recover On Restart Automatic Recovery Http Service SettingsMonitoring the Http Service Keypoint Interval Property name=statsProfilingEnabled value=false EnabledList --user admin --port DNS Cache Information dns Limit DNS Lookups to Asynchronous HitRatioCaching DNS Entries NameLookups File Cache Information file-cache Keep Alive keep-alive Connection Queue Tuning the Http ServiceAccess Log Request Processing Thread Count Request TimeoutInitial Thread Count Buffer Length Keep AliveMax Connections Http File Cache DNS Lookup EnabledHttp Protocol Time Out Max Age Max Files CountHash Init Size Small/Medium File Size and File Size Limit Network Address Tuning Http Listener SettingsAcceptor Threads How a Client Connects to the ORB ORB SettingsOverview Monitoring the ORB Connection Statistics Tuning the ORB3Tunable ORB Settings Thread Pools Tunable ORB Parameters ORB Thread Pool Parameters Client ORB Properties Using multiple connectionsControlling connections between client and server ORB Examining Iiop Messages Thread Pool SizingLoad Balancing Improving ORB Performance with Java Serialization To Enable Java Serialization Thread Pool SettingsTuning Thread Pools Unix /Linux only Using JSG for Application Clients Resources Jdbc Connection Pool SettingsTuning Jdbc Connection Pools Monitoring Jdbc Connection Pools Timeout Settings Pool Size Settings4Connection Pool Sizing Isolation Level Settings Connection Validation Settings Connector Connection Pool Settings Transaction Support Testpool Page Tuning the Java Runtime System Java Virtual Machine Settings Tuning the Garbage Collector Managing Memory and Garbage Collection To use the CMS collector Choosing the Garbage Collection AlgorithmAdditional Information Other Garbage Collector Settings Tracing Garbage Collection Guidelines for Java Heap Sizing Tuning the Java Heap1Maximum Address Space Per Process Heap Tuning Parameters Xmsvalue Xmxvalue Rebasing DLLs on Windows Example 4-1Heap Configuration on SolarisSurvivor Ratio Sizing Enter this command rebase -b 0x6000000 *.dll To rebase the Application Server’s DLLs For more information on tuning the JVM, see Page Server Scaling Processors Disk Space MemoryNetworking Tuning Parameters Ndd -get /dev/tcp tcpconnhash Sizing the Connection Hash TableNetstat -nP tcpwc -l Linux Configuration File Descriptor Setting Tuning for Solaris on File Descriptors on IP Stack Settings on IP Stack Settings File Descriptors Tuning for Linux platforms Soft Nofile 65535 Hard Virtual MemorySession required /lib/security/pamlimits.so To tune the TCP/IP settings Disk I/O SettingsTCP/IP Settings Network Interface Tuning UltraSPARC T1-Based Systems Tuning Operating System and TCP Settings 2Tuning 64-bit Systems for Performance Benchmarking Network Configuration Disk ConfigurationStart Options 106 Disk Use Tuning HadbCalculating Hadb Data Device Size Tuning Data Device Size Hadbm set TotalDatadeviceSizePerNode Beware last flush/fputs took too long Memory AllocationPlacing Hadb files on Physical Disks Vmstat -S DataBufferPoolSize PerformanceNodeNo TotalSize FreeSize Usage 512 504 LogBufferSize Tuning DataBufferPoolSizeHadbm set DataBufferPoolSize Hadbm resourceinfo --logbuf Tuning LogBufferSizeInternalLogbufferSize Node No Avail Free Size Hadbm resourceinfo --nilogbuf Tuning InternalLogbufferSizeNumberOfLocks Hadbm set InternalLogbufferSize Calculating the number of locks Tuning NumberOfLocksSummary Load Balancer timeouts TimeoutsJdbc connection pool timeouts Node No Avail Free Waits 50000 Hadb timeouts Tuning the Enterprise Server for High-AvailabilityOperating System Configuration No space left on device Web-method Tuning Session Persistence FrequencyTime-based Session Session Persistence ScopeSession Size Modified-session Configuring the Jdbc Connection Pool Checkpointing Stateful Session Beans Configuring the Load Balancer Enabling the Health Checker Tuning for High-Availability 121 122 Index Index 125 Monitoring transaction service Session timeout 128