Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 4.2.0
-
Fix Version/s: 5.0.0
-
Component/s: Configuration, Documentation, Recovery
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 4.2.1 [ 10413 ] | |
| Priority | Minor [ 4 ] |
| Description |
The recovery service used several properties to drive its processing.
These processing are not defined in the default local container configuration (ie. {{server.properties}}), and they are not documented on the on-line documentation |
The recovery service used several properties to drive its processing.
These processing parameters are not defined in the default local container configuration (ie. {{server.properties}}), and they are not documented on the on-line documentation |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Component/s | Configuration [ 10257 ] | |
| Component/s | Documentation [ 10079 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
The recovery service properties have been added to the default local container configurations (ie. server.properties), in trunk.
The user documentation has been completed.
The parameter 'petals.recovery.maxpoolsize' has been removed because the system recovery thread pool is only driven by the core pool size (because it uses an unbounded queue).