Problems integrating weasis

[Stephan Engelhardt]

Hello everybody !!

I got DCM4CHE to work on Windows 10 and I can open the UI on localhost (not on other machines in the network using the servers IP though ??) and I can add studies (from other computers in the network)

I left the AET as it was (DCM4CHEE)

and I installed Weasis by following the relevant online instructions (https://nroduit.github.io/en/getting-started/dcm4chee/)

Now after I restarted the dcm4chee deployment I am getting the Weasis Symbol just fine and when I hit is I just get a new tab titled error.

with jboss showing me the following error :

00:18:33,774 INFO  [org.dcm4chee.arc.conf.rs.QueryRejectionNotes] (default task-8) Process GET /dcm4chee-arc/reject from null@127.0.0.1
00:18:33,785 INFO  [org.dcm4chee.arc.conf.rs.QueryAttributeSets] (default task-9) Process GET /dcm4chee-arc/attribute-set/DIFF_RS from null@127.0.0.1
00:18:38,487 INFO  [stdout] (pool-3-thread-1) 2018-08-21 00:18:38,485 [pool-3-thread-1] ERROR o.w.s.ServletUtil         Not supported IID request type: STUDY
00:18:38,491 INFO  [stdout] (default task-10) 2018-08-21 00:18:38,491 [default task-10] INFO  o.w.s.JnlpLauncher        1 - templatePath = file:/D:/Program Files/wildfly-11.0.0.Final/standalone/tmp/vfs/temp/temp5716b0687189d8a7/content-39c8820b9c4f3023/weasis.jnlp
00:18:38,496 INFO  [stdout] (default task-10) 2018-08-21 00:18:38,492 [default task-10] ERROR o.w.s.JnlpLauncher        Build jnlp
00:18:38,496 INFO  [stdout] (default task-10) org.weasis.servlet.JnlpLauncher$ServletErrorException:
00:18:38,496 INFO  [stdout] (default task-10)   at org.weasis.servlet.JnlpLauncher.createLauncherTemplate(JnlpLauncher.java:345)
00:18:38,496 INFO  [stdout] (default task-10)   at org.weasis.servlet.JnlpLauncher.buildJNLP(JnlpLauncher.java:147)
00:18:38,497 INFO  [stdout] (default task-10)   at org.weasis.servlet.JnlpLauncher.doGet(JnlpLauncher.java:132)
00:18:38,499 INFO  [stdout] (default task-10)   at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)

On startup of jboss I get the following error :

3:39:42,960 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 70) WFLYCLINF0002: Started client-mappings cache from ejb container
23:39:43,355 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 83) WFLYUT0021: Registered web context: '/weasis' for server 'default-server'
23:39:43,433 INFO  [stdout] (ServerService Thread Pool -- 78) 2018-08-20 23:39:43,432 [read Pool -- 78] INFO  o.w.s.ManifestManager     Start the manifest manager servlet
23:39:43,436 INFO  [stdout] (ServerService Thread Pool -- 78) 2018-08-20 23:39:43,436 [read Pool -- 78] INFO  o.w.s.ManifestManager     External weasis-pacs-connector configuration: file:/D:/Program%20Files/wildfly-11.0.0.Final/standalone/configuration/weasis-pacs-connector.properties
23:39:43,454 INFO  [stdout] (ServerService Thread Pool -- 78) 2018-08-20 23:39:43,443 [read Pool -- 78] ERROR o.w.s.ManifestManager     Error on initialization of ManifestManager
23:39:43,454 INFO  [stdout] (ServerService Thread Pool -- 78) java.io.IOException: Cannot find archive configuration
23:39:43,455 INFO  [stdout] (ServerService Thread Pool -- 78)   at org.weasis.servlet.ManifestManager.readArchiveURL(ManifestManager.java:171)
23:39:43,455 INFO  [stdout] (ServerService Thread Pool -- 78)   at org.weasis.servlet.ManifestManager.init(ManifestManager.java:96)
23:39:43,455 INFO  [stdout] (ServerService Thread Pool -- 78)   at javax.servlet.GenericServlet.init(GenericServlet.java:244)
23:39:43,455 INFO  [stdout] (ServerService Thread Pool -- 78)   at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117)
23:39:43,458 INFO  [stdout] (ServerService Thread Pool -- 78) 2018-08-20 23:39:43,458 [read Pool -- 78] INFO  o.w.s.ManifestManager     ManifestManagerThread configuration (maxLifeCycle=300s, cleanFrequency=60s)
23:39:43,459 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0021: Registered web context: '/weasis-pacs-connector' for server 'default-server'
23:39:43,509 INFO  [org.jboss.weld.Version] (MSC service thread 1-6) WELD-000900: 2.4.3 (Final)

ERROR o.w.s.ManifestManager     Error on initialization of ManifestManager
java.io.IOException: Cannot find archive configuration





what does that mean ??

I have downloaded weasis-pacs-connector.properties and dicom-dcm4chee-arc.properties and put them into wildfly 11.0.0.final/standalone/configuration

These files were not edited.




Has somebody an idea what might be the problem here??




Thks for your efforts its appreciated :)




Stephan


[Nicolas Roduit]

According to the log file, the file standalone/configuration/weasis-pacs-connector.properties seems to be corrupted or unreadable (see if it matches to the one on github).

[Stephan Engelhardt]

Thks for the prompt answer!

I redownloaded the properties file from Github and replaced it.

On the pro side I dont get any errors any more in the jboss log (yay :) )

on the down side I still cant load weasis :(

when I try to open weasis by dcm4chee it will generate the following link in the browser (firefox or edge )

localhost:8080/weasis-pacs-connector/IHEInvokeImageDisplay?requestType=STUDY&studyUID=1.2.840.114257.0.1.269.3112807728.30475332

when I add jnlp:// in front of it the java console will report me

CouldNotLoadArgumentException[ Angegebene Datei/URL konnte nicht geladen werden: jnlp://localhost:8080/weasis-pacs-connector/IHEInvokeImageDisplay?requestType=STUDY&studyUID=1.2.840.114257.0.1.269.3112807728.30475332]
    at com.sun.javaws.Main.launchApp(Unknown Source)
    at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
    at com.sun.javaws.Main.access$000(Unknown Source)
    at com.sun.javaws.Main$1.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
Caused by: java.io.FileNotFoundException: http://localhost:8080/weasis-pacs-connector/IHEInvokeImageDisplay?requestType=STUDY&studyUID=1.2.840.114257.0.1.269.3112807728.30475332
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.access$200(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.AccessController.doPrivilegedWithCombiner(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
    at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source)
    at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
    at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
    at com.sun.deploy.net.BasicHttpRequest.doGetRequest(Unknown Source)
    at com.sun.javaws.jnl.LaunchDescFactory._buildDescriptor(Unknown Source)
    at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
    at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
    ... 5 more

Im not sure what that means.

I thought it might be a problem concerning permissions but when I checked them all users were able to access the two war files.

thks for the help :)

[Stephan Engelhardt]

Just as a quick addendum

I have Java 1.8.0_181 x86 and x86_64 installed on the server and I use win 10 professional

Is there a certain requirement were I have to save the two war files??

at this time I use "..\program files\weasis"

[Nicolas Roduit]

I guess it is related to the windows installation, see https://stackoverflow.com/questions/34878936/filenotfoundexception-during-jnlp-download

[Stephan Engelhardt]

MMmmh ok I toyed around with weasis.jnlp and weasis1.jnlp and tried to set the parameters mentioned in the post

however the jnlp is in a temp directory and gets rewritten on startup and 2nd it didnt change anything.

Where would I alter the header?

thks for all the help :)

Stephan

[Nicolas Roduit]

I've never seen this issue before and weasis-pacs-connector hasn't changed for a long time. So there is something in your configuration that overrides the normal behavior.

By default, the jnlp should not be cache, see https://github.com/nroduit/weasis-pacs-connector/blob/master/src/main/java/org/weasis/servlet/JnlpLauncher.java#L179

But you could have a configuration on the server that overrides these parameters?

Activate the details log file on the client side. 

Desactivate antivirus or security manager?

Did you try to access with different computers?

[José Camacho]

HI everyone,

I found an error with the path to weasis.jnlp. The JnlpLauncher is not working with spaces on the path. I moved my tomcat directory to c:/tomcat9 without spaces and that's resolves my problem...

[Nicolas Roduit]

I've open an issue: https://github.com/nroduit/weasis-pacs-connector/issues/15