Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.1.0
-
Fix Version/s: 5.0.0
-
Component/s: Operation 'getAsAttachment', Operation 'mget'
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | A file can not be get as attachment and consume on another node | A file can not be get as attachment and consumed on another node |
| Priority | Blocker [ 1 ] |
| Fix Version/s | 5.0.0 [ 10931 ] | |
| Priority | Blocker [ 1 ] | Major [ 3 ] |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Description |
With a Petals topology composed of 2 containers:
1 - if a file is read with operation '{{getAsAttachment}}' or '{{meget}}' by the BC FileTranfer on a container, 2 - the file as attachment can not be processed by another service on the other container, 3 - the file as attachment can be correctly processed on a service located on the container where the BC FileTransfer is installed The problem is due to the '{{DataHandler}}' used to store the file as attachment. A '{{DataHandler}}' based on a '{{FileDataSource}}' is used. This data source transmits only a reference to the file. And so the file can not be accessed by this reference from another machine where the other Petals container is running. We should use an '{{ByteArrayDataSource}}' instead of '{{FileDataSource}}' even if the memory footprint is bigger. |
With a Petals topology composed of 2 containers:
1 - if a file is read with operation '{{getAsAttachment}}' or '{{mget}}' by the BC FileTranfer on a container, 2 - the file as attachment can not be processed by another service on the other container, 3 - the file as attachment can be correctly processed on a service located on the container where the BC FileTransfer is installed The problem is due to the '{{DataHandler}}' used to store the file as attachment. A '{{DataHandler}}' based on a '{{FileDataSource}}' is used. This data source transmits only a reference to the file. And so the file can not be accessed by this reference from another machine where the other Petals container is running. We should use an '{{ByteArrayDataSource}}' instead of '{{FileDataSource}}' even if the memory footprint is bigger. |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Fixed in branch petals-bc-filetransfer-5.0.x