|
![]() |
"Eagles may soar but weasels don't get sucked into jet engines" SCJP 1.6, SCWCD 1.4, SCJD 1.5,SCBCD 5
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
Originally posted by rajesh bala:
Thatz
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
Originally posted by rajesh bala:
Hi Harish,
Yes. That would definitely affect the system's heap. Thatz the reason you might have observed this behavior.
Creating statements, explicitly closing the resultset and statement might clear the native leaks. But will it not affect the system performance?. PreparedStatements basically reduce the parsing-factor and query-path computation to a great extent. If you are going ahead with statements, every statement has to be parsed again.
Is it not possible to use type-4 driver?. I am not sure about your environment. But if possible, you could get rid of type-2 and switch over to type-4.
~Rajesh.B
Originally posted by Paul Maeng:
Maciej Miklas
I woder how you solved your issue. I have same problem to goes up to 300mb until ended the processing.
please show me.
thanks,
paul
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
Originally posted by Peter Chase:
In general, we would prefer you not to restart months-old discussion threads: DontWakeTheZombies.
Surfs up space ponies, I'm making gravy without this lumpy, tiny ad:
New web page for Paul's Rocket Mass Heaters movies
https://coderanch.com/t/785239/web-page-Paul-Rocket-Mass
|