At 19:05 14.12.00 , you wrote:
>Hey all,
>
>while I'm writing some code that monitors the bean cache and that can be
>then viewed in a client through JMX, I'd like to ask what do you think will
>be the best between sample monitoring and event monitoring, ie:
>- sample monitoring: the client (normally a GUI with charts) calls a method
>through JMX to sample the status of JBoss every, say, 1 second
>- event monitoring: the client is a registered listener of JMS messages that
>are sent every time in JBoss some interesting value changes.
I hope I understand your suggestions right but I would definiteley vote for
a polling (sample) rather than a callback approach as the former is more
firewall-friendly, which is an issue in all J2EE production installations I
am in charge of. I agree that the callback approach is nicer but in real
life polling is the more robust approach that fits better into enterprise
or ASP environments. A polling concept together with https-tunnelling
allows all the monitoring most people need in a secure fashion and you
don't have a problem just monitoring your jBoss installation from a
notebook using your mobile phone without installing any special firewall,
proxy software whatsoever. I'd like that. Of course, having the option for
both is best but if one has to decide for one approach, I think you satisfy
more people's practical needs using the sample/polling approach.
my 2c
robert
>If you have other suggestions, they're welcome.
>
>For now I'm writing a simple implementation of sample monitoring.
>
>Simon
(-) Robert Kr�ger
(-) SIGNAL 7 Gesellschaft f�r Informationstechnologie mbH
(-) Br�der-Knau�-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665401, Fax: 06151 665373
(-) [EMAIL PROTECTED], www.signal7.de
