Bahmni connect Sync issues

Tags: #<Tag:0x00007fb85e31fec0>

(Arjun Khandelwal) #1

Hi, One of the implementations using Bahmni connect for sometime had reported couple of sync issues listed below. This causes the whole sync to be blocked.

  1. Issue with catchment 1 at the time of initial sync:

The initial sync gets stuck at a particular point with the progress bar doing back and forth but nothing progressing really. Refer the screenshot for what the screen and chrome console shows.

  1. Issue with catchment 2 at the time of upload sync after capturing some data in offline catchment2_issue2

Any suggestion on how to go about investigating these issues?

Also, i think the sync shouldn’t get blocked if some error is encountered. It should complete the sync and in the end present a report showing a list of patients not synced and errors associated with them.

(liam hahne) #2

I noticed that when there is a problem patient, it still seems to sync the other patients, but I definitely agree a report showing unsynced patients and errors is necessary.

I had sync issues when using duplicate secondary IDs

(Suman Maity) #3

Hi @arjun, Can you check the network call, for which its throwing the error. Also re-upload the 2nd image

(liam hahne) #4

(liam hahne) #5
Request URL: https://localhost/openmrs/ws/rest/v1/bahmnicore/patientprofile/
Request Method: POST
Status Code: 400 Bad Request
Remote Address: [::1]:443
Referrer Policy: no-referrer-when-downgrade
Cache-Control: max-age=0, no-store
Connection: close
Content-Encoding: gzip
Content-Type: application/json;charset=UTF-8
Date: Sat, 12 May 2018 18:54:02 GMT
Server: Apache-Coyote/1.1
Set-Cookie: reporting_session=B5B69E80EFD2B8E02E753A26A81F5CB3; path=/; domain=localhost; expires=Wed, 11-Jul-2018 18:54:01 GMT; secure; HttpOnly
Transfer-Encoding: chunked
Vary: Accept-Encoding
Accept: application/json
Accept-Encoding: gzip, deflate, br
Accept-Language: en-GB,en;q=0.9,es;q=0.8
Cache-Control: no-cache
Connection: keep-alive
Content-Length: 2516
Content-Type: application/json
Cookie: JSESSIONID=B5B69E80EFD2B8E02E753A26A81F5CB3; bahmni.user.location=%7B%22name%22%3A%22impl.balat%22%2C%22uuid%22%3A%22265e0732-aa46-4993-bf8b-c85bed90a70d%22%7D; bahmni.user=%22superman%22; app:clinical:grantProviderAccessData=%7B%22uuid%22%3A%22c1c26908-3f10-11e4-adec-0800271c1b75%22%7D; user.platform=%22chrome-app%22; app%3Aclinical%3AgrantProviderAccessData=%7B%22uuid%22%3A%22c1c26908-3f10-11e4-adec-0800271c1b75%22%2C%22display%22%3A%22superman%20-%20Super%20Man%22%2C%22links%22%3A%5B%7B%22rel%22%3A%22self%22%2C%22uri%22%3A%22http%3A%2F%2Flocalhost%2Fopenmrshttp%3A%2F%2Flocalhost%2Fopenmrs%2Fws%2Frest%2Fv1%2Fprovider%2Fc1c26908-3f10-11e4-adec-0800271c1b75%22%7D%5D%2C%22name%22%3A%22Super%20Man%22%7D; reporting_session=B5B69E80EFD2B8E02E753A26A81F5CB3
Disable-WWW-Authenticate: true
DNT: 1
Host: localhost
Origin: https://localhost
Pragma: no-cache
Referer: https://localhost/bahmni-connect/home/index.html
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/65.0.3325.181 Chrome/65.0.3325.181 Safari/537.36
{person: {names: [{givenName: "b", familyName: "b", display: "b b", preferred: false,…}],…},…}

(Dimitri R) #6

See also

  • BAH-605 - Clicking on Sync On Bahmni Connect gives an error saying “There was an unexpected issue on the server”

@ouiliam @mksrom could you both look at the above ticket and report either here or there whether this looks like anything we ever came across?

(Romain Buisson) #7

@mksd, this does not remind of any of the issues we had.

(liam hahne) #8

Maybe you have to log in at least once to Bahmni Online first.