[JBoss JIRA] Created: (RF-5383) memory leakage issues during the load testing on rich faces version 3.2
by jFoundation java (JIRA)
memory leakage issues during the load testing on rich faces version 3.2
-----------------------------------------------------------------------
Key: RF-5383
URL: https://jira.jboss.org/jira/browse/RF-5383
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: Weblogic 9.1/Jboss4.2.1/Tomcat6.0 on Windows/Linux
Reporter: jFoundation java
Priority: Critical
When we ran the load testing for richfaces UI that we developed with minimum load upto 60 users, there was no issue. But if we increase beyond that load, Heap reaches the maximum heap utilization (as configured in jvm settings) and started taking more time for GC (though GC is happening but very limited objects are getting cleared). once the accumulated space reaches the max heap and started throwing OutOfMemory issue. This is only happening in higher user load. When we did the Profiling, we could not figure out this issue since we were able to do profiling with 1 user load.
With reference to this forum reply , the war file is added as an attachment. The the following scenario is used for load testing.
Testing Scenario:
Accommodation Basic Search:
Open the TOS Application in browser
Login with user name as LOCALADMIN and password as LOCALADMIN. Note: both are case sensitive.
Open "Quotation & Booking" menu and click on Search Availability
Type 'C' in Client text box and select CL100
Select 'A' as the Business segment and 'A' as the contact person
Enter City name as "Dubai"
Click on Search button
Search result will be displayed.
Click on Logout in the top navigation
Flight Search:
Open the TOS Application in browser
Login with user name as LOCALADMIN and password as LOCALADMIN. Note both are case sensitive.
Open "Quotation & Booking" menu and click on "Search Availability AA"
Enter From city as "DXB", To city as "LON", Departure Date as "1 Jan 2009", Return Date as "2 Jan 2009" and Adults as "1"
Click on Search button
Search result will be displayed.
Click on Logout in the top navigation
This war file is tested on Tomcat 6.0.10 and jdk 1.6.0_10
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 3 months
[JBoss JIRA] Created: (RF-5508) Provide a facility to cache on the browser the data/records that were already loaded through AJAX in tabPanel/scrollableDataTable. Also a refresh machanism is desired.
by Samba Siva Rao Kolusu (JIRA)
Provide a facility to cache on the browser the data/records that were already loaded through AJAX in tabPanel/scrollableDataTable. Also a refresh machanism is desired.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: RF-5508
URL: https://jira.jboss.org/jira/browse/RF-5508
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.2
Environment: Any JEE supporting Web/App Server and any standards compliant Browser
Reporter: Samba Siva Rao Kolusu
It would be highly desirable to have the data already loaded through AJAX be cached on the Browser rather than fetching it again every time the component accessed!
For example,in scrollableDataTable caching the data while we scroll down and showing the same when the user scrolls up makes reduces a lot of requests to the server and queries to the database. Similarly, In case of tabPanel, loading the data through AJAX only when the tab is created,and then displaying the cached data on every subsequent tab focus reduces so many requests to server. Similarly the tree nodes can be cached if loaded through AJAX. In general,this feature can be applied to other components in situations where data is loaded through AJAX. Preferably, this caching feature should be made optional by providing an attribute at the component level.
Also a means to refresh the cached data in the browser should be put in the component itself in either or both of the following ways :
1.the end user explicitly requesting "refresh cache" by clicking a link on the corresponding component or
2.based on some input or on meeting certain criteria, the page developer should be able to clear the cache and load records freshly.
It should be noticed that loading the same number of records as were there before clearing the cache (if they are still available) would be better from usability perspective.
Caching the data on the client-side improves performance manifold for those sites where there won't be any changes in the existing data set. But if there would be new records being added or existing records being deleted in the database , then client-side caching may not be any option to choose. Or may be we must ponder over how we can detect if there is a difference between the client-side cache and the data in the database,and then refresh the cache when a change is found!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 3 months