09-06-2019, 09:47 PM
Hi Dan
Sorry for not making myself clear! The Intraweb server and CGIRunner applications (A & B) are all on the same physical box.
More detail ... both Intrawweb servers handle project funding applications, but for different projects with different requirements. But their basic functions are similar ... applicants log in, input data to a number of forms and upload a number of pdfs to support their application. When the applicant clicks the Print/Preview button the CGIRunner is called (with parameters). It creates a series of report pages as pdfs plus gets the uploaded pdf documents and "stitches" them all together to produce the application document. It is saved to the user's cache folder and the CGIRunner terminates. The Intraweb server then displays the pdf. When it works it works great.
The final pdf documents being produced by A average about 30 pages. Those produced by B can be as big as 1,100 pages. So the issue shows up pretty quickly when B is live. The Print/Preview stops working on ServerB. And when it does the Print/Preview on ServerA also stops. If only ServerA is live then the issue takes much longer to eventuate. So my inclination is that it is some sort of "resource" issue. The difficulty is trying to figure out what that "resource" is, since when it is exhausted it affects both Intraweb servers ability to call their CGIRuner applications.
Sorry for not making myself clear! The Intraweb server and CGIRunner applications (A & B) are all on the same physical box.
More detail ... both Intrawweb servers handle project funding applications, but for different projects with different requirements. But their basic functions are similar ... applicants log in, input data to a number of forms and upload a number of pdfs to support their application. When the applicant clicks the Print/Preview button the CGIRunner is called (with parameters). It creates a series of report pages as pdfs plus gets the uploaded pdf documents and "stitches" them all together to produce the application document. It is saved to the user's cache folder and the CGIRunner terminates. The Intraweb server then displays the pdf. When it works it works great.
The final pdf documents being produced by A average about 30 pages. Those produced by B can be as big as 1,100 pages. So the issue shows up pretty quickly when B is live. The Print/Preview stops working on ServerB. And when it does the Print/Preview on ServerA also stops. If only ServerA is live then the issue takes much longer to eventuate. So my inclination is that it is some sort of "resource" issue. The difficulty is trying to figure out what that "resource" is, since when it is exhausted it affects both Intraweb servers ability to call their CGIRuner applications.