[
https://issues.apache.org/jira/browse/TINKERPOP-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1375.
---------------------------------------
Resolution: Fixed
Fix Version/s: 3.2.2
3.1.4
Fixed this in both 3.1.4:
https://github.com/apache/tinkerpop/commit/6be28270598862a7a92b88a67d18e5e8f198b92b
and 3.2.2:
https://github.com/apache/tinkerpop/commit/9913d64cd1f9050b3d047b59dcea34ee8507d2dd
In both cases, a failed transaction could have created a situation where a
{{Frame}} was not released and if that {{Frame}} contained a Netty {{Bytebuf}}
(which it likely would) then Netty would report a warning that the {{Bytebuf}}
had not been released.
> Possible ByteBuf leak for certain transactional scenarios
> ---------------------------------------------------------
>
> Key: TINKERPOP-1375
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1375
> Project: TinkerPop
> Issue Type: Bug
> Components: server
> Affects Versions: 3.1.3, 3.2.1
> Reporter: stephen mallette
> Assignee: stephen mallette
> Fix For: 3.1.4, 3.2.2
>
>
> Not sure how to recreate this but certain transactional scenarios in sessions
> seem to generate a standard Netty "LEAK" log message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
