geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dineshakhand <>
Subject [GitHub] geode pull request #720: Feature/geode 3462
Date Fri, 18 Aug 2017 09:45:14 GMT
GitHub user dineshakhand opened a pull request:

    Feature/geode 3462

    Thank you for submitting a contribution to Apache Geode.
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    ### For all changes:
    - [X ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit
    - [ X] Has your PR been rebased against the latest commit within the target branch (typically
    - [X ] Is your initial contribution a single, squashed commit?
    - [ X] Does `gradlew build` run cleanly?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way
that is compatible for inclusion under [ASF 2.0](
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and
    submit an update to your PR as soon as possible. If you need help, please send an
    email to

You can merge this pull request into a Git repository by running:

    $ git pull feature/GEODE-3462

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #720
commit 34f2a388f4643f8a5dd5374a2f9f2b8178367c13
Author: dineshpune2006 <>
Date:   2017-08-18T09:24:03Z

    Function Stats for JMX
    Async Qeueu Internal Region are exposed to JMX

commit f321c4b4e0d490f93a0a2611a6f219db4a8c1d97
Author: dineshpune2006 <>
Date:   2017-08-18T09:24:49Z

    Function Stats exposed to JMX
    Async Queue Internal Region are exposed to JMX


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message