Re: Can I find out what webapps resin is running?
"Bill Au" <[email protected]> Thu, 22 Jun 2006 08:01:31 -0400
| Newsgroups | gmane.text.xml.resin.user |
|---|---|
| Message-ID | <[email protected]> |
------=_Part_2738_5321775.1150977691958 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline If you are using Java 5, take a look at the MXBeans under java.lang.management. That's what JConsole and Scottit use behind the screen. They are very simple to use. You will find sample code under demo/management in your JDK install directory. Bill On 6/21/06, Jay Ballinger <[email protected]> wrote: > > One of our developers, who apparently doesn't have enough work to do, > borrowed the thread dump code from Scottit and added it to the > ResinStatusServlet with very little effort. Makes for a nice combo. ;) > > > > On 6/20/06, Bill Au <[email protected]> wrote: > > Threads count, sessions count, memory usage, db pools are all covered > > by ResinStatusServlet. In addition, it also shows the invocation and > proxy > > cacahe > > hit ratio. We have software in place to monitor threads count and > memory > > usage > > over HTTP. We are also logging gc info to file. I would have been > nice if > > we can > > monitor gc over HTTP too. Too bad that Scottit is reporting inaccurate > > data for gc. > > > > Yes, jconsole is very nice but it requires that jmxremote to be > enabled. > > We don't want to pay that overhead in production. Can't want for Java > 6 > > where > > jconsole can connect on-demand. > > > > Yes, the thread dump is about the only thing that Scottit provides that > I > > can't get > > from ResinStatusServlet. We already have ways to do that before we > learn > > about > > Scottit. So we had decided not to install another webapp (Scottit) > just > > for showing > > the thread dump. > > > > Bill > > > > > > On 6/20/06, Keith Fetterman <[email protected]> wrote: > > > Hi Bill, > > > > > > Sorry it took me so long to respond. > > > > > > Bill Au wrote: > > > > What useful information are you getting out of Scottit 3.1 that is > not > > > > available in ResinStatusServlet? > > > > > > We were experiencing a slow down with our Web site, and yet I couldn't > > > find any reason for it. All of the physical resources, like server > CPU > > > performance, network performance, memory consumption, database > > > connections, etc. did not show a problem. When I ran Scottit 3.1, I > > > found the problem. The critical information was this: active > sessions > > > and active threads. Before Scottit, I had no way to see the active > > > sessions and threads in production in real time. My problem ended up > > > being the max-threads were way too low. I quadrupled the limit and > > > solved my problem. > > > > > > There is also tons of other useful stuff. I can see a thread dump in > > > real time without having to perform a special command, sending an > > > interrupt to the server. > > > > > > I can see the total memory and with a Java applet I can watch the > > > garbage collections. But, If you really want to see the whole memory > > > picture, I recommend using jconsole instead. > > > > > > Since I was having memory problems about 6 months ago, I currently log > > > all GCs to a file so I can monitor it on a daily basis. > > > > > > I can also monitor the DB connection pools. > > > > > > > > > > > In the pre-release version that I had looked at, the GC information > > > > reported in the memory section was not accurate. They don't match > up > > > > with numbers reportes by the platform MBean or the -Xloggc > output. I > > > > was very disappointed to see that in the official release, the gc > info > > > > was removed completely instead of being fixed. > > > > > > I haven't performed a comparison of the memory section with the GC log > > > entries that are written to a log file so I can't comment on that. > > > > > > Overall, It provides a lot of information about a running Resin server > > > and the applications that are running on it. I didn't have to write > any > > > custom code to get it. And to top it all off, the developers are not > > > currently charging a fee to use it. Can't beat it. > > > > > > Take care, > > > Keith > > > > > > > > > > > > > > Throughput was still "Under construction" before and it is now also > > gone. > > > > > > > > Bill > > > > > > > > On 6/14/06, *Keith Fetterman* <[email protected] > > > > <mailto:[email protected] >> wrote: > > > > > > > > I highly recommend Scottit 3.1. > > > > > > > > http://www.ustobe.com/scottit/ > > > > > > > > It rocks because it provides a lot of information about the > running > > > > Resin server and the applications that are running. > > > > > > > > David Campbell wrote: > > > > > Andy Yates wrote: > > > > >> Just a quickie. Apart from performing an ls on the webapps > > directory > > > > >> is there anyway I can query a Resin server to tell me what > > > > webapps it > > > > >> is currently hosting (by name). > > > > >> > > > > >> i.e. If I have 4 apps called app, foo, bar, test can I get a > > webpage > > > > >> up which says "Currently hosting app, foo, bar, test". > > > > >> > > > > >> I'm not about the status of the app just what its got. > > > > > > > > > > resin-status > > > > > > > > > > http://www.caucho.com/resin-3.0/jmx/servlet.xtp > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------=_Part_2738_5321775.1150977691958 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline If you are using Java 5, take a look at the MXBeans under java.lang.management.<br> That's what JConsole and Scottit use behind the screen. They are very simple<br> to use. You will find sample code under demo/management in your JDK install<br> directory.<br> <br> Bill<br><br><div><span class="gmail_quote">On 6/21/06, <b class="gmail_sendername">Jay Ballinger</b> <<a href="mailto:[email protected]">[email protected]</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> One of our developers, who apparently doesn't have enough work to do,<br>borrowed the thread dump code from Scottit and added it to the<br>ResinStatusServlet with very little effort. Makes for a nice combo. ;)<br><br><br> <br>On 6/20/06, Bill Au <<a href="mailto:[email protected]">[email protected]</a>> wrote:<br>> Threads count, sessions count, memory usage, db pools are all covered<br>> by ResinStatusServlet. In addition, it also shows the invocation and proxy <br>> cacahe<br>> hit ratio. We have software in place to monitor threads count and memory<br>> usage<br>> over HTTP. We are also logging gc info to file. I would have been nice if<br>> we can<br>> monitor gc over HTTP too. Too bad that Scottit is reporting inaccurate <br>> data for gc.<br>><br>> Yes, jconsole is very nice but it requires that jmxremote to be enabled.<br>> We don't want to pay that overhead in production. Can't want for Java 6<br>> where<br>> jconsole can connect on-demand. <br>><br>> Yes, the thread dump is about the only thing that Scottit provides that I<br>> can't get<br>> from ResinStatusServlet. We already have ways to do that before we learn<br>> about<br>> Scottit. So we had decided not to install another webapp (Scottit) just <br>> for showing<br>> the thread dump.<br>><br>> Bill<br>><br>><br>> On 6/20/06, Keith Fetterman <<a href="mailto:[email protected]">[email protected]</a>> wrote:<br>> > Hi Bill, <br>> ><br>> > Sorry it took me so long to respond.<br>> ><br>> > Bill Au wrote:<br>> > > What useful information are you getting out of Scottit 3.1 that is not<br>> > > available in ResinStatusServlet? <br>> ><br>> > We were experiencing a slow down with our Web site, and yet I couldn't<br>> > find any reason for it. All of the physical resources, like server CPU<br>> > performance, network performance, memory consumption, database <br>> > connections, etc. did not show a problem. When I ran Scottit 3.1, I<br>> > found the problem. The critical information was this: active sessions<br>> > and active threads. Before Scottit, I had no way to see the active <br>> > sessions and threads in production in real time. My problem ended up<br>> > being the max-threads were way too low. I quadrupled the limit and<br>> > solved my problem.<br>> ><br>> > There is also tons of other useful stuff. I can see a thread dump in <br>> > real time without having to perform a special command, sending an<br>> > interrupt to the server.<br>> ><br>> > I can see the total memory and with a Java applet I can watch the<br>> > garbage collections. But, If you really want to see the whole memory <br>> > picture, I recommend using jconsole instead.<br>> ><br>> > Since I was having memory problems about 6 months ago, I currently log<br>> > all GCs to a file so I can monitor it on a daily basis. <br>> ><br>> > I can also monitor the DB connection pools.<br>> ><br>> > ><br>> > > In the pre-release version that I had looked at, the GC information<br>> > > reported in the memory section was not accurate. They don't match up <br>> > > with numbers reportes by the platform MBean or the -Xloggc output. I<br>> > > was very disappointed to see that in the official release, the gc info<br>> > > was removed completely instead of being fixed. <br>> ><br>> > I haven't performed a comparison of the memory section with the GC log<br>> > entries that are written to a log file so I can't comment on that.<br>> ><br>> > Overall, It provides a lot of information about a running Resin server <br>> > and the applications that are running on it. I didn't have to write any<br>> > custom code to get it. And to top it all off, the developers are not<br>> > currently charging a fee to use it. Can't beat it. <br>> ><br>> > Take care,<br>> > Keith<br>> ><br>> ><br>> > ><br>> > > Throughput was still "Under construction" before and it is now also<br>> gone.<br>> > > <br>> > > Bill<br>> > ><br>> > > On 6/14/06, *Keith Fetterman* <<a href="mailto:[email protected]">[email protected]</a><br>> > > <mailto:<a href="mailto:[email protected]"> [email protected]</a> >> wrote:<br>> > ><br>> > > I highly recommend Scottit 3.1.<br>> > ><br>> > > <a href="http://www.ustobe.com/scottit/">http://www.ustobe.com/scottit/ </a><br>> > ><br>> > > It rocks because it provides a lot of information about the running<br>> > > Resin server and the applications that are running.<br>> > ><br>> > > David Campbell wrote: <br>> > > > Andy Yates wrote:<br>> > > >> Just a quickie. Apart from performing an ls on the webapps<br>> directory<br>> > > >> is there anyway I can query a Resin server to tell me what <br>> > > webapps it<br>> > > >> is currently hosting (by name).<br>> > > >><br>> > > >> i.e. If I have 4 apps called app, foo, bar, test can I get a <br>> webpage<br>> > > >> up which says "Currently hosting app, foo, bar, test".<br>> > > >><br>> > > >> I'm not about the status of the app just what its got. <br>> > > ><br>> > > > resin-status<br>> > > ><br>> > > > <a href="http://www.caucho.com/resin-3.0/jmx/servlet.xtp">http://www.caucho.com/resin-3.0/jmx/servlet.xtp </a><br>> > > ><br>> > ><br>> > ><br>> > ><br>> ><br>> ><br>> ><br>><br>><br><br></blockquote></div><br> ------=_Part_2738_5321775.1150977691958--