[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service
[ https://issues.apache.org/jira/browse/IGNITE-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4235: Fix Version/s: (was: 2.1) 2.2 > Can't get user exception if was on remote service > - > > Key: IGNITE-4235 > URL: https://issues.apache.org/jira/browse/IGNITE-4235 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.7 >Reporter: Dmitriy Govorukhin > Fix For: 2.2 > > Attachments: node1.log, node2.log, Reproducer.java > > > Can get user exception if was on remote node. Reproducer in attached file. > For reproduce, run node1 first, second node 2, check logs. If remove cluster > group, for deploy service1, for node1, all will be okay, but if stay it, will > be error, see attached log. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service
[ https://issues.apache.org/jira/browse/IGNITE-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-4235: --- Attachment: Reproducer.java > Can't get user exception if was on remote service > - > > Key: IGNITE-4235 > URL: https://issues.apache.org/jira/browse/IGNITE-4235 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.7 >Reporter: Dmitriy Govorukhin > Fix For: 2.0 > > Attachments: Reproducer.java > > > Can get user exception if was on remote node. Reproducer in attached file . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service
[ https://issues.apache.org/jira/browse/IGNITE-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-4235: --- Description: Can get user exception if was on remote node. Reproducer in attached file . For reproduce, run node1 first, second node 2, check logs. If remove cluster group, for node1, all will be okay, but if stay it, will be error, see attached log. (was: Can get user exception if was on remote node. Reproducer in attached file .) > Can't get user exception if was on remote service > - > > Key: IGNITE-4235 > URL: https://issues.apache.org/jira/browse/IGNITE-4235 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.7 >Reporter: Dmitriy Govorukhin > Fix For: 2.0 > > Attachments: Reproducer.java > > > Can get user exception if was on remote node. Reproducer in attached file . > For reproduce, run node1 first, second node 2, check logs. If remove cluster > group, for node1, all will be okay, but if stay it, will be error, see > attached log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service
[ https://issues.apache.org/jira/browse/IGNITE-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-4235: --- Attachment: node2.log node1.log > Can't get user exception if was on remote service > - > > Key: IGNITE-4235 > URL: https://issues.apache.org/jira/browse/IGNITE-4235 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.7 >Reporter: Dmitriy Govorukhin > Fix For: 2.0 > > Attachments: Reproducer.java, node1.log, node2.log > > > Can get user exception if was on remote node. Reproducer in attached file . > For reproduce, run node1 first, second node 2, check logs. If remove cluster > group, for node1, all will be okay, but if stay it, will be error, see > attached log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service
[ https://issues.apache.org/jira/browse/IGNITE-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-4235: --- Description: Can get user exception if was on remote node. Reproducer in attached file . For reproduce, run node1 first, second node 2, check logs. If remove cluster group, for deploy service1, for node1, all will be okay, but if stay it, will be error, see attached log. (was: Can get user exception if was on remote node. Reproducer in attached file . For reproduce, run node1 first, second node 2, check logs. If remove cluster group, for node1, all will be okay, but if stay it, will be error, see attached log.) > Can't get user exception if was on remote service > - > > Key: IGNITE-4235 > URL: https://issues.apache.org/jira/browse/IGNITE-4235 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.7 >Reporter: Dmitriy Govorukhin > Fix For: 2.0 > > Attachments: Reproducer.java, node1.log, node2.log > > > Can get user exception if was on remote node. Reproducer in attached file . > For reproduce, run node1 first, second node 2, check logs. If remove cluster > group, for deploy service1, for node1, all will be okay, but if stay it, will > be error, see attached log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service
[ https://issues.apache.org/jira/browse/IGNITE-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-4235: --- Description: Can get user exception if was on remote node. Reproducer in attached file. For reproduce, run node1 first, second node 2, check logs. If remove cluster group, for deploy service1, for node1, all will be okay, but if stay it, will be error, see attached log. (was: Can get user exception if was on remote node. Reproducer in attached file . For reproduce, run node1 first, second node 2, check logs. If remove cluster group, for deploy service1, for node1, all will be okay, but if stay it, will be error, see attached log.) > Can't get user exception if was on remote service > - > > Key: IGNITE-4235 > URL: https://issues.apache.org/jira/browse/IGNITE-4235 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.7 >Reporter: Dmitriy Govorukhin > Fix For: 2.0 > > Attachments: Reproducer.java, node1.log, node2.log > > > Can get user exception if was on remote node. Reproducer in attached file. > For reproduce, run node1 first, second node 2, check logs. If remove cluster > group, for deploy service1, for node1, all will be okay, but if stay it, will > be error, see attached log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service
[ https://issues.apache.org/jira/browse/IGNITE-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4235: Fix Version/s: (was: 2.3) > Can't get user exception if was on remote service > - > > Key: IGNITE-4235 > URL: https://issues.apache.org/jira/browse/IGNITE-4235 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.7 >Reporter: Dmitriy Govorukhin > Attachments: node1.log, node2.log, Reproducer.java > > > Can get user exception if was on remote node. Reproducer in attached file. > For reproduce, run node1 first, second node 2, check logs. If remove cluster > group, for deploy service1, for node1, all will be okay, but if stay it, will > be error, see attached log. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service
[ https://issues.apache.org/jira/browse/IGNITE-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-4235: --- Fix Version/s: (was: 2.0) 2.1 > Can't get user exception if was on remote service > - > > Key: IGNITE-4235 > URL: https://issues.apache.org/jira/browse/IGNITE-4235 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.7 >Reporter: Dmitriy Govorukhin > Fix For: 2.1 > > Attachments: node1.log, node2.log, Reproducer.java > > > Can get user exception if was on remote node. Reproducer in attached file. > For reproduce, run node1 first, second node 2, check logs. If remove cluster > group, for deploy service1, for node1, all will be okay, but if stay it, will > be error, see attached log. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
