Same sourceMap variable batchId is used for different batches when disabling 'channel storage' on a batch and multi-thread channel source.
Tested with a big amount of batch files, with only 1 message per batch (so actually the batch mode is not needed). Each batch file is read by a multi-thread (5 threads) and source queue enabled channel, which sends each batch file to another batch and multi-thread channel.
The second channel (batch and multi-thread) is expected to receive each message from same batch in an unique thread, which is working fine, and an unique batchId identifier per batch file. However, this batchId could also be used by other thread of the same channel in other batch.
This means that it is not possible to use the batchId variable to uniquely identify which batch each message belongs to.
If 'channel storage' is set to raw or higher, the unique batchId is never repeated.
Same sourceMap variable batchId is used for different batches when disabling 'channel storage' on a batch and multi-thread channel source.
Tested with a big amount of batch files, with only 1 message per batch (so actually the batch mode is not needed). Each batch file is read by a multi-thread (5 threads) and source queue enabled channel, which sends each batch file to another batch and multi-thread channel.
The second channel (batch and multi-thread) is expected to receive each message from same batch in an unique thread, which is working fine, and an unique batchId identifier per batch file. However, this batchId could also be used by other thread of the same channel in other batch.
This means that it is not possible to use the batchId variable to uniquely identify which batch each message belongs to.
If 'channel storage' is set to raw or higher, the unique batchId is never repeated.
Imported Issue. Original Details: Jira Issue Key: MIRTH-4481 Reporter: nikkator Created: 2020-01-30T09:07:28.000-0800