[jira] [Updated] (IGNITE-3862) GridServiceProxy invocation never times out

2017-02-17 Thread Anton Vinogradov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-3862:
-
Fix Version/s: (was: 2.0)
   1.9

> GridServiceProxy invocation never times out
> ---
>
> Key: IGNITE-3862
> URL: https://issues.apache.org/jira/browse/IGNITE-3862
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
>Priority: Critical
> Fix For: 1.9
>
>
> {{GridServiceProxy}} uses compute for remote invocation. In some cases an 
> exception on server side can cause the closure execution never finish. For 
> example, this happens when the exception is thrown during the serialization 
> of the result.
> Need to add additional {{IgniteServices.serviceProxy(..)}} method that will 
> additionally allow to specify custom timeout.
> This timeout should limit the number of retries (there is an infinite loop 
> now) and also be passed to {{callAsyncNoFailover}} to avoid hangs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-3862) GridServiceProxy invocation never times out

2016-11-16 Thread Dmitry Karachentsev (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitry Karachentsev updated IGNITE-3862:

Fix Version/s: (was: 1.8)
   2.0

> GridServiceProxy invocation never times out
> ---
>
> Key: IGNITE-3862
> URL: https://issues.apache.org/jira/browse/IGNITE-3862
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 2.0
>
>
> {{GridServiceProxy}} uses compute for remote invocation. In some cases an 
> exception on server side can cause the closure execution never finish. For 
> example, this happens when the exception is thrown during the serialization 
> of the result.
> Need to add additional {{IgniteServices.serviceProxy(..)}} method that will 
> additionally allow to specify custom timeout.
> This timeout should limit the number of retries (there is an infinite loop 
> now) and also be passed to {{callAsyncNoFailover}} to avoid hangs.



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

[jira] [Updated] (IGNITE-3862) GridServiceProxy invocation never times out

2016-11-16 Thread Dmitry Karachentsev (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitry Karachentsev updated IGNITE-3862:

Assignee: Semen Boikov  (was: Dmitry Karachentsev)

> GridServiceProxy invocation never times out
> ---
>
> Key: IGNITE-3862
> URL: https://issues.apache.org/jira/browse/IGNITE-3862
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 1.8
>
>
> {{GridServiceProxy}} uses compute for remote invocation. In some cases an 
> exception on server side can cause the closure execution never finish. For 
> example, this happens when the exception is thrown during the serialization 
> of the result.
> Need to add additional {{IgniteServices.serviceProxy(..)}} method that will 
> additionally allow to specify custom timeout.
> This timeout should limit the number of retries (there is an infinite loop 
> now) and also be passed to {{callAsyncNoFailover}} to avoid hangs.



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

[jira] [Updated] (IGNITE-3862) GridServiceProxy invocation never times out

2016-11-09 Thread Semen Boikov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Semen Boikov updated IGNITE-3862:
-
Assignee: Dmitry Karachentsev  (was: Semen Boikov)

> GridServiceProxy invocation never times out
> ---
>
> Key: IGNITE-3862
> URL: https://issues.apache.org/jira/browse/IGNITE-3862
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
>Priority: Critical
> Fix For: 1.8
>
>
> {{GridServiceProxy}} uses compute for remote invocation. In some cases an 
> exception on server side can cause the closure execution never finish. For 
> example, this happens when the exception is thrown during the serialization 
> of the result.
> Need to add additional {{IgniteServices.serviceProxy(..)}} method that will 
> additionally allow to specify custom timeout.
> This timeout should limit the number of retries (there is an infinite loop 
> now) and also be passed to {{callAsyncNoFailover}} to avoid hangs.



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

[jira] [Updated] (IGNITE-3862) GridServiceProxy invocation never times out

2016-09-08 Thread Valentin Kulichenko (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Valentin Kulichenko updated IGNITE-3862:

Description: 
{{GridServiceProxy}} uses compute for remote invocation. In some cases an 
exception on server side can cause the closure execution never finish. For 
example, this happens when the exception is thrown during the serialization of 
the result.

Need to add additional {{IgniteServices.serviceProxy(..)}} method that will 
additionally allow to specify custom timeout.

This timeout should limit the number of retries (there is an infinite loop now) 
and also be passed to {{callAsyncNoFailover}} to avoid hangs.

  was:
{{GridServiceProxy}} uses compute for remote invocation. In some cases an 
exception on server side can cause the closure execution never finish. For 
example, this happens when the exception is thrown during the serialization of 
the result.

Need to add additional {{IgniteServices.serviceProxy(..)}} method that will 
additionally allow to specify custom timeout.


> GridServiceProxy invocation never times out
> ---
>
> Key: IGNITE-3862
> URL: https://issues.apache.org/jira/browse/IGNITE-3862
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.8
>
>
> {{GridServiceProxy}} uses compute for remote invocation. In some cases an 
> exception on server side can cause the closure execution never finish. For 
> example, this happens when the exception is thrown during the serialization 
> of the result.
> Need to add additional {{IgniteServices.serviceProxy(..)}} method that will 
> additionally allow to specify custom timeout.
> This timeout should limit the number of retries (there is an infinite loop 
> now) and also be passed to {{callAsyncNoFailover}} to avoid hangs.



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