HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- garbage collection for j2ee application on Oracle ...
Operating System - HP-UX
1829107
Members
2773
Online
109986
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2005 05:04 AM
09-16-2005 05:04 AM
garbage collection for j2ee application on Oracle iAS 9041
We installed Oracle iAS 9041 to run a j2ee application from the Internet. We configured the OC4J container to use default heap size.
We use dmstools to gather memory usage on Forms and plotted out the free memory value.
During the course of 1 day, we see it did garbage collections every 10 minutes. Please see attachment.
Question: Is this a normal frequency for garbage collection?
Thanks.
We use dmstools to gather memory usage on Forms and plotted out the free memory value.
During the course of 1 day, we see it did garbage collections every 10 minutes. Please see attachment.
Question: Is this a normal frequency for garbage collection?
Thanks.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2005 09:10 AM
09-16-2005 09:10 AM
Re: garbage collection for j2ee application on Oracle iAS 9041
Garbage collection in Java, sadly enough - is not guaranteed to happen. Memory deallocation from deconstruction may happen, may not. Memory will be marked for deletion, but garbage runs determine when actual deallocation occurs.
The fact that it is happening every 10 minutes tells me that apparently the rate of usage of the program is pretty constant, but not much more.
I'm guessing that what you're seeing is that performance noticeably goes down during the garbage collect phase - right?
We somewhat solved this by *suggesting* that garbage collection happen more often. You can do this as you your exits certain areas of the program by making a call to the public static method of class System(java.lang):
System.gc();
.
This will SUGGEST to the java engine that it is time to garbage collect, and it is generally willing in my experience.
Doing this *can* make the garbage collection happen in little chunks (as user exits areas of functionality), instead of waiting a while for them to bundle, and having to clear out loads of data.
Try this approach, it might work for you.
You could go another way, by increasing the available memory, you will garbage collect less often - but the penalty will be that when it does have to happen, it will take longer. So, I don't recommend that approach.
The fact that it is happening every 10 minutes tells me that apparently the rate of usage of the program is pretty constant, but not much more.
I'm guessing that what you're seeing is that performance noticeably goes down during the garbage collect phase - right?
We somewhat solved this by *suggesting* that garbage collection happen more often. You can do this as you your exits certain areas of the program by making a call to the public static method of class System(java.lang):
System.gc();
.
This will SUGGEST to the java engine that it is time to garbage collect, and it is generally willing in my experience.
Doing this *can* make the garbage collection happen in little chunks (as user exits areas of functionality), instead of waiting a while for them to bundle, and having to clear out loads of data.
Try this approach, it might work for you.
You could go another way, by increasing the available memory, you will garbage collect less often - but the penalty will be that when it does have to happen, it will take longer. So, I don't recommend that approach.
We are the people our parents warned us about --Jimmy Buffett
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP