GitHub user ctron opened a pull request:

    https://github.com/apache/camel/pull/1833

    CAMEL-11559: Work around a NPE in milo 0.1.3

    When the sampling interval is unset in the Camel component, then it is 
passed to milo as `null`. Which is acceptable to the milo API, however 
internally milo automatically unboxes the value from `Double` to `double` and 
may run into a NPE by doing so.
    
    This patch assures that, although theoretically acceptable, `null` is never 
passed in to the Milo API.
    
    Signed-off-by: Jens Reimann <jreim...@redhat.com>

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

    $ git pull https://github.com/ctron/camel feature/fix_issue_11559

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

    https://github.com/apache/camel/pull/1833.patch

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

    This closes #1833
    
----
commit 1a692127f54990e72dcbf1d56f83b0e3cb9df20e
Author: Jens Reimann <jreim...@redhat.com>
Date:   2017-07-19T08:21:33Z

    CAMEL-11559: Work around a NPE in milo 0.1.3
    
    When the sampling interval is unset in the Camel component, then it is
    passed to milo as 'null'. Which is acceptable to the milo API, however
    internally milo automatically unboxes the value from 'Double' to
    'double' and may run into a NPE by doing so.
    
    This patch assures that, although theoretically acceptable,
    'null' is never passed in to the Milo API.
    
    Signed-off-by: Jens Reimann <jreim...@redhat.com>

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to