aspose file tools*
The moose likes Object Relational Mapping and the fly likes Q 4 C. Bauer & G. King (13) and JavaRanchers: garbage collection and pooling Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Databases » Object Relational Mapping
Bookmark "Q 4 C. Bauer & G. King (13) and JavaRanchers: garbage collection and pooling" Watch "Q 4 C. Bauer & G. King (13) and JavaRanchers: garbage collection and pooling" New topic
Author

Q 4 C. Bauer & G. King (13) and JavaRanchers: garbage collection and pooling

Gian Franco
blacksmith
Ranch Hand

Joined: Dec 16, 2003
Posts: 977
The issue of GC touched in this thread
particularly interests me, due to recent stability issues with
our application.

Amongst other things, I was wondering if one
can really rely on the GC when it comes to
pooling. Isn't it so that one can't command
the GC just merely give it a hint. Therefore
it might get easy for a connectivity problem to
escalate, and hence the source of the problem
difficult to trace back?

Cheers,

Gian Franco
[ September 02, 2004: Message edited by: Gian Franco Casula ]

"Eppur si muove!"
Alexandru Popescu
Ranch Hand

Joined: Jul 12, 2004
Posts: 995
Isn't it so that one can't command the GC just merely give it a hint.


This is true. But going back to your question I was wondering what other solution do we have? If the one of the most important things in Java cannot be trusted what else is it left?
I think we must concentrate on having a good programming and good configuration (adapted for the solution in case).

I don't think a pool of instances (which is not something recommended anymore) will help avoid bad programming and bad configurations.

./pope


blog - InfoQ.com
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Q 4 C. Bauer & G. King (13) and JavaRanchers: garbage collection and pooling