search

openmhealth / shimmer

An application for reading health data from third-party APIs.
Apache License 2.0
442 stars 122 forks source link

Issue in running locally or on tomcat #41

Open shridhargune1977 opened 8 years ago

shridhargune1977 commented 8 years ago

Hi I am from windows & .Net world so having issues getting this running. I am able to build the code locally and get the "started application" message but when look at http://localhost:8083/ it gives whitelable error page mentioning "There was an unexpected error (type=Not Found, status=404). ". Attaching the log file

I also tried taking the war file created and deploying on tomcat. However got below error in log

INFO: validateJarFile(D:\apache-tomcat-7.0.47\webapps\shimmer-new\WEB-INF\lib\javax.el-3.0.0.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class

Based on some forums it looks to be issue related to dependencies. Tried to change the build.gradle but no use. shimmer.zip

emersonf commented 8 years ago

Can you paste the log as a link to a Gist please? We'll investigate whether there are any obvious dependency issues in the meantime.

shridhargune1977 commented 8 years ago

Hi I have created Gist for shimmer.log where in it says application started but http://localhost:8083/ gives whitelable error page mentioning "There was an unexpected error (type=Not Found, status=404). " Also added tomcat log when i deploy WAR file. Please find below URL: https://gist.github.com/shridhargune1977/83cefdbbde150d46485b

shridhargune1977 commented 8 years ago

Also please note I have Windows 8, 64 bit OS.

shridhargune1977 commented 8 years ago

Update on the issue - For native install, I am able to pragmatically authorize and read the data however not able to access console, Same error as mentioned earlier - 404. Also the WAR deployment issue is still there. Please let me know any pointers.

emersonf commented 8 years ago

re: the native issue, are you following the instructions in the run-natively.sh script and translating them to the equivalent Windows commands? Specifically the creation of the symlink to make the console JS available to Jetty? The Docker containers exist to avoid this exact issue, since the problem is environment-specific.

re: the WAR file issue, the JAR file exclusion shouldn't be causing problems, since the requisite classes are provided by Tomcat. We can look into that in the coming days. The console files are definitely missing when following the current instructions, and we'll need to look into building the WAR properly.

Both issues are caused by attempting to turn the console and resource server into a single application, with Tomcat requiring even more hoop jumping than Jetty. Since the client and server are two separate applications that talk over HTTP, we'll be evaluating the impact of not lumping them together in the coming weeks.