 |  |  |  |  |  |  |  |
java.lang.OutOfMemoryError
Please support our Java advertiser: Programming Forums - DaniWeb Sister Site
 |
Hi all,
I have a threaded program, which migrates contetn from one repository to another. The program works fine, when I test for small number of documents, say arround 10 or 20. But when I increase the number of documents, then I get java.lang.OutOfMemoryError. I can't seem to figure out how to fix this.
I presume it is the JVM which runs out of memory. Can someone please shed some lights arround this. Now, I am not sure if it's my code, or its JVM setting.
Please advise...
Thanks,
I have a threaded program, which migrates contetn from one repository to another. The program works fine, when I test for small number of documents, say arround 10 or 20. But when I increase the number of documents, then I get java.lang.OutOfMemoryError. I can't seem to figure out how to fix this.
I presume it is the JVM which runs out of memory. Can someone please shed some lights arround this. Now, I am not sure if it's my code, or its JVM setting.
Please advise...
Thanks,
•
•
Join Date: May 2007
Posts: 4,508
Reputation: 
Solved Threads: 522
Two options:
1) Give the program more memory with -Xmx: http://java.sun.com/javase/6/docs/te...a.html#options
2) Use less memory. That may involved using a smaller thread pool or limiting buffer sizes for file operations, etc.
1) Give the program more memory with -Xmx: http://java.sun.com/javase/6/docs/te...a.html#options
2) Use less memory. That may involved using a smaller thread pool or limiting buffer sizes for file operations, etc.
•
•
Join Date: Jun 2006
Posts: 7,648
Reputation:
Solved Threads: 474
Two reasons come to mind:
- A rogue implementation which manifests itself as the number of documents to be transferred increases. Profile the application thoroughly looking for memory leaks and unintentional object retention.
- The default heap size doesn't suit well for your current processing needs. Tune your JVM by setting an appropriate heap size and garbage collection strategy to suit your needs.
Read this.
- A rogue implementation which manifests itself as the number of documents to be transferred increases. Profile the application thoroughly looking for memory leaks and unintentional object retention.
- The default heap size doesn't suit well for your current processing needs. Tune your JVM by setting an appropriate heap size and garbage collection strategy to suit your needs.
Read this.
I don't accept change; I don't deserve to live.
Jo Tujhe Jagaaye, Nindein Teri Udaaye Khwaab Hai Sachcha Wahi.
Nindon Mein Jo Aaye Jise To Bhul Jaaye Khawab Woh Sachcha Nahi.
Khwaab Ko Raag De, Nind Ko Aag De
Jo Tujhe Jagaaye, Nindein Teri Udaaye Khwaab Hai Sachcha Wahi.
Nindon Mein Jo Aaye Jise To Bhul Jaaye Khawab Woh Sachcha Nahi.
Khwaab Ko Raag De, Nind Ko Aag De
|
Similar Threads
- XML Update?? (RSS, Web Services and SOAP)
- OutOfMemory Error (Java)
Other Threads in the Java Forum
- Previous Thread: File Input Exception
- Next Thread: Sunflower program...probably completely wrong...help!
| Thread Tools | Search this Thread |
Latest Java Posts
- Today's Posts
- Unanswered Threads
Related Forum Features
Tag cloud for Java
addressbook android api apple applet application arguments array arrays automation binary bluetooth button calculator chat class classes client code columns component converter database draw eclipse error errors event exception file fractal ftp game givemetehcodez graphics gridlayout gui helpwithhomework html ide image inetaddress input integer j2me japplet java javaprojects jme jmf jni jpanel julia link linux list loop map method methods midlethttpconnection mobile netbeans newbie number objects openjavafx oracle php print problem program programming project projects recursion rim scanner screen server set signing size smart sms socket sort sql storm string support swing test threads time tree unlimited variablebinding webservices windows
