Details
Bug
Resolved
Blocker
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|
|
||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue blocks PETALSDISTRIB-2 [ PETALSDISTRIB-2 ] |
| Attachment | PETALSCDK-83.patch [ 10731 ] |
| Summary | Memory leak because the JBIAcceptorManager.acceptorPool | Memory leak because the JBIAcceptorManager.acceptorPool is not freed |
| Priority | Blocker [ 1 ] |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Assignee | Mathieu Carrolle [ mcarrolle ] | Christophe DENEUX [ cdeneux ] |
| Description |
{{JBIAcceptorManager}} manages it acceptor thread pool using a {{ThreadPoolExecutor}}. {{ThreadPoolExecutor}} is designed to dispatch tasks to threads. The task are finished in the time.
But {{JBIAcceptorManager}} does not used tasks. It uses the ThreadFactory to create it's own thread, with its own method '{{run}}'. So this thread pool *MUST* be refactored to be a real thread pooo (for exemple, as an array of threads) |
{{JBIAcceptorManager}} manages it acceptor thread pool using a {{ThreadPoolExecutor}}. {{ThreadPoolExecutor}} is designed to dispatch tasks to threads. The task are finished in the time.
But {{JBIAcceptorManager}} does not used tasks. It uses the ThreadFactory to create it's own thread, with its own method '{{run}}'. So this thread pool *MUST* be refactored to be a real thread pool (for example, as an array of threads) |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.1.4 [ 10328 ] | |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 5.3.0 [ 10338 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |