Dcm4chee-arc4 Wado problems

249 views
Skip to first unread message

wakingd...@gmail.com

unread,
Aug 11, 2013, 11:23:26 PM8/11/13
to dcm...@googlegroups.com

I did as the https://github.com/dcm4che/dcm4chee-arc described,and install dcm4chee-arc4 successufly.And the Q-R test were also passed.While,when I test the wado interface,I get an error,it's like below

which means that I didn't deploy wado service successfully.But I found that,the dcm4chee-arc4 does contains Wado interface.Now I wonder if I should do some futher things to deploy or enable wado interface?Wating for your replay.

Aaron Boxer

unread,
Aug 12, 2013, 7:56:00 AM8/12/13
to dcm...@googlegroups.com
Dear Waking Dreamer,
The error screenshot does not show up. Can you post the error as text?



--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at http://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Aaron Boxer

unread,
Aug 12, 2013, 9:08:37 AM8/12/13
to dcm...@googlegroups.com
Actually, I am also seeing errors with wado interface. I can't access it.


On Sun, Aug 11, 2013 at 11:23 PM, <wakingd...@gmail.com> wrote:

--

Gunter Zeilinger

unread,
Aug 12, 2013, 9:51:05 AM8/12/13
to dcm...@googlegroups.com
Welche dcm4che-arc-4 version (4.1.0.Alpha2 oder current master branch)? Der resource path für das WADO URI service in
4.1.0.Alpha2 ist

http://HOST:8080/service/archive/wado

dagegen im aktuellen master branch:

http://HOST:8080/service/archive/wado-uri/DCM4CHEE

s.
http://www.dcm4che.org/jira/browse/ARCH-47
http://www.dcm4che.org/jira/browse/ARCH-49

--
gunter

Gunter Zeilinger

unread,
Aug 12, 2013, 9:57:22 AM8/12/13
to dcm...@googlegroups.com
Sorry, forgot to switch to English:

Which dcm4che-arc-4 version (4.1.0.Alpha2 or current master branch) did you installed? The resource path for the WADO URI service in

Aaron Boxer

unread,
Aug 12, 2013, 10:34:21 AM8/12/13
to dcm...@googlegroups.com
Thanks, Gunter. That fixed it for me.

wakingd...@gmail.com

unread,
Aug 12, 2013, 9:41:36 PM8/12/13
to dcm...@googlegroups.com
I am in current master now,and that fixed for me .Thanks,Gunter

在 2013年8月12日星期一UTC+8下午9时57分22秒,gunterze写道:

wakingd...@gmail.com

unread,
Aug 12, 2013, 10:15:03 PM8/12/13
to dcm...@googlegroups.com
By the way,does WADO in master support JPEG or other types?For I tried the URL like  that,but got expection




10:12:22,893 INFO  [org.dcm4chee.archive.wado.WadoURI] (http-localhost/127.0.0.1:8080-1) 127.0.0.1:49794 >> WADO-URI[http://localhost:8080/service/archive/wado-uri/DCM4CHEE?requestType=WADO&studyUID=1.2.840.113674.514.212.200&seriesUID=1.2.840.113674.514.212.81.300&objectUID=1.2.840.113674.950809132354242.100&contentType=image/jpeg, Accept=[text/html, application/xhtml+xml, application/xml;q="0.9", */*;q="0.8"]]
10:12:22,922 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/service].[org.dcm4chee.archive.ArchiveApplication]] (http-localhost/127.0.0.1:8080-1) JBWEB000236: Servlet.service() for servlet org.dcm4chee.archive.ArchiveApplication threw exception: java.lang.IncompatibleClassChangeError
at org.dcm4che.util.SafeClose.close(SafeClose.java:53) [dcm4che-core-3.2.1.jar:3.2.1]
at org.dcm4chee.archive.wado.WadoURI$1.write(WadoURI.java:340) [classes:]
at org.jboss.resteasy.plugins.providers.StreamingOutputProvider.writeTo(StreamingOutputProvider.java:32) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.plugins.providers.StreamingOutputProvider.writeTo(StreamingOutputProvider.java:17) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.interception.MessageBodyWriterContextImpl.proceed(MessageBodyWriterContextImpl.java:117) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.plugins.providers.jackson.JacksonJsonpInterceptor.write(JacksonJsonpInterceptor.java:112) [resteasy-jackson-provider-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.interception.MessageBodyWriterContextImpl.proceed(MessageBodyWriterContextImpl.java:123) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor.write(GZIPEncodingInterceptor.java:104) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.interception.MessageBodyWriterContextImpl.proceed(MessageBodyWriterContextImpl.java:123) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.ServerResponse.writeTo(ServerResponse.java:250) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.SynchronousDispatcher.writeJaxrsResponse(SynchronousDispatcher.java:602) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:528) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_38]







在 2013年8月12日星期一UTC+8下午9时57分22秒,gunterze写道:
Reply all
Reply to author
Forward
0 new messages