Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.3.0
-
Fix Version/s: 3.3.1
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Description |
In a HA use case where several BC FileTranfer will consume concurrently the same file:
# the file will be really consumed by only one BC FileTranfer, # other BC FileTranfer detect through a lock file that the file is already consumed by the other BC FileTranfer. MONIT traces must be generated only for the step #1, not for the step #2 |
In a HA use case where several BC FileTranfer will consume concurrently the same file:
# the file will be really consumed by only one BC FileTranfer, # other BC FileTranfer detect through a lock file that the file is already consumed by the other BC FileTranfer. MONIT traces must be generated only for the step #1, not for the step #2 |
| Description |
In a HA use case where several BC FileTranfer will consume concurrently the same file:
# the file will be really consumed by only one BC FileTranfer, # other BC FileTranfer detect through a lock file that the file is already consumed by the other BC FileTranfer. MONIT traces must be generated only for the step #1, not for the step #2 |
In a HA use case where several BC FileTranfer will consume concurrently the same file:
# the file will be really consumed by only one BC FileTranfer, # other BC FileTranfer detect through a lock file that the file is already consumed by the other BC FileTranfer. \\ MONIT traces must be generated only for the step #1, not for the step #2 |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 3.3.1 [ 10583 ] | |
| Resolution | Fixed [ 1 ] |