Guava's caches include the ability to define eviction behavior, based on
timeouts, memory usage, etc. Seriously, check them out if you haven't
previously, you'll be glad you did.
I'm not sure keying off the class name solves the problem (if there really
is one). If you've got a situation where y
Kevin,
Messages don't pile up on advisory topics because of the semantics of
topics: unless you have a durable subscription (which the broker-to-broker
advisory subscriptions aren't, if I recall correctly), any message that
arrives on the broker will be delivered to all connected consumers (and no
Ah.. What I could do is contain a reference to the Class name.. I think
it’s just Class method and parameter annotations. So those have full paths.
And I was probably just going to use a simple ConcurrentHashMap for the
case..
I t *might* leak a bit of memory if it’s static.. but maybe I could m
Guava's got some awesome support for caches; they may be the best feature
in the library (and Multisets/Multimaps are pretty awesome). If you
implement this (and it sounds like a good enhancement), you should use them
for it.
One thing to consider: this cache will hold references to classes, and
You'd have a hard time sending messages without connecting to a broker, so
I'd suggest confirming first that you actually see a connection in JMX (I'd
recommend using JConsole's MBeans tab). If you don't, it probably means
you're connecting to a different broker than you think you are.
If you do,
