Hi all,
I have a PASOE endpoint in v12.2.13 / Windows Server 2019 Standard that is running the web transport. I added a file upload capability to a WebSpeed screen in this endpoint, using a JavaScript XMLHttpRequest. The files are uploaded successfully but after a couple of hours all subsequent calls to the endpoint - not just the upload function - start to return a 500 error. It seems the upload is definitely to blame, as I am the only one using this endpoint and I'm not doing anything else. While troubleshooting I have been leaving it alone after uploading the files, then coming back in a couple of hours and trying to log into the application. It's as if there's a long-running thread that is getting timed-out by something other than PASOE, and getting into a state where it can't service any new requests. Multiple uploads (= multiple XMLHttpRequests) are possible... it's coming back to it after an extended period of inactivity that is the problem.
Thinking the problem might lie with the XMLHttpRequest, I set a timeout of 10 seconds on it and I also added an abort in the 'onreadystatechange' trigger. This didn't fix it. Next up, I noticed that the endpoint didn't have idle resource checking enabled, so I set idleResourceTimeout in openedge.properties to 30 minutes and bounced the endpoint. Related settings, which I didn't change, are:
idleSessionTimeout - 30 minutes
idleAgentTimeout - 30 minutes
idleConnectionTimeout - 1 minute
I repeated my test cycle and got the same result. I was hoping that by enabling idle resource checking, I might get in ahead of whatever is messing the threads up, and shut things down cleanly. I'm out of ideas at this point - any thoughts on what I could try next?
TIA
Tarby
I have a PASOE endpoint in v12.2.13 / Windows Server 2019 Standard that is running the web transport. I added a file upload capability to a WebSpeed screen in this endpoint, using a JavaScript XMLHttpRequest. The files are uploaded successfully but after a couple of hours all subsequent calls to the endpoint - not just the upload function - start to return a 500 error. It seems the upload is definitely to blame, as I am the only one using this endpoint and I'm not doing anything else. While troubleshooting I have been leaving it alone after uploading the files, then coming back in a couple of hours and trying to log into the application. It's as if there's a long-running thread that is getting timed-out by something other than PASOE, and getting into a state where it can't service any new requests. Multiple uploads (= multiple XMLHttpRequests) are possible... it's coming back to it after an extended period of inactivity that is the problem.
Thinking the problem might lie with the XMLHttpRequest, I set a timeout of 10 seconds on it and I also added an abort in the 'onreadystatechange' trigger. This didn't fix it. Next up, I noticed that the endpoint didn't have idle resource checking enabled, so I set idleResourceTimeout in openedge.properties to 30 minutes and bounced the endpoint. Related settings, which I didn't change, are:
idleSessionTimeout - 30 minutes
idleAgentTimeout - 30 minutes
idleConnectionTimeout - 1 minute
I repeated my test cycle and got the same result. I was hoping that by enabling idle resource checking, I might get in ahead of whatever is messing the threads up, and shut things down cleanly. I'm out of ideas at this point - any thoughts on what I could try next?
TIA
Tarby
Last edited: