Thanks for the explanations. Now that I understand the technical foundation better, I would like to get a better sense of the ‘logical coupling’.
I still get the same error as indicated by the stacktrace above. In the access log I see this request: “GET /openelis/ws/feed/patient/18 HTTP/1.1” 500 5859 25
So indeed a resources does not exists. This stacktrace appears every 15 seconds (as currently configured), so it makes it almost impossible to detect other problems/stacktraces in the log.
The URL for this patient with ID 18 does not exist, but none of the parent pathes for the URL do either; like /openelis/es, /openelis/ws/feed/, … (but htis might be ok).
Now for tests I’ve played around with my installation quite a bit. Started and stopped OpenELIS and OpenMRS independent from each other. Exexcuted SQL statements (e.g. deletes to get rid of my temporary test data) in the OpenMRS DB. Could this be the reason for this 'instability’?
Can you recommend a way how I could ‘clear’ the backlog for these feeds to get rid of these messages/errors?