We recently upgraded to Wisej 2.0 and we have a server that houses multiple website subdomains on some of them get an error message like this.
XML Parsing Error: no root element found Location: https://xxxxxxxxxxxxxxxx/app.wx?_sc=1553179109746 Line Number 1, Column 1:
If I kill the worker processes or www service the error is still there. But if I reboot the server it goes away for a while. This is our development server and we push new version of our product to it multiple times a day. So I don’t know if the error sometimes appears after we push a new version or just a period of time. I have things like browser cache disabled.
Any ideas?
14:44:17.306 000443 qx.core.Init: Load runtime: 443ms qx.min.js:1:1392318
14:44:17.319 000457 qx.core.Init: Main runtime: 12ms qx.min.js:1:1392318
14:44:17.324 000461 qx.core.Init: Finalize runtime: 4ms qx.min.js:1:1392318
14:44:17.847 XML Parsing Error: no root element found
Location: https://xxxxxxxxxxx/app.wx?_sc=1553179457318
Line Number 1, Column 1: app.wx:1:1
14:44:19.257 unreachable code after return statement[Learn More] qx.min.js:3:269
14:44:28.399 011537 qx.ui.core.queue.Manager: Flush Completed: 1 ms qx.min.js:1:1392318
14:44:29.963 013101 qx.ui.core.queue.Manager: Flush Completed: 0 ms qx.min.js:1:1392318
14:44:30.201 Source map error: request failed with status 404
Resource URL: https://xxxxxxxxxx/resource.wx/wisej.min.js?v=2.0.13.0
Source Map URL: vis.map[Learn More]
In chrome there is no error but I think its just the response that is blank.
We don’t use XML at all. But I have found some reports that Firefox has this issue in some cases https://ovinitech.blogspot.com/2019/01/xml-parsing-error-no-root-element-found.html
Do you see this on Firefox and Chrome? The “Source map error” and “unreachable code after return” are also Firefox bugs.
Please login first to submit.
