Sun Microsystems 820434310 manual

ORB Settings

++++++++++++++++++++++++++++++

Message(Thread[ORB Client-side Reader, conn to 192.18.80.118:1050,5,main]): createFromStream: type is 4 <

MessageBase(Thread[ORB Client-side Reader, conn to 192.18.80.118:1050,5,main]): Message GIOP version: 1.2

MessageBase(Thread[ORB Client-side Reader, conn to 192.18.80.118:1050,5,main]): ORB Max GIOP Version: 1.2

Message(Thread[ORB Client-side Reader, conn to 192.18.80.118:1050,5,main]): createFromStream: message construction complete.

com.sun.corba.ee.internal.iiop.MessageMediator

(Thread[ORB Client-side Reader, conn to 192.18.80.118:1050,5,main]): Received message:

----- Input Buffer -----

Current index: 0

Total length : 340

47 49 4f 50 01 02 00 04 0 0 00 01 48 00 00 00 05 GIOP.......H....

Note – The flag -Dcom.sun.CORBA.ORBdebug=giop generates many debug messages in the logs. This is used only when you suspect message fragmentation.

In this sample output above, the createFromStream type is shown as 4. This implies that the message is a fragment of a bigger message. To avoid fragmented messages, increase the fragment size. Larger fragments mean that messages are sent as one unit and not as fragments, saving the overhead of multiple messages and corresponding processing at the receiving end to piece the messages together.

If most messages being sent in the application are fragmented, increasing the fragment size is likely to improve efficiency. On the other hand, if only a few messages are fragmented, it might be more efficient to have a lower fragment size that requires smaller buffers for writing messages.

Improving ORB Performance with Java Serialization

It is possible to improve ORB performance by using Java Serialization instead of standard Common Data Representation (CDR) for data for transport over the network. This capability is called Java Serialization over GIOP (General Inter-ORB Protocol), or JSG.

In some cases, JSG can provide better performance throughput than CDR. The performance differences depend highly on the application. Applications with remote objects having small amounts data transmitted between client and server will most often perform better using JSG.

Chapter 3 • Tuning the Enterprise Server

75

Image 75

Sun Microsystems 820434310 manual Improving ORB Performance with Java Serialization

Contents

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