Attached test case that shows this issue.

Steps:

• Load welcomeICEfaces.iface
• In each inputFile components load a file ready for upload.
• Execute the first inputFile upload.
• Once the upload is finished, the file name in the second upload is cleared out.

It may be necessary for the test to use specify one of the submitOnUpload attribute settings to avoid this. From the TLD doc for inputFile:

Depending on the value of submitOnUpload, the inputFile may post its enclosing form, before and/or after the file upload occurs. Possible values are:

none
File uploading will not cause the inputFile's enclosing form, and any other of the form fields, to be submitted to the server.
preUpload
The inputFile's enclosing form, and any other of the form fields, will be submitted to the server, immediately before the file uploading begins.
postUpload
The inputFile's enclosing form, and any other of the form fields, will be submitted to the server, immediately after the file uploading finishes.
preAndPostUpload
The inputFile's enclosing form, and any other of the form fields, will be submitted to the server, both before and after the file uploading takes place.
This is to support two different use cases. Applications running in synchronous mode can not make use of server push, so to depict the beginning and the ending of the file upload requires browser initiated JSF lifecycles, accomplished via form submissions. As well, for some applications, it's desirable to submit other form fields when the user clicks on the file upload button, so that they may be processed together with the uploaded file.

Note: The default value is none.

The customer needs to use the preAndPostUpload value for this setting as they need to update the page when the upload begins and when the upload ends to facilitate their ui blocker/user notification code. Other values for this attribute would cause this functionality to no longer function correctly.