[arquillian-issues] [JBoss JIRA] (ARQ-1992) ServletTestRunner is leaking memmory

[Tomaz Cerar (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar updated ARQ-1992:
-----------------------------
    Description: 
ServletTestRunner saves ThreadLocal reference to ServletContex in its init() method,
and clears it in destroy(). 
Problem is that thread that calls init and thread that call destroy() are not guaranteed to be the same thread.

In wildfly/undertow undeploy/server shotdown is executed in different thread than he one that was used to call servlet init first.

reproducer and some evaluation on the bug can be found at https://github.com/wildfly/wildfly/issues/8263

  was:
ServletTestRunner saves reference to ServletContex in its init() method,
and clears it in destroy(). 
Problem is that thread that calls init and thread that call destroy() are not guaranteed to be the same thread.

In wildfly/undertow undeploy/server shotdown is executed in different thread than he one that was used to call servlet init first.

reproducer and some evaluation on the bug can be found at https://github.com/wildfly/wildfly/issues/8263



> ServletTestRunner is leaking memmory
> ------------------------------------
>
>                 Key: ARQ-1992
>                 URL: https://issues.jboss.org/browse/ARQ-1992
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Base Implementation
>    Affects Versions: 1.1.9.Final
>         Environment: Using arquillian with servlet protocol
>            Reporter: Tomaz Cerar
>            Priority: Critical
>
> ServletTestRunner saves ThreadLocal reference to ServletContex in its init() method,
> and clears it in destroy(). 
> Problem is that thread that calls init and thread that call destroy() are not guaranteed to be the same thread.
> In wildfly/undertow undeploy/server shotdown is executed in different thread than he one that was used to call servlet init first.
> reproducer and some evaluation on the bug can be found at https://github.com/wildfly/wildfly/issues/8263



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)