This page (revision-23) was last changed on 26-Nov-2021 10:22 by ibarr

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
23 26-Nov-2021 10:22 8 KB ibarr to previous
22 26-Nov-2021 10:22 8 KB rforbes to previous | to last
21 26-Nov-2021 10:22 8 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
SOFTWARE_INSTALLATION.TROUBLESHOOTING
SOFTWARE_INSTALLATION.TROUBLESHOOTING

Version management

Difference between version and

At line 3 changed one line
Personality Professional and Self-Service utilizes various components of the Oracle Application Server. Therefore, it is important to know where the logs files are stored for each component before proceeding any further.
[{$applicationname}] Professional and Self-Service utilizes various components of the Oracle Application Server. Therefore, it is important to know where the logs files are stored for each component before proceeding any further.
At line 5 changed one line
!Oracle HTTP Server Logs
!Oracle HTTP Server Logs:
At line 9 changed one line
!J2ee Application Logs
!J2ee Application Logs:
At line 13 changed one line
!OPMN Logs
!OPMN Logs:
At line 19 changed one line
;Problem:There is an attempt to run a report in Personality and a red bar is automatically encountered, indicating the report has failed.
;Problem:There is an attempt to run a report in [{$applicationname}] and a red bar is automatically encountered, indicating the report has failed.
At line 29 changed one line
!!Unable to View Report After Running It
!!Unable to view report after running it.
At line 34 changed one line
!!Unable to Write or Read from Extract or Load Folder
!!Unable to write or read from extract or load folder.
At line 39 changed one line
!!Self Service Tuning Tips
!!Self Service Tuning Tips:
At line 42 changed one line
#Does your server meet the minimum requirements for the number of users and more importantly, does it have sufficient resources to scale when the load increases. Please reference the 'Personality Operating Environment’ for more information on the minimum requirements.
#Does your server meet the minimum requirements for the number of users and more importantly, does it have sufficient resources to scale when the load increases. Please reference the '[{$applicationname}] Operating Environment’ for more information on the minimum requirements.
At line 44 changed 2 lines
!Configuring the Number of Concurrent Self Service Users
The assumption is made that 500 users will be accessing Self Service currently and that Self Service is deployed separately from Personality. The below configurations changes are based on this fact.
!Configuring the Number of Concurrent Self Service Users:
The assumption is made that 500 users will be accessing Self Service currently and self Service is deployed separately from [{$applicationname}]. The below configurations changes are based on this fact.
At line 47 changed one line
When a Self Service user connects, the first component it communicates with is the HTTP Web server. Therefore, the first component to tune is the HTTP Server. Open the httpd.conf file from the ''ORACLE_HOME\Apache\Apache\conf\'' directory.
When a Self Service user connects, the first component it communicates with is the HTTP Web server. Therefore, the first component to tune is the HTTP Server. Open the httpd.conf file from the ORACLE_HOME\Apache\Apache\conf\ directory
At line 49 changed one line
;(MS Windows Only) MaxRequestsPerChild:This is the number of concurrent requests the server will allow. As noted, we are tuning Self Service to support 500 current users. Therefore, we can set this parameter to approximately 520 to facilitate the number of user plus any additional overhead.
;(MS Windows Only) MaxRequestsPerChild: Number of concurrent requests the server will allow. As noted, we are tuning Self Service to support 500 current users. Therefore, we can set this parameter to approximately 520 to facilitate the number of user plus any additional overhead.
At line 51 changed one line
;(UNIX/Linux Only) MaxClients:This is similar to MaxRequestPerChild.
;(UNIX/Linux Only) MaxClients: Similar to MaxRequestPerChild.
At line 53 changed 5 lines
!Tuning the JVM
For starters, the java options below should be used:
;(-Xms# and –Xmx#):Initial and maximum heap parameters. To reduce the overhead required by the JVM to manage the heap, it is suggested setting these two parameters to the same value.
;(-XX:MaxPermSize ):The permanent generation is used to store and load java classes needed by the application. The default value of 64MB is not adequate. Increasing this parameter to 256 will avoid the ''java.lang.OutOfMemoryError: PermGen'' space error message.
;(-Xrs) MS Windows Only:All OC4J should be configured with this option to avoid random disconnects from the application. On a Windows platform there are occasions when the administrator logs on/off the console and the JVM does not handle it correctly resulting in the termination of the JVM process.
!Tuning the JVM:
For starters the below java options should be used.
*(-Xms# and –Xmx#) initial and maximum heap parameters. To reduce the overhead required by the JVM to manage the heap, we suggest setting these two parameters to the same value
*(-XX:MaxPermSize ) The permanent generation is used to store and load java classes needed by the application. The default value of 64MB is not adequate. Increasing this parameter to 256 will avoid the ‘java.lang.OutOfMemoryError: PermGen space error message.
*(-Xrs) MS Windows Only. All OC4J should be configured with this option to avoid random disconnects from the application. On a Windows platform there are occasions when the administrator logs on/off the console and the JVM does not handle it correctly resulting in the termination of the JVM process.
At line 59 changed one line
If you have implemented the above java options and you are still encountering performance issue and if further, you suspect the application server is where the problem lies, the below steps can be used to isolate the problem.
If you have implemented the above java options and you are still encountering performance issue – further, you suspect the application server is where the problem lies, the below steps can be used to isolate the problem.
*(-verbose:gc) enable this startup java option will allow you to analyze the Garbage Collector, for example:
At line 61 changed one line
(-verbose:gc) Enable this startup java option will allow you to analyze the Garbage Collector, for example:\\[SOFTWARE_INSTALLATION.TROUBLESHOOTING_01.JPG]
[GC 66693K->60776K(88216K), 0.0128313 secs]
At line 63 changed 4 lines
*From the above example, there is a minor collection and one full collection.
*The GC 66693K->60776K is the combined size of live objects before and after garbage collection respectively.
*The 88216K is the total available space – in other words to total heap.
*The 0.0128313 secs is the amount of time it took to perform a minor collection.
[Full GC 60776K->49550K(88216K), 0.2769277 secs]
At line 66 added 8 lines
From the above example, there is a minor collection and one full collection.
The GC 66693K->60776K is the combined size of live objects before and after garbage collection respectively.
The 88216K is the total available space – in other words to total heap.
The 0.0128313 secs] is the amount of time it took to perform a minor collection.
At line 70 changed one line
There are a number of tuning options available to assist with performance related issues. Here are a few of those options, for a complete list of all the java options, please refer to the [Java Virtual Machine Garbage Collection Tuning|http://www.oracle.com/technetwork/java/javase/gc-tuning-6-140523.html|target="_blank"] document.
There are a number of tuning options available to assist with performance related issues. Here are a few of those options, for a complete list of all the java options, please refer to the Java Virtual Machine Garbage Collection Tuning document.
At line 72 changed one line
__(-XX:+UseParallelGC -XX:ParallelGCThreads=2)__\\The parallel collector is the default collector on server class machines. Increase the parallel GC threads to match the CPU count. The above example implies the server has two CPUs.
*(-XX:+UseParallelGC -XX:ParallelGCThreads=2)
At line 74 changed one line
__(-XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode)__\\The above options will enable the concurrent collector. The concurrent collector will shorten pause times by sharing processor resources with the garbage collector while the application is running. This option should only be used on server class machine that have more than 2 CPUs.
The parallel collector is the default collector on server class machines. Increase the parallel GC threads to match the CPU count. The above example implies the server has two CPUs
At line 76 changed 2 lines
!Self-Service Timeout
The timeout setting for Self-Service will have a negative impact on performance if it is not configured correctly. By default, the web server sessions will remain for 30 minutes before they're removed. If the server has limited resources this can be an area where resources can be reclaimed.
*(-XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode)
At line 79 changed one line
*([SS_APP_TIMEOUT|SS APP TIMEOUT(System_Preference)] preference) The timeout value can be set to 5 minutes.
The above options will enable the concurrent collector. The concurrent collector will shorten pause times by sharing processor resources with the garbage collector while the application is running. This option should only be used on server class machine that have more than 2 CPUs
At line 81 changed one line
*(ORION-WEB-XML) The timeout value can be set to 6 minutes.
!Self-Service Timeout:
The timeout setting for Self-Service will have a negative impact on performance if it is not configured correctly. By default the web server sessions will remain for 30 minutes before there removed. If the server has limited resources this can be an area where resources can be reclaimed.
At line 89 added 4 lines
*(SS_APP_TIMEOUT preference) the timeout value can be set to 5 minutes
*(ORION-WEB-XML) the timeout value can be set to 6 minutes
At line 85 changed one line
*(SS_AJAX_TIMEOUT preference) By default, an Ajax request must be completed within 25 seconds. If the request cannot be completed within the allotted time, then an Ajax request timed out error message will be encountered. The time required to complete an Ajax request will vary during normal and peak usage and will be different for every client. Testing will be required in order to determine the appropriate value for your site.
*(SS_AJAX_TIMEOUT preference) By default an Ajax request must be completed within 25 seconds. If the request cannot be completed within the allotted time then an Ajax request timed out error message will be encountered. The time required to complete an Ajax request will vary during normal and peak usage and will be different for every client – to determine the appropriate value for your site will require testing.
At line 87 changed 2 lines
!!Personality
The performance of Personality is heavily dependent of the size of the heap and the garbage collector utilized. Please review the above section on [Tuning JVM Options|SOFTWARE_INSTALLATION.TROUBLESHOOTING#TuningTheJVM].
!![{$applicationname}]
The performance of [{$applicationname}] is heavily dependent of the size of the heap and the garbage collector utilized. Please review the above section -tuning JVM options:
At line 90 changed one line
A new site preference has been introduced, [DB_PRCSS_THREADS|DB PRCSS THREADS(System_Preference)], which will allow specific update functions to run as a multi-threaded process. In other words the functions will be able to take advantage of multiple processors.
High Lines has introduced a new site preference, DB_PRCSS_THREADS which will allow specific update functions to run as a multi-threaded process –in other words the functions will be able to take advantage of multiple processors.
At line 92 changed 5 lines
The below list of functions can utilize the [DB_PRCSS_THREADS|DB PRCSS THREADS(System_Preference)]:
\\[UPCALC]
\\[UPUNDO]
\\[UTTP]
\\[UEGTS]
The below list of functions can utilize the DB_PROCSS_THREADS:
[UPCALC]
[UPUNDO]
[UTTP]
At line 98 removed 4 lines
\\
%%commentbox
[Prev page|WIKI.INSTALLATION] - [Next Page|SOFTWARE_INSTALLATION.GO_LIVE_CONFIGURATION]
%%
This page (revision-23) was last changed on 26-Nov-2021 10:22 by ibarrTop