[
https://issues.jboss.org/browse/JBAS-9474?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-9474:
------------------------------------
Chris, there's no more development going on in JBoss AS6 or previous releases. All the
development is now happening in AS7
http://www.jboss.org/as7. We just released 7.1.1.Final
last Friday. 7.1.x is a Java EE6 Full Profile certified server, so try out your
application there and see if it works fine there.
Asynchronous SLSBs are leaked if they execute too quickly
---------------------------------------------------------
Key: JBAS-9474
URL:
https://issues.jboss.org/browse/JBAS-9474
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, 6.1.0
Environment: Linux x86_64, JDK 1.6.0_31
Reporter: Chris Rankin
Fix For: Open To Community
Attachments: testboss.tar.bz2
I have created a SLSB which exports a single asynchronous service, and a singleton bean
which invokes it via a TimerService. Once every minute, the singleton executes the SLSB 15
times via a loop. If the asynchronous service executes "too quickly" (e.g. 500ms
or less) then the asynchronous thread is destroyed and the SLSB is leaked, along with all
of its resources. Over time, these SLSB instances force an OutOfMemory exception.
However, if the asynchronous service is "slow enough" then the asynchronous
thread stays in the pool and the SLSB can be reused. This is the behaviour that I want,
although I would obviously still want the service to execute as quickly as possible.
--
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