It seems Iike the delay I encountered was due to problems on the client side that I have now resolved.
Thanks, /Bengt 2010/2/18 Bengt Rodehav <[email protected]> > Thanks for your reply Claus. However, I've really tried to Google about > this and I haven't managed to find out how this works. If anyone has a hint > I would really appreciate it. > > /Bengt > > 2010/2/18 Claus Ibsen <[email protected]> > > On Thu, Feb 18, 2010 at 2:15 PM, Bengt Rodehav <[email protected]> wrote: >> > I'm creating my own user interface for interacting with Camel routes via >> > JMX. I seem to have a "delay" problem when reading these attributes. E g >> > when reading the "ExchangesCompleted" attribute, it takes a while (> 1 >> > minute) after an exchange is completed before this value is incremented. >> > >> > When reading the value via the JConsole, the value is immediately >> updated >> > (after I press the "refresh" button) meaning that I must be doing >> something >> > wrong when accessing the JMX attribute. Can someone enlighten me as to >> what >> > is going on and how I can make sure that I read the latests (up-to-date) >> > value. E g , is there a "refresh" method I can call from my code? >> > >> > /Bengt >> > >> >> I think there is some general JMX "refresh" or "delay" interval which >> can be set to indicate how often the JMX attributes updates are >> visible. >> Try to google about about this. >> >> >> -- >> Claus Ibsen >> Apache Camel Committer >> >> Author of Camel in Action: http://www.manning.com/ibsen/ >> Open Source Integration: http://fusesource.com >> Blog: http://davsclaus.blogspot.com/ >> Twitter: http://twitter.com/davsclaus >> > >
