Compression is enabled on both servers (new and old). I removed compression on the new and restarted the site. Same issues. I checked the thread you linked also… nothing there to point me to why it is acting up. Tested the code on Lucee Express desktop version and it acted the same way. Leads me to wonder if this is a setting in the web server or tomcat?
I adjusted boncode settings and set FlushThreshold to 20000 as suggested elsewhere… still nothing. This is really becoming a challenge as I need cfscheduler to not timeout on long requests either. Flush was preventing that in CF9.
Does it also happen if you request Tomcat directly on port 8888 (e.g. http://service.bodepro.com:8888/service/test2.cfm) from the local machine? What is strange is that your code behaves just the same at trycf with ACF.
For flushing to work gzip compression needs to be turned off in both your web server and in Lucee (Lucee admin → Settings → Output → Compression. This is probably okay in development but in production you probably want to have gzip compression enabled at some point in your stack.
Not using a VPN. Both new and old machines are behind a NSA. New server is on a NAT, but the old machine is performing to spec. But to negate the NAT question, we tested on local host and the result is the same.
We moved the test file into Tomcat’s Root and tested there via 8888 (removing IIS from the mix) and we got the same result using only Tomcat/Lucee.
@Richx1
Have you enabled flushing in your BonCode settings. it is off by default.
If you used standard install you can add something like this to your setting file BonCodeAJP14.settings in C:\Windows <FlushThresholdTicks>500000</FlushThresholdTicks>
I had been updating the flushThreashold in the settings file in C:\lucee\AJP13 instead of windows. After updating and restarting services… the result is on target.