Oxygen XML Forum

Hello, Oxygen -

Our users connect to a CMS using WebDAV connections. Sometimes, people receive this error message:

Cannot open the specified file: Timeout waiting for connection from pool
(https://<file_path>)
Would you like to open it as a regular file?

If the user restarts Oxygen XML Editor, the problem goes away.

We already contacted our CMS vendor, and they explained that it was an endpoint client issue... so, now I'm contact you.

Thanks for your help.

Take care,
- Nick

Hello,

What version and build of Oxygen are you using (Help > About)?

Go to Options > Preferences, Network Connection Settings > HTTP(S)/WebDAV and increase the value of the Maximum number of simultaneous connections per host from 20 to 50. Restart Oxygen and check if it still happens.

Regards,
Adrian

Thanks! I let the user know, and it doesn't seem to be happening anymore... but let's see how thing go.

Take care,
- Nick

Hi Nick,

I found some time to try and reproduce the problem on my side. Could you tell us what particular operations the users are doing with Oxygen when the problem occurs?
Also, do the end users have a plugin installed in Oxygen which connects to the CMS using WebDav or are they using webdav directly?

Regards,
Radu

Hi Radu,
This timeout issue has reappeared, but at a larger scale after our CMS vendor upgraded to a new cloud service. Updating the Maximum number of simultaneous connections per host settings does not resolve the problem.

Where are the configuration files stored for the Oxygen XML Editor WebDAV connection settings? I'd like to review these and perhaps try to manually restore the default files.

Specifically, the issue occurs whenever a technical writer does not interact with Oxygen XML Editor for a period of time. Any node in the Data Source Explorer shows "Pending..." and then times out. Restarting the Oxygen XML Editor application resolves the problem. We connect directly to the CMS via WebDAV.

Thanks,
Nick

Hi Nick,

You are not the only ones having this problem with Oxygen and Easydita. I was in contact with someone from Easydita and I gave them information about how to enable logging in Oxygen to see why the HTTP connections start to fail. But I do not know if they found anything or not. My advice for you is to write to the CMS vendors and they will contact us if they come up with anything.
About this remark:

Where are the configuration files stored for the Oxygen XML Editor WebDAV connection settings? I'd like to review these and perhaps try to manually restore the default files.

In the Oxygen "Options" main menu you can reset the global options if you want. After this you will need to manually create again your Webdav data sources for the CMS connection. As an alternative each Oxygen Preferences page has a "Restore Defaults" button. But I do not think that this will help in any way.

Regards,
Radu

Thanks, Radu. It looks like this was perhaps due to a web server setting.