- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- java memory leak problem
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
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
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
12-14-2006 04:50 PM
12-14-2006 04:50 PM
java memory leak problem
and we found it has severe memory leak after monitoring HPjtune and HPjmeter.
still trying to find which part is wrong but the source code looked alright.
most of the cases, we usually don't think about memory leak about java, because garbage-collector does manage memory and there's no way to remove instances in java source code(like 'delete ..' in C++).
i want to know which case brings memory leak when we writes java source code.
thank you,
- Tags:
- Java
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2006 09:53 PM
12-18-2006 09:53 PM
Re: java memory leak problem
were do you want to start ? ;-)
Have a read of some of the stuff returned by:
http://www.google.co.uk/search?hl=en&q=memory+leak++JAVA&meta=
A simple start is to first concentrate on areas of that that are repeatetly executed.
Please also read:
http://forums1.itrc.hp.com/service/forums/helptips.do?#33 on how to reward any useful answers given to your questions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
3 weeks ago
Re: java memory leak problem
Java has automatic garbage collection, which essentially clears unwanted objects from the application. This garbage collection will only free up objects that are no longer referenced or are not reachable. When objects that are no longer needed still reference other objects, the garbage collector will not recognize these objects as unwanted ones, and this will not help in reclaiming the memory. If this persists, it will slowly lead to a memory leak. In socket-based Java applications, such as those implementing FTP functionality, memory leaks can be caused by several actions, including when static fields hold references, when caches continue to grow indefinitely, or when objects are registered but never removed after actions are performed. Over time, these actions result in the accumulation of memory, leading to a slow increase in heap size and ultimately causing performance degradation or an OutOfMemoryError. For a deeper understanding of common signs of a Java memory leak, identifying memory leaks by analyzing a heap dump, check out this blog, From Symptoms to Solutions: Troubleshooting Java Memory Leaks & OutOfMemoryError.