Sometimes Failing to Load Neighbourhood Arcs

[everbeek]

For SNOMED Qualifier Value root concept, if you load only 20 of the 50 concepts in the term neighbourhood mode, it fails to load any of the arcs. If you load all 50, it will succeed appropriately.

http://bioportal.bioontology.org/ontologies/46896/?p=terms&conceptid=362981000#visualization

Make sure to look at the JS console in Chrome for this. There are likely hints there.

[everbeek]

It all looks like server latency leading to timeouts. I raised the timeout from 10 seconds to 15 seconds, and that reduced (eliminated) occurrences in dev context. I am deploying to bioportal-integration-test to see how it works up there. If it works for the terms above, I will deploy to production and tell the folks at NCBO, as well as explain to them the source of the problem. Can their servers be adjusted to allow for any service to be a bulk call? That might lead to unintentional DoS though...

[everbeek]

No, I change my mind. There's no way it's the delay. The problem still occurs in stage after the timeout adjustment. I will leave it at 15 seconds, but I need to look further for the problem.

It doesn't seem to happen in dev. I get the timeout issues with lower timeout settings, but it always seems to resolve arcs fine. I will have to fix via inspection, I think.

[everbeek]

Shows up in dev when I use dev embed, of course.

http://127.0.0.1:8888/?mode=embed&embed_mode=concept_neighbourhood&virtual_ontology_id=1353&full_concept_id=http://purl.bioontology.org/ontology/SNOMEDCT/71388002

[everbeek]

Discovered that the usage of various containers in the TermNeighbourhoodLoader was confused (because it is complex!). Sorted it out, have it working in dev. Deploying to stage, will commit and deploy to live if successful.

[everbeek]

Deployment working.