[jboss-jira] [JBoss JIRA] (JBAS-9474) Asynchronous SLSBs are leaked if they execute too quickly

[Chris Rankin (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677153#comment-12677153 ] 

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