Problem with Java Heap Space using Socket

[mvillara]

Hi,

I have a Server in Java using Socket and ServerSocket and a client. Well, the communication is perfect. The server must send about 35 - 300 packets per second. Well, when the process is working about 4 or 5 hours, the server goes down with an error: OutOfMemoryError: Java heap Space. How can i solve this problem? I know that its a virtual memory issue and i know how to increase it but the problem will persist some hours later if i increase it.

Does anyone know any technic?

Thanks in advance.

[RamyaSivakanth]

Using JProfiler,you can check which part of code is taking more memory and we can do some correction related to our design.If not,let me think some other option and tell you.

[mvillara]

Hi RamyaSivakanth,

Thanks for your reply. I will check JProfile to learn how to use it.
By now, i have running the Server with the client connected and sending packets continuosly watching with Runtime.freeMemory() the virtual memory available and i can see that the memoria start decreasing from 70Mb to 60Mb and suddently it recover back, so it seems that works fine but not.... we have to wait for 4 hours to see how the memory down to almost 0 bytes free.

The sever alway has the same work.

[Steve11235]

The garbage collector will wait until a certain amount of the heap is in use and then reclaim old objects to get the heap space back, so having the heap space drop and then restore is normal.

On the other hand, 60 - 70 MB is not much memory, especially for a server. I provide 512 MB just to run Netbeans or Eclipse. While dwindling memory indicates a memory leak, if you don't provide a large enough heap, you may simply not have enough heap for your server to run, especially when it is handling so many transactions.

What are your heap settings?