Weasis deployment problem

526 views
Skip to first unread message

Nurettin KATRANCI

unread,
Feb 5, 2013, 5:06:34 AM2/5/13
to dcm...@googlegroups.com
Hi after deploying weasis under dcm4chee-2.17.2-mysql  (dcm4chee-web3), below written error is produced and can not start weasis:

11:37:31,994 INFO  [TomcatDeployer] deploy, ctxPath=/weasis-pacs-connector, warUrl=.../tmp/deploy/tmp5467243139988086972weasis-pacs-connector-exp.war/
11:37:32,093 ERROR [STDERR] SLF4J: Class path contains multiple SLF4J bindings.
11:37:32,102 ERROR [STDERR] SLF4J: Found binding in [jar:file:/home/katranci/Applications/dcm4chee/server/default/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
11:37:32,102 ERROR [STDERR] SLF4J: Found binding in [jar:file:/home/katranci/Applications/dcm4chee/server/default/tmp/deploy/tmp5467243139988086972weasis-pacs-connector-exp.war/WEB-INF/lib/logback-classic-0.9.29.jar!/org/slf4j/impl/StaticLoggerBinder.class]
11:37:32,103 ERROR [STDERR] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

Note to admins: dcm4chee-web3 tag is needed.

Nurettin

nicolas...@gmail.com

unread,
Feb 5, 2013, 9:19:41 AM2/5/13
to dcm...@googlegroups.com
This error doesn't have any consequence. This is because SLF4J already exists in the dcm4chee-jboss.
You can simply unzip weasis-pacs-connector.war and remove slf4j-api-1.6.1.jar, logback-classic-0.9.29.jar and logback-core-0.9.29.jar, and then zip it again.

If you cannot start Weasis, I guess there is something else.

gian78567

unread,
Jun 8, 2015, 9:57:38 AM6/8/15
to dcm...@googlegroups.com
Hi,

I hope you can help me.
I can start weasis from dcm4chee-web3 UI and I get the error while it's trying to get images from server  the Error window is from JRE and it says " error on loading wadoXML from http://loclahost:8080/weasis-pacs-connector/RequestManifest?id=2"

attached you find the log file for boot and for server
in server.log you can see me opening the applet 
It is a new instllation so I might have forgot something.
thanks
server.log
boot.log

Nicolas Roduit

unread,
Jun 9, 2015, 1:53:29 AM6/9/15
to dcm...@googlegroups.com, gptom...@gmail.com

...
2015-06-08 15:52:13,380 INFO  -> (pool-12-thread-1) [STDOUT] 2015-06-08 15:52:13,380 ERROR [-12-thread-1:CFind] findscu: A-ASSOCIATE-RJ[result: 1 - rejected-permanent, source: 1 - service-user, reason: 7 - called-AE-title-not-recognized]]

=> that means the calling AET "PACS-CONNECTOR" is rejected. Add it from the AE tab.

gian78567

unread,
Jun 9, 2015, 12:58:14 PM6/9/15
to dcm...@googlegroups.com, gptom...@gmail.com
Thanks for your prompt reply.
I fix the pacs.connector.properties file with the correct aetitle
but I still don't see the images
I attached the logs
server.log
boot.log

Nicolas Roduit

unread,
Jun 9, 2015, 1:38:31 PM6/9/15
to dcm...@googlegroups.com, gptom...@gmail.com
2015-06-09 18:50:44,201 INFO  -> (http-0.0.0.0-8080-8) [STDOUT] 2015-06-09 18:50:44,201 ERROR [0.0.0-8080-8:RequestManifest     ] Building Manifest Exception [id=1] - java.util.concurrent.ExecutionException: WadoQueryException: No Patients List

=> the patient does not have images or you applied a restriction somewhere.  

Nicolas Roduit

unread,
Jun 26, 2015, 5:07:00 AM6/26/15
to dcm...@googlegroups.com, nicolas...@gmail.com, gptom...@gmail.com
2015-06-09 18:47:34,931 INFO  -> (main) [STDOUT] 2015-06-09 18:47:34,931 ERROR [main        :ManifestManager     ] No request ID is allowed!

You have no ID allow in your configuration.
Reply all
Reply to author
Forward
0 new messages