@AndyPayne@stevebaer
Is there still a limit to the timeout?
I have set the timeout to be about 500 secs and it still throws an error when I run a large study and it takes approximately 240 secs to run the definition.
Hi Anuj. There are two TIMEOUT values to be aware of. One is a HTTP timeout for the server (ie. rhino.compute) and the other is a HTTP timeout for the client (ie. Hops). The timeout dialog which is exposed in the Hops preferences sets the HTTP timeout value for the client. The server timeout is set via an environment variable on the machine where the server is running. To set this one, you have to set the value of the RHINO_COMPUTE_TIMEOUT environment variable. Does this help?
Sorry for the delay. The RHINO_COMPUTE_TIMEOUT can be set on whatever computer is running rhino.compute. You don’t have to do anything specific to the rhino.compute configuration. Basically, when it starts up, it looks to see if there is an environment variable stored on that machine called RHINO_COMPUTE_TIMEOUT and uses that value as the number of seconds to wait before timing out. If no variable is found, it defaults to 60 seconds.
To set the environment variable follow these steps:
Click in the Windows search bar and type “environment variable”. Click the line item that appears that says “Edit the system environment variables (control panel)” menu item.
This brings up a System Properties panel and there is a button towards the bottom which says “Environment Variable”. Click that to open up the dialog.
In the lower “System Variables” section, click “New” to create a new variable.
In the Variable Name input, type RHINO_COMPUTE_TIMEOUT
In the Variable Value input, type the number of seconds you want to use as your timeout value.
Click OK and then close out of all the dialogs you opened. Now restart your machine for the changes to take effect.
I went ahead and created the Environment Variable RHINO_COMPUTE_TIMEOUT and set the value for 600 and matched it on the grasshopper preferences timeout value to be 600 as well. I’m not sure if it worked but i don’t think it did or else i wouldn’t be getting this error and all of the HOPS components would be working.
I don’t think the Timeout is an issue here. Looking at your console output, it looks like most requests are being returned in under 3-4 seconds. What’s odd is that you seem to get a bunch of 200 response codes when you call hit the /io endpoint (which is what you want). Then you get one 200 response code after you hit the /grasshopper endpoint… but after that you get a 500 response code which basically looks like that server crashes. So something odd is going on. Can you post the file your using?