So this issue has been driving me up a wall for months, I put it on the back burner while finishing up development as the system is plenty stable on a single instance, but now that full production is around the corner I am needing to figure out the solution to this issue.
I am running multiple WAS instances on my server using always up, I can run all the instances just fine and the application works as expected except when it comes time to download/email a report generated on demand. If I have a single instance running everything works, but as soon as I start a second instance I can run the report (ie get it to display on the screen), but as when I try to click the PDF button to download (it is an HTML report) or run the xbasic code to email the report it doesn't work. Specifically when downloading and then trying to open the file it says the file is empty, and when trying to attach the pdf to the email there is no attachment. I have a feeling the issue has to do with session storage but I can't for the life of me figure out what is setup incorrectly.
When I have multiple instances running I can go find the report file that is generated in the session storage directory (this is in the general settings pane when configuring the WAS server) and the report opens just fine so it seems when downloading/emailing the system is not able to find this location. When emailing the report I am using the e.sessionFileKey to create a blob and then saving a new file in a directory within the Webroot folder, and again this all works fine with only one instance running.
Any thoughts on what I have setup incorrectly when it comes to the session storage? I didn't specifically setup the session storage files, in my config files for the instances it has the session storage set to "__default__" so I am assuming these session folders were generated based on that setting?
I am running multiple WAS instances on my server using always up, I can run all the instances just fine and the application works as expected except when it comes time to download/email a report generated on demand. If I have a single instance running everything works, but as soon as I start a second instance I can run the report (ie get it to display on the screen), but as when I try to click the PDF button to download (it is an HTML report) or run the xbasic code to email the report it doesn't work. Specifically when downloading and then trying to open the file it says the file is empty, and when trying to attach the pdf to the email there is no attachment. I have a feeling the issue has to do with session storage but I can't for the life of me figure out what is setup incorrectly.
When I have multiple instances running I can go find the report file that is generated in the session storage directory (this is in the general settings pane when configuring the WAS server) and the report opens just fine so it seems when downloading/emailing the system is not able to find this location. When emailing the report I am using the e.sessionFileKey to create a blob and then saving a new file in a directory within the Webroot folder, and again this all works fine with only one instance running.
Any thoughts on what I have setup incorrectly when it comes to the session storage? I didn't specifically setup the session storage files, in my config files for the instances it has the session storage set to "__default__" so I am assuming these session folders were generated based on that setting?
Comment