Page 1 of 1
Failed to send snapshot - standalone to multiuser viewer
Posted: 05 Aug 2025, 21:25
by sankar5m
Hi,
I am publishing the repository from Protege Standalone to the Essential viewer which is deployed as image in AWS ECS. I have got multiple post pointing to memory and i have upgraded my memory settings but still no luck. Please advise.
apache-tomcat - 9.0.207
Protege standalone Version 3.5 (Build 663)
Exception encountered during send
Failed to send snapshot to the Report Service :
No response from the Report Service at this URL
Re: Failed to send snapshot - standalone to multiuser viewer
Posted: 07 Aug 2025, 11:25
by neil.walsh
Hi,
We'll need some more information to help you here.
Firstly, when you say "s deployed as image in AWS ECS". Is this a Docker image you have created yourself? We do not currently provide a Docker image of Essential.
On the Publish screen in Protege, have you upgrade the path to the Viewer web application? This should match the URL you use to access Viewer in the browser.
Related, can you access Viewer in the browser ok? This should work without publishing with the default data snapashot. This will let you know things are running as expected. If you cannot access then check if you have opened the correct ports to access this (AWS security groups). For Tomcat, you'll need to open 8080 unless you are doing some mapping in your Docker configuration.
Thanks
Neil
Re: Failed to send snapshot - standalone to multiuser viewer
Posted: 13 Aug 2025, 20:05
by sankar5m
Thanks for responding. First apologize for delayed response, as forum URL is not working from our intranet and just now got whitelisted.
Current Situation:
1) I have moved the container orchestration from ECS to AWS EKS, to ease our troubleshooting.
2) I am successfully able to access the Essential viewer endpoint from our browser.
3) Tomcat 8080 port is open and hence we were able to access from webpage.
4) re-iterating that I am trying from standalone open-source protege version.
5) I also tried CURL POST to /reportService using this option curl -k -v disabling and i was able to see the logs on my EKS Logs. So for sure the connectivity is there. Only from protege its not able to connect.
Please advice.