On Thu, May 24, 2012 at 1:19 PM, Peter Roßbach wrote:
> HI Vadzim,
>
> as you like a hot HTTP-JMX access use
>
> http://www.jolokia.org/
>
> chili...
>
> Peter
>
>
> Am 23.05.2012 um 00:06 schrieb Vadzim Mikhalenak:
>
> > On Wed, May 23, 2012 at 12:31 AM, Konstantin Kolinko <
> knst.koli...@gmail
HI Vadzim,
as you like a hot HTTP-JMX access use
http://www.jolokia.org/
chili...
Peter
Am 23.05.2012 um 00:06 schrieb Vadzim Mikhalenak:
> On Wed, May 23, 2012 at 12:31 AM, Konstantin Kolinko > wrote:
>
>> 2012/5/22 Vadzim Mikhalenak :
>>> Hello Christopher,
>>> *
>>> *
>>> Thank you for
apache.org/tomcat-6.0-doc/config/listeners.html#JMX_Remote_Lifecycle_Listener_-_org.apache.catalina.mbeans.JmxRemoteLifecycleListener
>
>
>
> - Original Message -
> > From: "Vadzim Mikhalenak"
> > To: "Tomcat Users List"
> > Sent: Tuesday,
6:52 PM
> Subject: Re: Tomcat 7. MX4J
>
> On Wed, May 23, 2012 at 12:31 AM, Konstantin Kolinko
> > wrote:
>
> > 2012/5/22 Vadzim Mikhalenak :
> > > Hello Christopher,
> > > *
> > > *
> > > Thank you for the reply! Yes, link
> > &
On Wed, May 23, 2012 at 12:31 AM, Konstantin Kolinko wrote:
> 2012/5/22 Vadzim Mikhalenak :
> > Hello Christopher,
> > *
> > *
> > Thank you for the reply! Yes, link
> > http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html is for version
> 5.5
> > but we are migrating from version 6 (sorry fo
2012/5/22 Vadzim Mikhalenak :
> Hello Christopher,
> *
> *
> Thank you for the reply! Yes, link
> http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html is for version 5.5
> but we are migrating from version 6 (sorry for the confusion) but the
> configuration above was valid for version 6
>
It w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vadim,
Bringing this back onto the list...
On 5/22/12 4:29 PM, Vadzim Mikhalenak wrote:
> Thank you for the reply! Yes, link
> http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html is for
> version 5.5 but we are migrating from version 6 (sorry fo
Hello,
We are going to migrate our application from tomcat 6 to tomcat 7. But
during migration we've faced with the following issue:
we have the following configuration to have possbility to manage JMX Bean
using browser (through http):
...
...
as described at the following page:
http://tomcat.a