Description
There is a timeout setting that you may be able to utilize. This has not been tested and confirmed by support.
You would need to make a change the nodelocal.js file. You will also want to be sure make a copy/backup of this nodelcoal.js first as if it is incorrect, it will cause the entire Syracuse web server to stop working.
- Have all users exit Sage X3
- On the Syracuse server, browse to ..\SyracuseComponent\syracuse\bin and locate the file nodelocal.js
- Make a copy of the nodelocal.js as a backup
- Once a copy has been made, right-click the nodelocal.js file and select Edit
- Add to the Sessions tag
"session": {
"timeout": 20, //minutes
"checkInterval": 60, //seconds
// session timeout (minutes - decimals allowed) for stateless (web service) requests.
statelessTimeout: 1,
// session timeout (minutes - decimals allowed) for api1 requests.
api1SessionTimeout: 2,
"auth": "basic"
},
- Save the nodelocal.js file
- Restart the Syracuse Windows service
Note: If the Syracuse service does not start or if logging into Sage X3 generates errors, this generally means the nodelocal.js file was edited incorrectly. Restore the copy and try again.
Resolution
- If you are using .NET to call the X3 web service, you can change the timeout.
- For example:
- x3WebService.Timeout = 6000000; // Default is 100000
- You can also change the timeout that web server is using(On Web server 9.7 and higher)
- Open Administration, Servers, Hosts.
- Edit your host record.
- Change the Return request timeout from 30 to a higher number depend on your need.