OHDSI Home | Forums | Wiki | Github

Deployed Atlas shows no menus/UI elements

Implementers
#1

My Atlas web page just displays the Atlas animation but menus or UI at all.

I successfully built/deployed the WebAPI .war file (schema OHDSI)
I created a CDM database with the synpuf data (schema SYNPUF)
When I run achilles, it generates results from the SYNPUF data and puts it into a schema called RESULTS
My OHDSI.source table points towards the SYNPUF data
INSERT INTO OHDSI.source (source_id, source_name, source_key, source_connection, source_dialect) VALUES (1, ‘My Cdm’, ‘CDM_SOURCE’, ‘jdbc:oracle:thin:SYNPUF/MY_PASSWORD@//mydburl.com:1521/ORCL’, ‘oracle’);
INSERT INTO OHDSI.source (source_id, source_name, source_key, source_connection, source_dialect) VALUES (2, ‘Default vocabulary’, ‘VOCABULARY’, ‘jdbc:oracle:thin:SYNPUF/MY_PASSWORD@//mydburl.com:1521/ORCL’, ‘oracle’);

config-local.js for Atlas is as follows:
define([], function () {
var configLocal = {};

configLocal.api = {
	name: 'Commonwealth Informatics',
	url: 'https://localhost:8080/WebAPI/'
};

return configLocal;

});

I can’t find any logging information for Atlas. Is there a way to increase the logging level for Atlas so I can see some of what is going on?

What schemas is atlas trying to connect to and how does atlas get the urls/credentials for these?

In config-local.js should the url for WebAPI be http: rather than https?

What does this Atlas behavior (showing no UI elements) indicate?

#2

We need more logging information. Please feel free to post relevant logs and screenshots.

Atlas: In Chrome, open devtools (F12) and see if you have errors in Networks or Console when you load Atlas.

WebAPI: Tail/monitor the relevant tomcat logs to see if WebAPI starts up cleanly and is actually receiving REST requests from Atlas and responding without errors.

#3

Thanks,

Opening the dev tools showed me that my server was having trouble fetching code from code.jquery.com (due to firewall issues that have been fixed).

Now it gets farther in the Atlas load process, but displays the following error messages:
application initialization failed
unable to connect to an instance of the webapi.
please contact your administrator to resolve this issue.

The tomcat log shows the following:

27-Aug-2018 15:01:11.633 INFO [http-nio-8080-exec-7] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:414)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:294)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:764)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1388)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

I believe the config-local.js example given in the install instructions has a bug in it. It specifies an HTTPS url

url: 'https://localhost:8080/WebAPI/'

When I change this to http and load the application the web page seems to load correctly.

url: 'http://localhost:8080/WebAPI/'
#4

Thank you @jaybww - I was tripped up by this too!

t