Hi Alan, Thanks for that. It is definitely the apache piece causing the issue as I did a little loop test with the cffush returning something from jetty to apache every 15 seconds and then the page will run for as many loops as I want without erroring providing there is some STDoutput being passed back.
So to get around wanting it to report to the screen I have just rigged a thread to do the work in the background whilst the master thread runs a look while the other thread has not reached COMPLETED status which just pushes a byte of data back to apache. Works for now before I can spend more time on it. Regards, Lee On 18 January 2016 at 18:49, 'Alan Holden' via Open BlueDragon < [email protected]> wrote: > Lee; > > Good luck, I'll bet that there's some log entries which might confirm that > suspicion. > > I'm not experienced in the following department, but I'm pretty sure you > can also run OpenBD cfm scripts in a command-line manner, outside a web > browser connection. > > IOW, folks would use the CFML/Apache part just to upload the import data > (assuming that's what you're doing). Once the data has arrived, thank the > user and complete the web page request. > > Then "offline", run the importing script via OpenBD OS command-line. Your > script would send an email (for example) when the process was complete. You > wouldn't need to keep Apache/browser/user waiting while you do everything. > > Granted, I didn't do any research here - to see if I remember this feature > correctly or if it's still around. > > Al > > > > On 1/17/2016 12:06 AM, Lee Fortnam wrote: > > Hi Alan, > > Thanks for the reply. I run a number of database imports which at times > can take 30 mins plus. > > The debug info is passed back to the screen purely for info purposes. The > scripts are still completing in jetty after the current 60 seconds so it is > not jetty that appears to be timing out but Apache giving up waiting. > > I had tried the resolution you recommended but to no avail, I will > continue with further investigation. > > Thanks, > > Lee > > On Sunday, 17 January 2016, 'Alan Holden' via Open BlueDragon < > [email protected]> wrote: > >> I don't know which Apache Proxy you are using, or the reason that you >> would have a web page running longer than 60 seconds, but this message >> ("The proxy server received...") is probably coming from Apache. You can >> search on that phrase for a lot of reasons and possible fixes, for Apache's >> message at least. >> >> If Jetty is just taking too long - and Apache has given up waiting, then >> it looks like you can add or edit something like this in your Apache >> httpd.conf file: >> Resolution: >> Timeout 2400 >> ProxyTimeout 2400 >> ProxyBadHeader Ignore >> >> The 2400 seconds is just a number you can set yourself. Be sure to >> restart the Apache service. >> >> If Jetty is actually breaking, then the real cause of the error might be >> in Jetty's logs, not Apache's. >> >> HTH, >> Al >> >> On 1/16/2016 12:36 PM, Lee wrote: >> >> Hi All, >> >> I have an AWS server running CentOS and OpenBDJam 3.1 but there default >> settings between Jetty and Apache appear to be timing out certain pages >> resulting in the error message: >> >> Proxy Error >> >> The proxy server received an invalid response from an upstream server. >> >> This is on any page that runs longer than 60 seconds, I have tried to >> find the right setting but cannot find the right combination or location to >> put it. >> >> Pages work find under my old apache / tomcat setup with 3.1 but not the >> new ones. >> >> Any direction you guys could provide would be much appreciated. >> >> Kind Regards, >> >> Lee >> -- >> -- >> online documentation: http://openbd.org/manual/ >> http://groups.google.com/group/openbd?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Open BlueDragon" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> -- >> online documentation: http://openbd.org/manual/ >> http://groups.google.com/group/openbd?hl=en >> >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "Open BlueDragon" group. >> To unsubscribe from this topic, visit >> <https://groups.google.com/d/topic/openbd/6PCYUz3Bfd8/unsubscribe> >> https://groups.google.com/d/topic/openbd/6PCYUz3Bfd8/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > -- > -- > online documentation: http://openbd.org/manual/ > http://groups.google.com/group/openbd?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Open BlueDragon" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > -- > -- > online documentation: http://openbd.org/manual/ > http://groups.google.com/group/openbd?hl=en > > --- > You received this message because you are subscribed to a topic in the > Google Groups "Open BlueDragon" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/openbd/6PCYUz3Bfd8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
