[JBoss JIRA] (JBAS-9491) JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every asynchronous call
9:23 a.m.
Chris Rankin created JBAS-9491:
----------------------------------
Summary: JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for
every asynchronous call
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Assignee: Carlo de Wolf
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
9:27 a.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Chris Rankin commented on JBAS-9491:
------------------------------------
I can fix the JUnit test by reimplementing the {{equals()}} method as follows:
{code:Java}
@Override
public boolean equals(final Object obj) {
if (this == obj) {
return true;
}
if ((obj == null) || (obj.getClass() != getClass())) {
return false;
}
AsyncInvocationIdUUIDImpl other = (AsyncInvocationIdUUIDImpl) obj;
return uuid.equals(other.uuid);
}
{code}
But first, can anyone explain the original {{equals()}} implementation, please? Could
anything be relying on that other implementation's weirdness?
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Assignee: Carlo de Wolf
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
9:29 a.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Chris Rankin updated JBAS-9491:
-------------------------------
Description:
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
was:
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
Steps to Reproduce:
Basically, {{AsyncInvocationIdUUIDImpl}} fails the following JUnit test:
{code:Java}
@Test
public void testWithConcurrentHashMap() {
AsyncInvocationId uuid = new AsyncInvocationIdUUIDImpl();
Map<AsyncInvocationId, Boolean> map = new
ConcurrentHashMap<AsyncInvocationId, Boolean>();
map.put(uuid, Boolean.TRUE);
map.remove(uuid);
assertTrue(map.isEmpty());
}
{code}
This same test also fails with {{Hashtable}}, although it passes with {{HashMap}} and
{{LinkedHashMap}}.
was:
Basically, {{AsyncInvocationIdUUIDImpl}} fails the following JUnit test:
{code:Java}
@Test
public void testWithConcurrentHashMap() {
AsyncInvocationId uuid = new AsyncInvocationIdUUIDImpl();
Map<AsyncInvocationId, Boolean> map = new
ConcurrentHashMap<AsyncInvocationId, Boolean>();
map.put(uuid, Boolean.TRUE);
map.remove(uuid);
assertTrue(map.isEmpty());
}
{code}
This same test also fails with {{Hashtable}}, although it passes with {{HashMap}} and
{{LinkedHashMap}}.
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Assignee: Carlo de Wolf
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
9:29 a.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Chris Rankin updated JBAS-9491:
-------------------------------
Steps to Reproduce:
Basically, {{AsyncInvocationIdUUIDImpl}} fails the following JUnit test:
{code:Java}
@Test
public void testWithConcurrentHashMap() {
AsyncInvocationId uuid = new AsyncInvocationIdUUIDImpl();
Map<AsyncInvocationId, Boolean> map = new
ConcurrentHashMap<AsyncInvocationId, Boolean>();
map.put(uuid, Boolean.TRUE);
map.remove(uuid);
assertTrue(map.isEmpty());
}
{code}
This same test also fails with {{Hashtable}}, although it passes with {{HashMap}} and
{{LinkedHashMap}}.
was:
Basically, {{AsyncInvocationIdUUIDImpl}} fails the following JUnit test:
{code:Java}
@Test
public void testWithConcurrentHashMap() {
AsyncInvocationId uuid = new AsyncInvocationIdUUIDImpl();
Map<AsyncInvocationId, Boolean> map = new
ConcurrentHashMap<AsyncInvocationId, Boolean>();
map.put(uuid, Boolean.TRUE);
map.remove(uuid);
assertTrue(map.isEmpty());
}
{code}
This same test also fails with {{Hashtable}}, although it passes with {{HashMap}} and
{{LinkedHashMap}}.
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Assignee: Carlo de Wolf
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
10:05 a.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Carlo de Wolf updated JBAS-9491:
--------------------------------
Fix Version/s: Open To Community
Assignee: (was: Carlo de Wolf)
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
10:05 a.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Carlo de Wolf commented on JBAS-9491:
-------------------------------------
It is buggy code. If you post a pull request I'll merge it in.
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
10:31 a.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Chris Rankin commented on JBAS-9491:
------------------------------------
I don't have a git repository for you to pull from. Would a unified diff be OK
instead?
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
12:04 p.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Carlo de Wolf commented on JBAS-9491:
-------------------------------------
I would recommend creating one on github. There you can also fork the code from
https://github.com/jbossejb3/jboss-ejb3-async.
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
9:53 a.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Chris Rankin commented on JBAS-9491:
------------------------------------
I've created a fork called "rankinc/jboss-ejb3-async" and committed my
change to it.
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
12:37 p.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Carlo de Wolf commented on JBAS-9491:
-------------------------------------
Cool. Now you can pull request on the top right.
I do miss your JUnit test though. ;-)
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
12:37 p.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Carlo de Wolf edited comment on JBAS-9491 at 5/3/12 1:36 PM:
-------------------------------------------------------------
Cool. Now you can create a pull request on the top right.
I do miss your JUnit test though. ;-)
was (Author: wolfc):
Cool. Now you can pull request on the top right.
I do miss your JUnit test though. ;-)
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
12:41 p.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Chris Rankin commented on JBAS-9491:
------------------------------------
I'd be happy to add the JUnit test in as well if you could suggest the best place in
the tree to put it. The {{test/}} directory structure was not what I expected...
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
1:02 p.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Carlo de Wolf commented on JBAS-9491:
-------------------------------------
A simple class test can go into {{src/test/java/org/jboss/ejb3/async/impl}}. The other
tests are more functional.
Another alternative we sometimes use is the Jira identifier as a subpackage
{{src/test/java/org/jboss/ejb3/async/impl/jbas9491}}.
Having the test is more important than its location. :-)
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
3:17 a.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Chris Rankin commented on JBAS-9491:
------------------------------------
Added. And I've also created a pull request - I think...
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
6:02 a.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Carlo de Wolf commented on JBAS-9491:
-------------------------------------
Fixed by [~chrisjr] in component version 1.0.0-alpha-11.
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
6:02 a.m.
[
https://issues.jboss.org/browse/JBAS-9491?page=com.atlassian.jira.plugin....
]
Carlo de Wolf resolved JBAS-9491.
---------------------------------
Resolution: Done
JBoss 6.0.0-Final leaks an AsyncInvocationIdUUIDImpl object for every
asynchronous call
---------------------------------------------------------------------------------------
Key: JBAS-9491
URL: https://issues.jboss.org/browse/JBAS-9491
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: CentOS, Windows7
Reporter: Chris Rankin
Fix For: Open To Community
The {{AsyncInvocationIdUUIDImpl.equals()}} method is implemented as:
{code:Java}
@Override
public boolean equals(final Object obj) {
return uuid.equals(obj);
}
{code}
This implementation is incompatible with {{ConcurrentHashMap<AsyncInvocationId,
Boolean>}}, which means that {{AsyncInvocationMap.remove(id)}} does _not_ remove the
{{AsyncInvocationIdUUIDImpl}} object from the map at all. In other words, the
{{AsynchronousServerInterceptor.invoke()}} method is accumulating
{{AsyncInvocationIdUUIDImpl}} objects until the JVM's heap explodes.
--
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
4620
days inactive
4622
days old
15 comments
2 participants
participants (2)
-
Carlo de Wolf (JIRA) -
Chris Rankin (JIRA)