[
https://issues.jboss.org/browse/AS7-4056?page=com.atlassian.jira.plugin.s...
]
Richard Opalka updated AS7-4056:
--------------------------------
Description:
In our test suite we're doing the following usecase many times:
{code}
InitialContext ctx = new InitialContext(remoteJndiProperties);
try {
Object obj = ctx.lookup();
// do something with obj
} finally {
ctx.close();
}
{code}
Unfortunately this leads to huge thread leaks in remote naming :(
was:
In our test suite we're doing the following usecase many times:
InitialContext ctx = new InitialContext(remoteJndiProperties);
try {
Object obj = ctx.lookup();
// do something with obj
} finally {
ctx.close();
}
Unfortunately this leads to huge thread leaks :(
JBoss Remote Naming is leaking threads
--------------------------------------
Key: AS7-4056
URL:
https://issues.jboss.org/browse/AS7-4056
Project: Application Server 7
Issue Type: Bug
Components: Naming
Reporter: Richard Opalka
Assignee: Stuart Douglas
Fix For: 7.1.1.Final
In our test suite we're doing the following usecase many times:
{code}
InitialContext ctx = new InitialContext(remoteJndiProperties);
try {
Object obj = ctx.lookup();
// do something with obj
} finally {
ctx.close();
}
{code}
Unfortunately this leads to huge thread leaks in remote naming :(
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira