This table lists the enhancements and fixes in fix pack version 6.0.2.1. |
Enhancements |
There are no enhancements in this fix pack. |
Fixes |
1 | 87361 | | FlatFile endpoint activiation failure when non default NS is used |
Symptom: If you specify a non-default namespace when performing discovery for example, http://www.ibm.com/customer, then the endpoint won't activate for inbound in FlatFiles adapter |
Resolution: Any namespace value can be specified during EMD process with the fix. |
|
2 | 69116 | JR26960 | Flat file adapter not posting files onto same queue |
Symptom: When multiple activation specs (with entirely different values for event directory, archive directory, etc.) are configured with FlatFiles adapter, it delivers the event to only one of the end-points. |
Resolution: The problem has been fixed and delivery of events will be done as per the configuration in the respective activation spec. |
|
3 | 87894 | JR26014 | FlatFile throwing NPE during restart |
Symptom: When the FlatFiles adapter is processing a file with SplitByDelimiter configuration and the adapter is stopped in the middle of processing, and later when the adapter is restarted, it generates a NullPointerException. |
Resolution: This has been fixed. |
|
4 | 88684 | JR26473 | Duplicate event processing when the application is restarted |
Symptom: During recovery of events in case of inbound, events that were processed in the last run are getting processed again. |
Resolution: The duplicate delivery of events issue has been resolved and the FlatFiles adapter now recovers normally as expected. |
|
5 | 88533 | JR26372 | FlatFileAppendException generated during Append operation in a clustered environment |
Symptom: In a clustered environment when simultaneous append requests come from multiple instances of FlatFiles adapter (deployed over various nodes) to the same file and when staging directory is used, the adapter generates, FlatFileAppendException. |
Resolution: This problem has been fixed and when simultaneous append requests are fired, the FlatFiles adapter instance which requests first in line, gains a control via lock, meanwhile the other instances keep waiting till the lock is released. |
|
6 | 88578 | JR26470 | Flat Files adapter cannot move events to archive folder on separate partitions |
Symptom: Flat File adapter cannot move events to archive folder if both event and archive directories are on different partitions |
Resolution: This has been fixed; the adapter can move files from event to archive directory even if both the directories are on different partitions. |
|