[jira] [Updated] (GEODE-9411) ExecutionHandlerContext.getExceptionResponse() should not close the client connection on IOException
[
https://issues.apache.org/jira/browse/GEODE-9411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-9411:
-
Labels: pull-request-available unreleased (was: pull-request-available
unable)
> ExecutionHandlerContext.getExceptionResponse() should not close the client
> connection on IOException
>
>
> Key: GEODE-9411
> URL: https://issues.apache.org/jira/browse/GEODE-9411
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> In {{ExecutionHandlerContext.getExceptionResponse()}} we always return a
> response of some kind to the client, except for if we hit an {{IOException}}
> during command execution, in which case we close the client connection and
> don't send any reply. This behaviour is leftover from the now-removed
> function execution approach that Radish was taking, so should also be removed.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9411) ExecutionHandlerContext.getExceptionResponse() should not close the client connection on IOException
[
https://issues.apache.org/jira/browse/GEODE-9411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-9411:
-
Labels: pull-request-available unable (was: pull-request-available)
> ExecutionHandlerContext.getExceptionResponse() should not close the client
> connection on IOException
>
>
> Key: GEODE-9411
> URL: https://issues.apache.org/jira/browse/GEODE-9411
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: pull-request-available, unable
> Fix For: 1.15.0
>
>
> In {{ExecutionHandlerContext.getExceptionResponse()}} we always return a
> response of some kind to the client, except for if we hit an {{IOException}}
> during command execution, in which case we close the client connection and
> don't send any reply. This behaviour is leftover from the now-removed
> function execution approach that Radish was taking, so should also be removed.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9411) ExecutionHandlerContext.getExceptionResponse() should not close the client connection on IOException
[
https://issues.apache.org/jira/browse/GEODE-9411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9411:
--
Labels: pull-request-available (was: )
> ExecutionHandlerContext.getExceptionResponse() should not close the client
> connection on IOException
>
>
> Key: GEODE-9411
> URL: https://issues.apache.org/jira/browse/GEODE-9411
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: pull-request-available
>
> In {{ExecutionHandlerContext.getExceptionResponse()}} we always return a
> response of some kind to the client, except for if we hit an {{IOException}}
> during command execution, in which case we close the client connection and
> don't send any reply. This behaviour is leftover from the now-removed
> function execution approach that Radish was taking, so should also be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
