incubator-esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hirsch <hirsch.d...@gmail.com>
Subject Re: JMX code and scala-stats
Date Wed, 04 Nov 2009 05:13:01 GMT
Sounds great.

Just tell me when you are ready and I'll take over from there :->

D.

On Tue, Nov 3, 2009 at 8:04 PM, Andy the destroyer
<andythedestroyer@gmail.com> wrote:
> I am about half way done with a rest api for the JMX so it will work on
> STAX. The api works for any MBean not just stats and shouldn't screw up STAX
> because it doesn't use any adaptors. I haven't had much time to finish it
> due to school, work and family but I am hacking away at it.
>
> -A
>
> On Tue, Nov 3, 2009 at 1:28 AM, Richard Hirsch <hirsch.dick@gmail.com>wrote:
>
>> I committed the code from the existing patch and created a Wiki entry
>> describing its use:
>> http://cwiki.apache.org/confluence/display/ESME/JMX
>>
>> I decided to commit the code, because the Stax environment is just one
>> special deployment environment and usually we won't have to deal with
>> port restrictions.
>>
>> D
>>
>>
>> On Mon, Oct 26, 2009 at 5:41 AM, Richard Hirsch <hirsch.dick@gmail.com>
>> wrote:
>> > We have a strange exception on the stax deployment and the app doesn't
>> > run correctly, so I'm redeploying an old older version.
>> >
>> > javax.management.InstanceNotFoundException:
>> > localEngine:name=http-8085,type=GlobalRequestProcessor
>> >        at
>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094)
>> >        at
>> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:662)
>> >        at
>> com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
>> >        at
>> com.staxnet.appserver.queries.MBeanIntervalCounter.getMBeanStat(MBeanIntervalCounter.java:59)
>> >        at
>> com.staxnet.appserver.queries.MBeanIntervalCounter.updateValue(MBeanIntervalCounter.java:41)
>> >        at
>> com.staxnet.appserver.queries.RequestProcessingTimeCounter.updateValue(RequestProcessingTimeCounter.java:19)
>> >        at
>> com.staxnet.appserver.queries.AppStatsQuery$1.run(AppStatsQuery.java:70)
>> >        at java.util.TimerThread.mainLoop(Timer.java:512)
>> >        at java.util.TimerThread.run(Timer.java:462)
>> >
>> > D.
>> >
>> > On Sun, Oct 25, 2009 at 11:09 AM, Richard Hirsch <hirsch.dick@gmail.com>
>> wrote:
>> >> It is now really deployed on Stax. Once I test the HTTP/REST access,
>> >> I'll commit the code.
>> >>
>> >> So, how do I test the HTTP/REST  JMX access?
>> >>
>> >> D.
>> >>
>> >> On Sun, Oct 25, 2009 at 10:36 AM, Richard Hirsch <hirsch.dick@gmail.com>
>> wrote:
>> >>> It appears that I messed up  and the deployment wasn't successful.
The
>> >>> mean reason was that I didn't use the TortoiseSVN patch tool correctly
>> >>> and I deployed old code.  :-<.
>> >>>
>> >>> I finally got the patch tool to work and got an error:
>> >>>
>> >>> [WARNING]
>> D:\temp\committer_esme\trunk\server\src\main\scala\bootstrap\liftweb\
>> >>> oot.scala:165: error: not found: value ESMEStatsMBean
>> >>> [WARNING]     ESMEStatsMBean("org.apache.esme.stats")
>> >>> [WARNING]     ^
>> >>> [WARNING] one error found
>> >>>
>> >>> I changed "ESMEStatsMBean" to "StatsMBean"  and changed the twitter
>> >>> include so that it compiled
>> >>>
>> >>>
>> >>> D.
>> >>>
>> >>> On Sun, Oct 25, 2009 at 8:18 AM, Richard Hirsch <hirsch.dick@gmail.com>
>> wrote:
>> >>>> Tried to access the REST interface with
>> >>>> "http://esmecloudserverapache.dickhirsch.staxapps.net/rest/jmx"
and
>> >>>> got the error "The requested page was not defined in your SiteMap,
so
>> >>>> access was blocked.  (This message is displayed in development
mode
>> >>>> only)"
>> >>>>
>> >>>> What do I have to do to access the HTTP interface?
>> >>>>
>> >>>> D.
>> >>>>
>> >>>> On Sun, Oct 25, 2009 at 8:06 AM, Richard Hirsch <
>> hirsch.dick@gmail.com> wrote:
>> >>>>> I've added you to a project contributor in Jira and assigned
you this
>> item.
>> >>>>>
>> >>>>> Could you write a wiki piece on how to use it?
>> >>>>>
>> >>>>> On Fri, Oct 23, 2009 at 10:08 AM, Richard Hirsch <
>> hirsch.dick@gmail.com> wrote:
>> >>>>>> Packing and staging is fine. We can use OpenDMK without
problem to
>> >>>>>> test our JMX interface - for example in the Stax environment.
The
>> only
>> >>>>>> possible problems would be when we included it in the ESME
source.
>> >>>>>>
>> >>>>>> D.
>> >>>>>>
>> >>>>>> On Fri, Oct 23, 2009 at 11:02 AM, Andy the destroyer
>> >>>>>> <andythedestroyer@gmail.com> wrote:
>> >>>>>>> Actually I really just didn't look at the license. I
have only used
>> the
>> >>>>>>> package in testing and staging so I never paid attention.
I do know
>> the
>> >>>>>>> standard licenses, bsd, apache, gnu 1&2. I should
have checked.
>> Sorry.
>> >>>>>>>
>> >>>>>>> -Andy
>> >>>>>>>
>> >>>>>>> On Oct 23, 2009 1:15 AM, "Richard Hirsch" <hirsch.dick@gmail.com>
>> wrote:
>> >>>>>>>
>> >>>>>>> Do you mean this one: Project OpenDMK is the open source
project
>> for
>> >>>>>>> the JavaTM Dynamic Management Kit.
>> >>>>>>>
>> >>>>>>>  https://opendmk.dev.java.net/
>> >>>>>>>
>> >>>>>>> The majority of Project OpenDMK code is released under
and governed
>> by
>> >>>>>>> either the GNU General Public License, Version 2 only
(GPL) or the
>> >>>>>>> Common Development and Distribution License (CDDL).
Before
>> downloading
>> >>>>>>> Project OpenDMK software, you should become familiar
with these
>> >>>>>>> licences. Some binary components listed on the download
page are
>> >>>>>>> covered under the Binary License for Project OpenDMK.
>> >>>>>>>
>> >>>>>>> D.
>> >>>>>>>
>> >>>>>>> On Fri, Oct 23, 2009 at 10:10 AM, Andy the destroyer
>> >>>>>>>
>> >>>>>>> <andythedestroyer@gmail.com> wrote: > I can't
include a link right
>> now
>> >>>>>>> because I am unloading music ...
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> >
>>
>

Mime
View raw message