[ 
https://issues.apache.org/jira/browse/IGNITE-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739997#comment-14739997
 ] 

ASF GitHub Bot commented on IGNITE-1378:
----------------------------------------

GitHub user vkulichenko opened a pull request:

    https://github.com/apache/ignite/pull/83

    IGNITE-1378 - Fixed exception handling in GridContinuousProcessor

    

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

    $ git pull https://github.com/vkulichenko/incubator-ignite ignite-1378

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

    https://github.com/apache/ignite/pull/83.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 #83
    
----
commit 4f652966c956e8a04576c1b60089ba34d052b7a1
Author: Valentin Kulichenko <valentin.kuliche...@gmail.com>
Date:   2015-09-08T20:35:35Z

    IGNITE-1378 - Fixed exception handling in 
GridContinuousProcessor.startRoutine()

commit 6cda6ec91d7d7be588eda57e62dbfe06153ceee9
Author: Valentin Kulichenko <valentin.kuliche...@gmail.com>
Date:   2015-09-11T01:36:58Z

    Merge branch 'ignite-1.4' into ignite-1378

----


> Continuous processor doesn't remove message listener if continuous query 
> failed to start
> ----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-1378
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1378
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>            Reporter: Valentin Kulichenko
>            Assignee: Valentin Kulichenko
>            Priority: Blocker
>             Fix For: ignite-1.4
>
>
> {{GridContinuousProcessor.startRoutine(..)}} method adds message listener on 
> line 538 and never removes it if handler registration fails (e.g., due to 
> marshalling issues). Need to fix exception handling in this method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to