FHIR Chat · v5.2.0 Web UI issue · hapi

Stream: hapi

Topic: v5.2.0 Web UI issue

view this post on Zulip Vasyl Herman (Jan 23 2021 at 11:52):

Hello, a newbie needs some help :)
I am using docker to run FHIR server as described here hapi-fhir-jpaserver-starter:

docker pull hapiproject/hapi:latest
docker run -p 8080:8080 hapiproject/hapi:latest

However, I have the webUI looking weird:
fhir-web-ui.png

I would appreciate any help on how to fix it, or advice what stable version should be used.

view this post on Zulip Lin Zhang (Jan 23 2021 at 12:29):

Alternatively, you might want to build the images using the stater project.

view this post on Zulip Lin Zhang (Jan 23 2021 at 12:31):

https://github.com/hapifhir/hapi-fhir-jpaserver-starter

view this post on Zulip Vasyl Herman (Jan 23 2021 at 12:36):

@Lin Zhang
I have hapiproject/hapi:v5.1.0 up and running, seems like it works fine. However, it doesn't recognize application.yml from latest version.
Do you think it's a good idea to start exploring FHIR server using 5.1.0 ?

view this post on Zulip Vasyl Herman (Jan 23 2021 at 12:38):

Lin Zhang said:

Alternatively, you might want to build the images using the stater project.

I have built an image from v5.2.0 source with the same web UI issue.

view this post on Zulip Vasyl Herman (Jan 23 2021 at 12:39):

I feel like I should also try to build an image from master branch.

view this post on Zulip Jens Villadsen (Jan 23 2021 at 12:39):

@Vasyl Herman try out https://github.com/hapifhir/hapi-fhir-jpaserver-starter#using-the-dockerfile-and-multistage-build

view this post on Zulip Jens Villadsen (Jan 23 2021 at 12:40):

so clone from master branch and follow that

view this post on Zulip Jens Villadsen (Jan 23 2021 at 12:40):

the :latestdocker tag may not necessarily reflect latest fixes and changes in the code base

view this post on Zulip Jens Villadsen (Jan 23 2021 at 12:41):

the master branch should work as intended

view this post on Zulip Vasyl Herman (Jan 23 2021 at 12:41):

Thanks a lot for help !!!

view this post on Zulip Lin Zhang (Jan 23 2021 at 12:57):

I followed the multistage approach and it's working.

view this post on Zulip Dexter (Jan 26 2021 at 13:19):

I'm having this issue on HAPI FHIR 5.2.0 REST Server (FHIR Server; FHIR 4.0.1/R4)

Sending this request fails localhost:8080/fhir/Patient?identifier=EXSYS|.

root@hapifhir:/usr/local/tomcat# curl 'localhost:8080/fhir/Patient?identifier=EXSYS|'

<!doctype html><html lang="en"><head><title>HTTP Status 400 – Bad Request</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 400 – Bad Request</h1><hr class="line" /><p><b>Type</b> Exception Report</p><p><b>Message</b> Invalid character found in the request target [&#47;fhir&#47;Patient?identifier=EXSYS|]. The valid characters are defined in RFC 7230 and RFC 3986</p><p><b>Description</b> The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).</p><p><b>Exception</b></p><pre>java.lang.IllegalArgumentException: Invalid character found in the request target [&#47;fhir&#47;Patient?identifier=EXSYS|]. The valid characters are defined in RFC 7230 and RFC 3986
        org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:486)
        org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:261)
        org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
        org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)
        org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1590)
        org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
        java.base&#47;java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        java.base&#47;java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        java.base&#47;java.lang.Thread.run(Thread.java:834)
</pre><p><b>Note</b> The full stack trace of the root cause is available in the server logs.</p><hr class="line" /><h3>Apache Tomcat/9.0.38</h3></body></html>

HAPI public server is down, but I am confident that this request is supposed to work, I tested it with VONK too.
Pulled from standard HAPI docker image, with this configuration

spring:
  datasource:
    url: 'jdbc:h2:file:./target/database/h2'

    username: sa
    password: null
    driverClassName: org.h2.Driver
    max-active: 15

  batch:
    job:
      enabled: false

hapi:
  fhir:
    fhir_version: R4
    default_encoding: JSON
    default_pretty_print: false
    tester:

        home:
          name: Local Tester
          server_address: 'http://localhost:8080/fhir'
          refuse_to_fetch_third_party_urls: false
          fhir_version: R4

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -