The PSAPPSRV server process performs the functional requests, such as building and loading panel groups. It also provides the in-memory-caching feature for PeopleTools objects on the application server. Each server process maintains its own cache.
Enter the minimum number of application server instances that start when you boot the domain. There's always at least this number of instances running. This translates to the PSAPPSRV server's -m (min) parameter in the UBB file.
Enter the maximum number of server instances that can be started. This translates to the PSAPPSRV server's -M (Max) parameter in the UBB file.
Enter the number of seconds that a PSAPPSRV waits for a service request, such as MgrGetObj or PprLoad, to complete before timing out. Service timeouts are recorded in the TUXLOG and APPSRV.LOG. In the event of a timeout, PSAPPSRV is terminated and a replacement process is started by Tuxedo.
Enter the number of service requests that each server has carried out before being terminated (intentionally) and then immediately restarting. Servers must be intermittently recycled to clear buffer areas. The time that is required to recycle a server is negligible, occurring in milliseconds. The recycle count does not translate into a native Tuxedo parameter in the PSAPPSRV.UBB file. Instead, the value is stored in memory and is managed by a PeopleSoft server.
Note: The default value for the small, medium, and large templates is 10,000.
Note: Serial Recycle or Dynamic Recycle parameters can delay the recycle even if the number of the requests is greater than or equal to the Recycle Count value.
Percentage of Memory Growth
The Percentage of Memory Growth option, enables you to perform dynamic recycling, in a test environment, so that you can arrive at a static Recycle Count value suited to your production system. The Percentage of Memory Growth parameter indicates the percentage of memory growth to reach before the PSAPPSRV process will automatically restart (dynamically recycle). The default is 20, meaning an additional 20% of memory growth will be incurred after the process has established a baseline memory cache.
A dynamic recycling configuration is intended to be used in testing environment where a usage load, representative of your production usage load, can be run against a system. During this load test, administrators can monitor log files to determine when the dynamic recycle occurs. The intervals and trends related to the dynamic recycling can help to identify an appropriate Recycle Count value for a production environment. When the load test is complete, the Recycle Count value should be adjusted appropriately, and the dynamic recycle feature should be disabled.
When dynamic recycling is configured, the system evaluates the memory size after every 100 service requests to determine if the process needs to be recycled. If any new PeopleTools objects have been loaded into the memory cache, or if a JVM has been initialized since the last memory evaluation, the memory baseline is reset to the current value and no recycling will occur.
If no PeopleTools objects have been loaded, and if the JVM has not been initialized since the last memory evaluation, and if the memory footprint has grown by more than the specified percentage, the system recycles the PSAPPSRV process and adds messages to the APPSRV_xxyy.log file.
Note: Due to the overhead involved in measuring the memory usage, dynamic recycling is not recommended for use in a production environment.
Note: Unless you can emulate, in your test environment, a usage load representative of a typical production usage load, the results of your test will be of little value for determining the optimal Recycle Count value.
Configuring Dynamic Recycling
To configure dynamic recycling:
In the PSAPPSRV section, set Recycle Count to 0 to disable the fixed recycle interval.
Uncomment the Percentage of Memory Growth parameter, and adjust the value as needed to a value between 1–100, where 100 = 100%.
Percentage of Memory Growth=20
Restart the domain.
Viewing Logs for Dynamic Recycle Count Information
Recycle messages are logged with the service count indicated at that point. The system logs messages based on the following scenarios:
Memory Evaluation Scenario
Memory could not be determined.
Use Recycle Count for recycling due to unable to obtain virtual memory size
In this case, the message is logged at the "Status Level". This message appears at LogFence=3.
The current service count is less than the Recycle Count, although the memory usage exceeds the Percentage of Memory Growth value.
This indicates that the Recycle Count was set to a value other than 0. Should this condition occur, the system logs this message:
delay dynamic recycle(services=100, Recycle Count=500)
At intervals of 100 and if the LogFence is set to at least 4.
dynamic recycle results [ recycle=true, orig_mem=1000000, current_mem=2000000, max_mem=3000000, check_count=100, obj_loaded=100, jvm_loaded=true ]
Allowed Consec Service Failures
Enter a number greater than 0 to enable dynamic server processes to restart for service failures. To disable this option, enter 0. The default is 2. The value that you enter is the number of consecutive service failures that will cause a recycle of the server process. This is a catchall error handling routine that enables PSAPPSRV, PSQCKSRV, and PSAMSRV to terminate themselves if they receive multiple, consecutive, fatal error messages from service routines. Such errors should not occur consecutively, but if they do, the server process must be recycled or cleansed. A retry message appears on the client browser when this occurs.
Max Fetch Size
The default is 5000 (K). Enter the maximum memory that is used by the server to store fetched rows for a transaction before sending the result set back to a client. If the memory limit is exceeded, the client receives the rows retrieved with a memory buffer exceeded warning. You should use the default value. PSAPPSRV supports nonconversational transactions, so this parameter provides a way to balance high-volume throughput with the needs of users working with large volumes of data. A value of 0 means unlimited memory is used. The memory is not preallocated—it is acquired as needed for each transaction.
Auto Select Prompts
Enter 1 (the default) to enable automatic prompting on lookup pages. When the user selects the prompt lookup button, the application server automatically returns all values for that field, up to 300 rows. If necessary, the user can refine the search further by entering partial data in the Search By field.
Enter 0 to require the user to enter a partial value before the automatic prompt list appears.
You can add this parameter, if needed, manually to the [PSAPPSRV] section of the PSAPPSRV.CFG file. AutoLoad JVM controls whether the JVM gets loaded automatically when the domain boots.
By default, domain behavior reflects a setting of AutoLoad JVM=0 (not enabled).
If you have configured EnablePPM Agent=1, then JVM will be loaded at the domain boot time. If you have configured EnablePPM Agent=0, then to load JVM when the domain boots, you need add AutoLoad JVM=1 to the [PSAPPSRV] section of the PSAPPSRV.CFG file.
When serial recycling is enabled for a server process, the system recycles server processes of that type within a domain on a serial basis–one after another–to allow processing to continue uninterrupted. By default, the domain behavior reflects Serial Recycle=Y (enabled).
When Serial Recycle=Y for PSAPPSRV, for example, then only one PSAPPSRV process will recycle during the recycle time of 60 seconds when the Recycle Count limit is reached. Then the next PSAPPSRV will recycle.
When serial recycling is not enabled, all the server processes of that type recycle simultaneously when the Recycle Count limit is reached, which can cause throughput to pause.
Serial recycling applies to these server process types: PSAPPSRV, PSQCKSRV, PSQRYSRV, and the Integration Broker server processes.
To disable serial recycling, manually add the Serial Recycle parameter, and assign the value N. For example:
The recycle time is 60 seconds.