Re: JMXProxyServlet
Look at the literature on JMX. Interesting stuff! On 12/18/05, anita kulshreshtha <[EMAIL PROTECTED]> wrote: > > Hi All, > What is required for a servlet to be able to > behave like the JMXProxyServlet in tomcat manager > application? > > Thanks In Advance > Anita > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~
Re: JMXProxyServlet
Anita, if you just read up on how this works the answer will become obvious. To make a class manageable by JMX you must implement a JMX interface and become part of an agent process. There is no short answer to any question that will replace learning the technology. On 12/19/05, anita kulshreshtha <[EMAIL PROTECTED]> wrote: > > Can any servlet access MBeans of type > RequestProcessor and GlobalRequestProcessor ? > > Thanks > Anita > > --- Dakota Jack <[EMAIL PROTECTED]> wrote: > > > Look at the literature on JMX. Interesting stuff! > > > > On 12/18/05, anita kulshreshtha > > <[EMAIL PROTECTED]> wrote: > > > > > > Hi All, > > > What is required for a servlet to be able to > > > behave like the JMXProxyServlet in tomcat manager > > > application? > > > > > > Thanks In Advance > > > Anita > > > > > > __ > > > Do You Yahoo!? > > > Tired of spam? Yahoo! Mail has the best spam > > protection around > > > http://mail.yahoo.com > > > > > > > > > - > > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > > > > > > -- > > "You can lead a horse to water but you cannot make > > it float on its back." > > ~Dakota Jack~ > > > > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~
Re: NIO vs BIO speed
I am interested in this code. Is there a way I can see the code? Thanks. On 6/22/06, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: Remy Maucherat wrote: Filip Hanik - Dev Lists wrote: Here is another test that I ran from a remote machine, setting maxThreads="25" and ab concurrency to 50 and keepalive on. In this case, NIO is a lot faster. Turn off keepalive on ab, and we get similar results to previous run, where BIO is a tad faster. Scaling the thread per connection model is done by increasing the amount of threads. This particular test demonstrates the obvious. yes, what is interesting though, is my NIO connector is not really true NIO, as it ties up a thread while polling for data. The true implementation would have not invoked that thread yet, but for that I would have had to rewritten the connector from scratch as I couldn't have taken advantage of code already written and tested. The reason it was done like this, is cause that way I could use almost all the code from the APR connector. So you could call it a semi-"thread-per-connection" model, yet handles better than the true thread per connection model. APR does the same thing. If I understand the results correctly, the results would be acceptable on Unix. yes, I think they are looking pretty good. And I am fairly confident in this new code, as most of it, is old tested APR code. Filip -- Filip Hanik -- "You can lead a horse to water but you cannot make it float on its back."~Dakota Jack~
