Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.1.0
-
Component/s: Operation 'get', Operation 'getAsAttachment', Operation 'mget'
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] |
| Fix Version/s | 5.0.0 [ 10931 ] |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify is the is locked or not by another program.
If the file is locked, an error is immediately returned. We should wait few seconds before to return the error. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program.
If the file is locked, an error is immediately returned. We should wait few seconds before to return the error. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program.
If the file is locked, an error is immediately returned. We should wait few seconds before to return the error. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program.
If the file is locked, an error is immediately returned. We should wait few seconds before to return the error. The error returned is a fault to be able to manage it in a process point of view. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program.
If the file is locked, an error is immediately returned. We should wait few seconds before to return the error. The error returned is a fault to be able to manage it in a process point of view. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program.
Error management: * for operations '{{get}}' and '{{getAsAttacgment}}', if the file is locked, an error is immediately returned. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', the locked file is not returned, and no error is raised. * we should wait few seconds before to return the error. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
| Summary | Wait few seconds before to declared a file as locked | Avoid to be blocked when trying to acces locked files |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program.
Error management: * for operations '{{get}}' and '{{getAsAttacgment}}', if the file is locked, an error is immediately returned. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', the locked file is not returned, and no error is raised. * we should wait few seconds before to return the error. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
If the file is locked, we should wait few seconds before to return an error. Error management: * for operations '{{get}}' and '{{getAsAttacgment}}', if the file is locked, an error is immediately returned. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', the locked file is not returned, and no error is raised. * we should wait few seconds before to return the error. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
If the file is locked, we should wait few seconds before to return an error. Error management: * for operations '{{get}}' and '{{getAsAttacgment}}', if the file is locked, an error is immediately returned. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', the locked file is not returned, and no error is raised. * we should wait few seconds before to return the error. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
If the file is locked, we should wait few seconds before to return an error. Error management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, an error is immediately returned. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', the locked file is not returned, and no error is raised. * we should wait few seconds before to return the error. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
If the file is locked, we should wait few seconds before to return an error. Error management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, an error is immediately returned. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', the locked file is not returned, and no error is raised. * we should wait few seconds before to return the error. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
If the file is locked, we should wait few seconds before to return an error. Error management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, an error is immediately returned. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', the locked file is not returned, and no error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
If the file is locked, we should wait few seconds before to return an error. Error management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, an error is immediately returned. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', the locked file is not returned, and no error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
If the file is locked, we should wait few seconds before to return an error. Error management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, we wait few seconds before to return an error. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', if the file is locked, we wait few seconds before to skip the file and continue with other files matching file patterns. No error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
If the file is locked, we should wait few seconds before to return an error. Error management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, we wait few seconds before to return an error. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', if the file is locked, we wait few seconds before to skip the file and continue with other files matching file patterns. No error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
New locked file management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, we wait few seconds before to return an error. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', if the file is locked, we wait few seconds before to skip the file and continue with other files matching file patterns. No error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
New locked file management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, we wait few seconds before to return an error. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', if the file is locked, we wait few seconds before to skip the file and continue with other files matching file patterns. No error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}'. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}'. Default value at component level: 5seconds This value can be change at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
New locked file management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, we wait few seconds before to return an error. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', if the file is locked, we wait few seconds before to skip the file and continue with other files matching file patterns. No error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}', defined in seconds. This waiting time is checked per period defined by '{{locking-poll-interval}}' in milliseconds. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}' and '{{locking-poll-interval}}'. Default value at component level: * {{locking-wait-time}}: 5seconds, * {{locking-poll-interval}}: 1000ms This value at can be changed at runtime. |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
New locked file management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, we wait few seconds before to return an error. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', if the file is locked, we wait few seconds before to skip the file and continue with other files matching file patterns. No error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}', defined in seconds. This waiting time is checked per period defined by '{{locking-poll-interval}}' in milliseconds. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}' and '{{locking-poll-interval}}'. Default value at component level: * {{locking-wait-time}}: 5seconds, * {{locking-poll-interval}}: 1000ms This value at can be changed at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
New locked file management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, we wait few seconds before to return an error. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', if the file is locked, we wait few seconds before to skip the file and continue with other files matching file patterns. No error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}', defined in seconds. This waiting time is checked per period defined by '{{locking-poll-interval}}' in milliseconds. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}' and '{{locking-poll-interval}}'. Default value at component level: * {{locking-wait-time}}: 5seconds, * {{locking-poll-interval}}: 1000ms Component level parameters can be changed at runtime. |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
New locked file management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, we wait few seconds before to return an error. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', if the file is locked, we wait few seconds before to skip the file and continue with other files matching file patterns. No error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}', defined in seconds. This waiting time is checked per period defined by '{{locking-poll-interval}}' in milliseconds. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}' and '{{locking-poll-interval}}'. Default value at component level: * {{locking-wait-time}}: 5seconds, * {{locking-poll-interval}}: 1000ms Component level parameters can be changed at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
New locked file management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, we wait few seconds before to return an error. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', if the file is locked, we wait few seconds before to skip the file and continue with other files matching file patterns. No error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}', defined in seconds. This waiting time is checked per period defined by '{{locking-poll-interval}}' in milliseconds. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}' and '{{locking-poll-interval}}'. Default value at component level: * {{locking-wait-time}}: 5seconds, * {{locking-poll-interval}}: 1000ms Component level parameters can be changed at runtime. |
| Description |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
New locked file management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, we wait few seconds before to return an error. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', if the file is locked, we wait few seconds before to skip the file and continue with other files matching file patterns. No error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}', defined in seconds. This waiting time is checked per period defined by '{{locking-poll-interval}}' in milliseconds. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}' and '{{locking-poll-interval}}'. Default value at component level: * {{locking-wait-time}}: 5seconds, * {{locking-poll-interval}}: 1000ms Component level parameters can be changed at runtime. |
When reading a file with operations {{get}}, {{getAsAttachment}} and {{mget}}, a check is done to verify if the file is locked or not by another program. If the file is locked, the operation is blocked until the file can be locked by the BC FileTransfer. And so timeout can occurs.
New locked file management: * for operations '{{get}}' and '{{getAsAttachment}}', if the file is locked, we wait few seconds before to return an error. The error returned is a fault to be able to manage it in a process point of view. * for operation '{{mget}}', if a file is locked, we wait few seconds before to skip the file and continue with other files matching file patterns. No error is raised. The waiting time could be set at SU level: '{{locking-wait-time}}', defined in seconds. This waiting time is checked per period defined by '{{locking-poll-interval}}' in milliseconds. If not set at SU level, the global configuration at component level is used: '{{locking-wait-time}}' and '{{locking-poll-interval}}'. Default value at component level: * {{locking-wait-time}}: 5seconds, * {{locking-poll-interval}}: 1000ms Component level parameters can be changed at runtime. |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Fix Version/s | 5.1.0 [ 10862 ] |
| Summary | Avoid to be blocked when trying to acces locked files | Avoid to be blocked when trying to access locked files |
| Link |
This issue depends on |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
New locked file management added in branch petals-bc-filetransfer-5.0.x
Setting the configuration of both parameters at runtime is delayed to 5.1.x