A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
Win a copy of
EJB 3 in Action
this week in the
EJB and other Java EE Technologies
Other Open Source Projects
JAMon - implications if Monitor#stop is never reached
Myyron Murray Latorilla
Joined: Dec 10, 2009
Nov 05, 2012 22:16:50
Not sure if this topic is on the right category, please do advise.
For the subject, I'm wondering what are the implications if Monitor#stop is never reached in the code. Thanks in advance.
Joined: Mar 22, 2005
Nov 05, 2012 23:21:24
Depends on the amount of data you're tracking. You could run out of memory at some point.
Ping & DNS
- updated with new look and Ping home screen widget
Joined: Jun 26, 2002
Dec 01, 2012 02:15:26
not calling 'stop' has no effect on memory in jamon. The only result is that the 'active' number will continually climb, but the objects themselves will be properly garbage collected when the code goes out of scope.
- a fast, free open source performance tuning api.
JavaRanch Performance FAQ
I agree. Here's the link:
subject: JAMon - implications if Monitor#stop is never reached
String Equality diffs bw EJB-QL and SQL
WA #1.....word association
In reference to notify maybe pausing a thread?
Thought of the Day!
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2014