AOP is a technology to implement cross-cutting concerns and it is heavily used
in JBM 1.4. I simply used the existing classes (some of them are precompiled
with aopc) and added an interceptor. This one is called before/after the method
call. Using this the message rate (incoming/outgoing) or
Hi, thanks for the replies, sorry for replying late, postphoned this work until
the completion of another job.
I want the number of active producers/consumers and message rate on each topic
and metrics on memory as well.
@mlange
what is AOP? Can you please elaborate this?
to intercept the
JMX is the way to go. There are only very few monitoring metrics in 1.4 so I
decided to intercept the calls via AOP and aggregate them into a separate
mbean. This is fairly simple.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4213252#4213252
Reply to the
JBM 2.0 has management notifications (I guess this is what you mean by
monitoring metrics).
I'd be interested in what specific notifications would be of interest to you so
we can ensure we have them in JBM 2.0
View the original post :
What I was interested in (and what I implemented) was the current message
throughput (incoming and outgoing messages) because we use the clustered
messaging server as an asynchronous backend for other applications. Also
general message counters and the current registered message listeners are
Hi, I don't think JBM 1.4 has built-in monitoring topics. I think you can use
JMX.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4213243#4213243
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4213243
