6:05 p.m.
Chris Rankin created JBAS-9474:
----------------------------------
Summary: 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
Environment: Linux x86_64, JDK 1.6.0_31
Reporter: Chris Rankin
Assignee: Carlo de Wolf
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
6:05 p.m.
[
https://issues.jboss.org/browse/JBAS-9474?page=com.atlassian.jira.plugin....
]
Chris Rankin updated JBAS-9474:
-------------------------------
Attachment: testboss.tar.bz2
Maven project containing sample WAR source.
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
Environment: Linux x86_64, JDK 1.6.0_31
Reporter: Chris Rankin
Assignee: Carlo de Wolf
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
5:39 p.m.
[
https://issues.jboss.org/browse/JBAS-9474?page=com.atlassian.jira.plugin....
]
Chris Rankin updated JBAS-9474:
-------------------------------
Affects Version/s: 6.1.0
Forum Reference: https://community.jboss.org/thread/196168 (was:
https://community.jboss.org/thread/196168)
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
Assignee: Carlo de Wolf
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
9:27 a.m.
[
https://issues.jboss.org/browse/JBAS-9474?page=com.atlassian.jira.plugin....
]
Carlo de Wolf updated JBAS-9474:
--------------------------------
Fix Version/s: Open To Community
Assignee: (was: Carlo de Wolf)
Forum Reference: https://community.jboss.org/thread/196168 (was:
https://community.jboss.org/thread/196168)
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
9:05 p.m.
[
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
4:28 p.m.
[
https://issues.jboss.org/browse/JBAS-9474?page=com.atlassian.jira.plugin....
]
Chris Rankin edited comment on JBAS-9474 at 3/15/12 5:28 PM:
-------------------------------------------------------------
Porting my WAR file from JBoss 6 to JBoss 7 is hardly a trivial undertaking. The removal
of {{@Service}} _alone_ is causing me grief, because my MBean _needs_ to access EJBs in
order to do anything useful. (A round of applause please for utterly _pointless_ examples
of {{@Singleton}} MBeans in JBoss 6 which only return a {{String}} that reads "Hello
World"...! {{@Service}} may be deprecated in JBoss 6, but it's still the only
practical way that actually *works*.)
Does JBoss 7 allow you to register MBeans that have EJBs injected into them?
was (Author: chrisjr):
Porting my WAR file from JBoss 6 to JBoss 7 is hardly a trivial undertaking. The
removal of {{@Service}} _alone_ is causing me grief, because my MBean _needs_ to access
EJBs in order to do anything useful. (A round of applause please for utterly _pointless_
examples of {{@Singleton}} MBeans in JBoss 6 which only return a {{String}} that reads
"Hello World"...! Using {{@Service}}s may be deprecated in JBoss 6, but it's
still the only practical way that actually *works*.)
Does JBoss 7 allow you to register MBeans that have EJBs injected into them?
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
4:28 p.m.
[
https://issues.jboss.org/browse/JBAS-9474?page=com.atlassian.jira.plugin....
]
Chris Rankin commented on JBAS-9474:
------------------------------------
Porting my WAR file from JBoss 6 to JBoss 7 is hardly a trivial undertaking. The removal
of {{@Service}} _alone_ is causing me grief, because my MBean _needs_ to access EJBs in
order to do anything useful. (A round of applause please for utterly _pointless_ examples
of {{@Singleton}} MBeans in JBoss 6 which only return a {{String}} that reads "Hello
World"...! Using {{@Service}}s may be deprecated in JBoss 6, but it's still the
only practical way that actually *works*.)
Does JBoss 7 allow you to register MBeans that have EJBs injected into them?
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
5233
days inactive
5244
days old
6 comments
3 participants
participants (3)
-
Carlo de Wolf (JIRA) -
Chris Rankin (JIRA)
-
jaikiran pai (JIRA)