|
From: Alef A. <al...@jt...> - 2004-11-08 08:02:26
|
I have a couple of projects that would greatly benefit from Spring's JMX = support. Being able to slightly or temporarily reconfigure certain beans = in an application is something our projects often require. Think of = manually firing a job (cleanup, whatever). =20 alef =20 ________________________________ From: spr...@li... on behalf of = Seth Ladd Sent: Mon 11/8/2004 3:15 AM To: spr...@li... Subject: Re: [Springframework-developer] Re: Design patterns for JMX and = application manageability : A guide for developers. - HP Dev Resource = Central On Sun, 7 Nov 2004 21:35:06 +0000, Nick Minutello <nic...@gm...> wrote: > > We won't be competing to an appserver, but by JMX-enabling the core = Spring > > classes you will have a lot more runtime control over your Spring = beans. > > Fair enough. > I guess I havent run into examples of the sorts of things you would > want to control at runtime... hence my misunderstanding. Our biggest requirement is to control logging at runtime. By hooking log4j into JMX, we're now able to do this. Note that we had to do some hacking to log4j to get it to work with latest release of JMX. Seth ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=3D5588&alloc_id=3D12065&op=3Dclick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Seth L. <set...@gm...> - 2004-11-08 18:18:29
|
On Mon, 8 Nov 2004 09:01:17 +0100, Alef Arendsen <al...@jt...> wrote: > I have a couple of projects that would greatly benefit from Spring's JMX support. Being able to slightly or temporarily reconfigure certain beans in an application is something our projects often require. Think of manually firing a job (cleanup, whatever). Bingo! We have lots of Quartz jobs running. Can't wait to wire those into JMX to reschedule or fire the jobs manually. Seth |
|
From: Nick M. <nic...@gm...> - 2004-11-09 01:36:56
|
I can easily see why people would want to monitor or "poke" the odd component that was instantiated by spring (its exactly what I want to do). I havent yet seen which bits of Spring itself you would control or monitor via Spring... -Nick On Mon, 8 Nov 2004 08:18:22 -1000, Seth Ladd <set...@gm...> wrote: > On Mon, 8 Nov 2004 09:01:17 +0100, Alef Arendsen <al...@jt...> wrote: > > I have a couple of projects that would greatly benefit from Spring's JMX support. Being able to slightly or temporarily reconfigure certain beans in an application is something our projects often require. Think of manually firing a job (cleanup, whatever). > > Bingo! We have lots of Quartz jobs running. Can't wait to wire those > into JMX to reschedule or fire the jobs manually. > > > > Seth > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Rob H. <ro...@ca...> - 2004-11-09 08:33:46
|
Nick, If we JMXify the BeanFactory or ApplicationContext then we can expose a wide variety of functionality via a standard JMX MBean. For instance we could use JMX as an interface for hot swapping bean implementations at runtime or as a mechanism for introducing new bean definitions at runtime similar to the JMX MLet service. By introducing JMX we can introduce all sorts of lifecycle functionality and make it accessible using the wide variety of JMX adapters such as HTTP and SNMP - plus we can publish notifications to a wide variety of listeners using JMX notifications allowing for management of internal Spring functionality like caches and configuration files. Also since we now have JSR160 support, we can use JMX to provide a mechanism for remote management of Spring. Rob Nick Minutello wrote: >I can easily see why people would want to monitor or "poke" the odd >component that was instantiated by spring (its exactly what I want to >do). > >I havent yet seen which bits of Spring itself you would control or >monitor via Spring... > >-Nick > > >On Mon, 8 Nov 2004 08:18:22 -1000, Seth Ladd <set...@gm...> wrote: > > >>On Mon, 8 Nov 2004 09:01:17 +0100, Alef Arendsen <al...@jt...> wrote: >> >> >>>I have a couple of projects that would greatly benefit from Spring's JMX support. Being able to slightly or temporarily reconfigure certain beans in an application is something our projects often require. Think of manually firing a job (cleanup, whatever). >>> >>> >>Bingo! We have lots of Quartz jobs running. Can't wait to wire those >>into JMX to reschedule or fire the jobs manually. >> >> >> >>Seth >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: >>Sybase ASE Linux Express Edition - download now for FREE >>LinuxWorld Reader's Choice Award Winner for best database on Linux. >>http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click >>_______________________________________________ >>Springframework-developer mailing list >>Spr...@li... >>https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Sybase ASE Linux Express Edition - download now for FREE >LinuxWorld Reader's Choice Award Winner for best database on Linux. >http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > |