You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (Jira)" <ji...@apache.org> on 2020/08/04 10:23:00 UTC
[jira] [Resolved] (SLING-9626) "Writer has already been closed"
exception in GraphQLServlet
[ https://issues.apache.org/jira/browse/SLING-9626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-9626.
----------------------------------------
Fix Version/s: GraphQL Core 0.0.6
Assignee: Bertrand Delacretaz
Resolution: Fixed
Fixed in commit 91b0817
> "Writer has already been closed" exception in GraphQLServlet
> ------------------------------------------------------------
>
> Key: SLING-9626
> URL: https://issues.apache.org/jira/browse/SLING-9626
> Project: Sling
> Issue Type: Bug
> Components: GraphQL
> Affects Versions: GraphQL Core 0.0.4
> Reporter: Evgeny Tugarev
> Assignee: Bertrand Delacretaz
> Priority: Major
> Fix For: GraphQL Core 0.0.6
>
>
> The GraphQLServlet shouldn't call {{response.getWriter().flush()}} as the {{JsonWriter}} used by the {{JsonSerializer}} implements {{Closeable}} and as such [closes the Writer|https://github.com/jdereg/json-io/blob/cf849f15460decf10a8a320390de11965bb5996b/src/main/java/com/cedarsoftware/util/io/JsonWriter.java#L2413].
> This causes a "Writer has already been closed" Exception when {{flush()}} is called.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)