Re: Can I find out what webapps resin is running?

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
> > >      >
> > >
> > >
> > >
> >
> >
> >
>
>