+++ This bug was initially created as a clone of Bug #1088603 +++
When the XmlDataImporter generates and subsequently deletes a temp file (e.g. for a large message) it will continue trying to delete that same file whenever it imports another message and log spurious WARN messages when it can't.
I have written a RN entry for the 'Known Issues' section as the fix is not included in ER3. For the product's final release, the following RN text can be published:
"When the `XmlDataImporter` was importing large messages, spurious 'WARN' messages were logged. The root cause of this issue was that when importing sufficiently large messages, the `XmlDataImporter` created a temporary file and deleted it when the import task was complete. When importing another large message, the `XmlDataImporter` function tried to delete the temporary file, which no longer existed, and so logged the WARN message. The handling of temporary files in the `XmlDataImporter` function has now been modified and as a result, spurious WARN messages are no longer logged."
Should be fixed by upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1064596 for DR2
Already verified for EAP 6.2.3.CR2 where code of XmlDataImporter is the same as for EAP 6.3.0.ER7. Verified!