[jira] [Comment Edited] (OLINGO-754) MemoryLeak when using Olingo in Wildfly

["Manuel Blechschmidt (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OLINGO-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909180#comment-14909180 ] 

Manuel Blechschmidt edited comment on OLINGO-754 at 9/28/15 1:17 PM:
---------------------------------------------------------------------

[~chandan.v.a] would it be possible to make this behavior configurable?

When exceptions are thrown I can't guarantee that ODataJPAContext.unsetContextInThreadLocal is always called.

Thanks for your support
    Manuel


was (Author: manuel_b):
[~chandan.v.a] would it be possible to make this behavior configurable?

When exceptions are thrown I can guarantee that ODataJPAContext.unsetContextInThreadLocal is always called.

Thanks for your support
    Manuel

> MemoryLeak when using Olingo in Wildfly
> ---------------------------------------
>
>                 Key: OLINGO-754
>                 URL: https://issues.apache.org/jira/browse/OLINGO-754
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-jpa
>    Affects Versions: V2 2.0.4
>         Environment: java 8, wildfly 8.2, Linux
>            Reporter: Manuel Blechschmidt
>
> The following code produces a memory leak in an application server:
> {code:title=org.apache.olingo.odata2.jpa.processor.core.ODataJPAContextImpl}
>   @Override
>   public void setODataContext(final ODataContext ctx) {
>     odataContext = ctx;
>     // This produces a memory leak on wildfly
>     setContextInThreadLocal(odataContext);
>   }
> {code}
> I removed the setContextInThreadLocal and it worked afterwards. I searched the whole code how this variable is normaly removed but was not able to find the clean way to solve this problem.



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