On May 12, 2009, at 12:23 AM, Igor Minar wrote:
>
> On May 11, 2009, at 10:09 PM, Ken Cavanaugh wrote:
>
>>
>> On May 11, 2009, at 4:17 PM, Survivant 00 wrote:
>>
>>> there was suppose to have a jmx implementation for grizzly.
>>>
>>> gmbal available on kenai.
>>
>> We have talked about using gmbal in Grizzly before, but I'm not
>> sure where that work is these days.
>
> I believe it's here: http://kenai.com/projects/gmbal
Yes, that's where I put gmbal. I was referring to an earlier
discussion about using gmbal in grizzly.
I'm the developer/owner for gmbal.
>
>
>> The gmbal bundles are also available from maven now: groupid
>> org.glassfish.gmbal, current
>> version 3.0.0-b002. There are currently 2 bundles:
>> • gmbal-api-only (14 K), which includes only the APIs needed to
>> build and run. A gmbal client can use this to minimize footprint
>> when MBeans are not needed.
>> • gmbal (250K), which includes everything.
>> Both bundles have the same API: the org.glassfish.gmbal. Note that
>> there is also a source bundle for reference
>> with each release (and for use in a debugger if needed).
>>
>> Unfortunately I won't be able to attend the Grizzly meeting this
>> week, if anyone plans to discuss gmbal
>> in grizzly this week.
>
> Actually, I think that we can implement this even without adding
> another dependency to the project. grizzly is already instrumented
> via JMX (as Jeanfrancois mentioned), so this would only needed to be
> extended.
Sure, that's fine too. It is easier to make the JMX instrumentation
compatible with AMX in GFv3 using gmbal,
but of course that is not required.
Ken.
>
>
> I'll create an RFE tomorrow.
>
> /i
>
>
>
>>
>> Ken.
>>>
>>>
>>> 2009/5/11 Survivant 00 <survivant00_at_gmail.com>
>>> sure that something embedded is better, but only if we use it :)
>>>
>>> What I was planning is to offer a webapp that can do jmx
>>> monitoring. if the user put that war into webapps folder, it
>>> willbe deployed..
>>>
>>> 2009/5/11 Igor Minar <iiminar_at_gmail.com>
>>> I'm glad that others were thinking about this too.
>>>
>>> IMO it would be better if such a feature was in the grizzly or
>>> grizzly-http module so that others can benefit from it (e.g. for
>>> glassfish that would be a major improvement).
>>>
>>> I actually already have a primitive implementation of something
>>> similar for grizzly-sendfile, but it works only for connections
>>> served by grizzly-sendfile (I'm using my own selector). If you are
>>> curious check out SendfileDownloadsMonitor.java
>>>
>>> /i
>>>
>>>
>>>
>>>
>>> On May 11, 2009, at 2:48 PM, Survivant 00 wrote:
>>>
>>> yes I would be nice. I had planned to add this feature with GWS
>>> Deployer.
>>>
>>> 2009/5/11 Igor Minar <iiminar_at_gmail.com>
>>> hi there,
>>>
>>> Sun Webserver 7 has a feature called "perfdump" which allows
>>> admins to quickly get all the important perf stats of the
>>> webserver by hitting a URI or using the console tool. One part
>>> that I find really useful to when debugging production issues, is
>>> the list of open sessions (basically the list of requests that are
>>> currently being processed by the webserver with the ip addresses
>>> and the states).
>>>
>>> I was wondering if anyone thinks that this would be a useful
>>> feature for grizzly too. Info like this exposed via JMX would be
>>> pretty cool IMO.
>>>
>>> http://blogs.sun.com/elving/entry/perfdump_in_7_0
>>> http://docs.sun.com/app/docs/doc/820-1067/6ncovgc84?l=ru&a=view
>>>
>>> what do you think?
>>>
>>> /i
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>
>>>
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>