Inconsistent FileLoad error

[Soohoon]

Hi team, I'm implementing an webapp and experiencing an error as below.
BAS-010014 Cannot open file '/usr/local/neolane/nl6/var/SAS360/survey_data/655708__questionList.xml' with read access (errno=2, No such file or directory)
The error happens every other time when I load. (whenever I enter the link, it loads, but after I reload from the web browser it shows the error page showing the error page. when I reload once more then it loads again and it repeats.)

I tried checking the web server log and the log stacks only when the loading was successful. 
I'm assuming the file does not exist in one of the two application servers. the file is generated from a table by a workflow.
could anyone give any suggestions on this?

[Giriprasath-B]

Hi @Soohoon ,

Your understanding is correct. This issue is almost certainly caused by multiple application servers without shared file storage.

The behavior you described (page loads once, fails on refresh, then works again) usually means the webapp requests are being handled by different application servers behind a load balancer.

What’s happening is:

• The XML file is generated by a workflow on one application server only

• The file is written to
  /usr/local/neolane/nl6/var/SAS360/survey_data/, which is local to each server
  
  

• When the request goes to:

  • Server A → file exists → page loads

  • Server B → file does not exist → BAS-010014 error

This also explains why logs appear only when the page loads successfully.

Recommended fix:

Use shared storage for the generated files:

• Place the survey_data directory on a shared filesystem (NFS / NAS)

• Mount it on all application servers at the same path

This ensures the file is available regardless of which server handles the request and resolves the intermittent error.

If shared storage is not possible, the alternative is to generate or synchronize the file on all application servers, but this approach is harder to maintain and not recommended for production.

Conclusion:

This is not a workflow timing or webapp issue. It’s a file-system issue caused by multiple application servers using local storage. Configuring shared storage (or syncing the files) will fix the problem permanently