Re: Long running open connections badly leak memory
From: Joerg von Frantzius (joerg.von.frantzius_at_artnology.REMOVE.com)
Date: 02/22/05
- Next message: Alin Sinpalean: "Re: Long running open connections badly leak memory"
- Previous message: Alin Sinpalean: "Re: Long running open connections badly leak memory"
- In reply to: Alin Sinpalean: "Re: Long running open connections badly leak memory"
- Next in thread: Alin Sinpalean: "Re: Long running open connections badly leak memory"
- Reply: Alin Sinpalean: "Re: Long running open connections badly leak memory"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 22 Feb 2005 11:13:37 +0100
Alright, now I got the point about the Statements and ResultSets, sorry. To be honest, I can't be absolutely sure about that, because I'm relying on a JDO implementation to take care of it.Joerg von Frantzius wrote:When I close the connections, memory is reclaimed properly. What I wanted to say is that memory is eaten up indefinitely as long as the connection *remains open* and is used to repeatedly write largechunksof data into the DB.I understand that. What I meant to say is "are you sure you are explicitly closing ALL Statements and ResultSets when you're done with them?". Leaving them open could and will cause the effects you now see. Alin.
- Next message: Alin Sinpalean: "Re: Long running open connections badly leak memory"
- Previous message: Alin Sinpalean: "Re: Long running open connections badly leak memory"
- In reply to: Alin Sinpalean: "Re: Long running open connections badly leak memory"
- Next in thread: Alin Sinpalean: "Re: Long running open connections badly leak memory"
- Reply: Alin Sinpalean: "Re: Long running open connections badly leak memory"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|