problem with weasis with dcm4chee-arc-light integration

[Marko]

Hello,

I deployed and configured weasis and weasis pacs connector as per:

https://dcm4che.atlassian.net/wiki/display/WEA/Installing+Weasis+in+DCM4CHEE#InstallingWeasisinDCM4CHEE-Fordcm4chee-arc-light

https://github.com/nroduit/weasis-pacs-connector#configuration-of-weasis-pacs-connector

Weasis is version 2.5.3 and dcm4chee-arc-light is 5.10.1

When I click on the eye link in a study in dcm4chee-arc UI I'm redirected to a page and get the 404.

The URL I'm redirected to is: 

http://192.168.1.110:8080/weasis-pacs-connect1.2.276.0.37.1.164.20094529394

clearly is missing a part of the url:

"or/viewer?patientID="

Just wondering if I'm missing something

[Márcio Farias]

I have the same problem

[Nicolas Roduit]

What is the configuration in ldap for dcmInvokeImageDisplayPatientURL and dcmInvokeImageDisplayStudyURL ?

[Marko]

dcmInvokeImageDisplayPatientURL: ../../weasis-pacs-connector

dcmInvokeImageDisplayStudyURL: ../../weasis-pacs-connector

[Marko]

It's a dcm4chee-arc-light version related.

all works with dcm4chee-arc-light v 5.10.0

it doesn't work with v5.10.1

On Monday, May 15, 2017 at 7:39:21 PM UTC+2, Nicolas Roduit wrote:

[Nicolas Roduit]

I cannot reproduce this issue with 5.10.1 and 5.10.2:

docker ps -a

CONTAINER ID        IMAGE                                        COMMAND                  CREATED             STATUS              PORTS                                                                                              NAMES

ce39b506980c        dcm4che/dcm4chee-arc-psql:5.10.2-secure-ui   "/docker-entrypoint.s"   45 minutes ago      Up 44 minutes       0.0.0.0:2575->2575/tcp, 0.0.0.0:8080->8080/tcp, 0.0.0.0:9990->9990/tcp, 0.0.0.0:11112->11112/tcp   dcm4chee-arc

f95bebaf450b        dcm4che/postgres-dcm4chee:9.6-9              "/docker-entrypoint.s"   45 minutes ago      Up 44 minutes       5432/tcp, 0.0.0.0:5435->5435/tcp                                                                   postgres

c3ddb19fe009        dcm4che/slapd-dcm4chee:2.4.40-9.3            "/docker-entrypoint.s"   45 minutes ago      Up 44 minutes       0.0.0.0:389->389/tcp                                                                               slapd

[Marko Kauzlaric]

I just tried with the new v5.10.2 and I have the same problem.
This is with dcm4chee mysql version without docker.

On Thu, May 18, 2017 at 6:57 PM, Nicolas Roduit
<nicolas...@gmail.com> wrote:
> I cannot reproduce this issue with the following configuration:

> --
> You received this message because you are subscribed to a topic in the
> Google Groups "dcm4che" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/dcm4che/AnZ7T_87iDw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> dcm4che+u...@googlegroups.com.
> To post to this group, send email to dcm...@googlegroups.com.
> Visit this group at https://groups.google.com/group/dcm4che.
> For more options, visit https://groups.google.com/d/optout.

[leogrande]

I have the same problem as Marco as I stated in this post.

What I see from your, Nicolas, docker configuration that you are using dcm4che/slapd-dcm4chee:2.4.40-9.3 and I use slapd-dcm4chee:2.4.40-10.1.

Probably there is some difference regarding LDAP configuration in those versions. But I have not checked it yet.

[Marko]

I'm using slapd 2.4.42

Should that matter though? When I import the ldif files I don't get any errors

[Nicolas Roduit]

I finally reinstall all with the latest component and the issue appears.

The URL interpretation has changed, so I updated the documentation and weasis.ldif

[gunterze]

With dcm4chee-arc-light 5.10.2 alternatively to import weasis.ldif into LDAP, you may use the Web UI at http://localhost:8080/dcm4chee-arc/ui2 :

Configuration > Devices > dcm4chee-arc > Extensions > Archive Device

  Invoke Image Display Patient URL: ../../weasis-pacs-connector/IHEInvokeImageDisplay?requestType=PATIENT&patientID={}
  Invoke Image Display Study URL: ../../weasis-pacs-connector/IHEInvokeImageDisplay?requestType=STUDY&studyUID={}

Save

gunter

[Marko]

Thanks, this is working now.

[Gustavo Fernandez Guirland]

Gunter, Nicolas:

In my case, I used dcm4chee-arc-5.10.2-psql, with openldap-2.4.40-13.el7.x86_64 and Wildfly 10 on Centos 7. Weasis 2.5.3 and PACS-CONNECTOR 6.1.0.

I follow the procedure stated in https://dcm4che.atlassian.net/wiki/display/WEA/Installing+Weasis+in+DCM4CHEE
When configure pacs-connector, at the time of trying to download the study (eye icon from the UI of UI2) the error that appears in the dcm4chee-arc console is:
16: 48: 32,204 INFO [stdout] (default task-15) 2017-06-02 16: 48: 32,201 [default task-15] INFO owsJnlpLauncher 1 - templatePath = file: /opt/wildfly-10.1.0.Final /standalone/tmp/vfs/temp/tempa3313ecf6e41d0b7/weasis-pacs-connector.war-28f97337743a2da1/weasis.jnlp
(EE-ManagedExecutorService-default-Thread-2) Accept connection Socket [addr = / 127.0.0.1, port = 46593, localport = 11112]
16: 48: 32,342 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-8) DCM4CHEE <-PACS-CONNECTOR (4) >> A-ASSOCIATE-RQ
16: 48: 32,355 INFO [org.dcm4chee.arc.impl.ArchiveAssociationHandler] (EE-ManagedExecutorService-default-Thread-8) DCM4CHEE <-PACS-CONNECTOR (4): Calling AE not configured
DCM4CHEE <PACS-CONNECTOR (4) << A-ASSOCIATE-RJ [result: 1 - Rejected-permanent , Source: 1 - service-user, reason: 3 - calling-AE-title-not-recognized]
DCM4CHEE <-PACS-CONNECTOR (4): close Socket [addr = / 127.0.0.1, port = 46593, 16:48:32,405 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread- Localport = 11112]
16: 48: 32,418 INFO [stdout] (pool-6-thread-1) 2017-06-02 16:48:32,407 [pool-6-thread-1] ERROR o.w.d.o.CFind findscu
A-ASSOCIATE-RJ [result: 1 - rejected-permanent, source: 1 - service-user, reason: 3 - calling-AE-title- Not-recognized]
16: 48: 32,419 INFO [stdout] (pool-6-thread-1) at org.dcm4che3.net.PDUDecoder.nextPDU (PDUDecoder.java:182)
16: 48: 32,419 INFO [stdout] (pool-6-thread-1) at org.dcm4che3.net.Association $ 2.run (Association.java:518)
16: 48: 32,419 INFO [stdout] (pool-6-thread-1) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1142)
16: 48: 32,419 INFO [stdout] (pool-6-thread-1) at java.util.concurrent.ThreadPoolExecutor $ Worker.run (ThreadPoolExecutor.java:617)
(Default task-29) 2017-06-02 16: 48: 48,707 [default task-29] ERROR o.w.s.RequestManifest Building Manifest Exception [id = 1]
16: 48: 48,708 INFO [stdout] (default task-29) java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Empty Patient List
16: 48: 48,708 INFO [stdout] (default task-29) at java.util.concurrent.FutureTask.report (FutureTask.java:122)
16: 48: 48,708 INFO [stdout] (default task-29) at java.util.concurrent.FutureTask.get (FutureTask.java:206)
16: 48: 48,708 INFO [stdout] (default task-29) at org.weasis.servlet.RequestManifest.doGet (RequestManifest.java:91)
16: 48: 48,708 INFO [stdout] (default task-29) at javax.servlet.http.HttpServlet.service (HttpServlet.java:687)
16:48:48,709 INFO [stdout] (default task-29) 2017-06-02 16: 48: 48,709 [default task-29] INFO o.w.s.RequestManifest Consume ManifestBuilder with id = 1
16:48:48,730 [default task-30] 2017-06-02 16: 48: 48,730 [default task-30] ERROR o.w.s.RequestManifest No 'ManifestBuilder' found with id = 1.

Is there any additional configuration of the AET PACS-CONNECTOR given the primary error that they mention not recognizing the AET? Would it be that you do not receive RESPONSE from MANIFEST for not having VALIDATED THE AEY PACS-CONNECTOR? I have noticed that when I have tried the DICOM ECHO with other Modalities that I have configured there is no ERROR or SUCCESSFUL ECHO, however both the ping and DICOM ECHO from Mode to the DCM4CHEE is POSITIVE

DICOM ECHO FROM THE MODALITY to DCM4CHEE (MODALITY is ADDED to DCM4CHEE using ldif file and ldapadd command) and checked via Apache DS
12: 49: 42,158 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket [addr = / 10.202.151.171, port = 49402, localport = 11112]
12: 49: 42,161 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-7) DCM4CHEE <-MODALITY (3) >> A-ASSOCIATE-RQ
12: 49: 42,163 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-7) DCM4CHEE <-MODALITY (3) << A-ASSOCIATE-AC
12: 49: 42,257 INFO [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-7) DCM4CHEE <-MODALITY (3) >> 1: C-ECHO-RQ [pcid = 1
  Cuid = 1.2.840.10008.1.1 - Verification SOP Class
  Tsuid = 1.2.840.10008.1.2 - Implicit VR Little Endian
12: 49: 42,273 INFO [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-7) DCM4CHEE <-MODALITY (3) << 1: C-ECHO-RSP [pcid = 1, status = 0H
  Cuid = 1.2.840.10008.1.1 - Verification SOP Class
  Tsuid = 1.2.840.10008.1.2 - Implicit VR Little Endian
12: 49: 42,345 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-7) DCM4CHEE <-MODALITY (3) >> A-RELEASE-RQ
12: 49: 42,345 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-7) DCM4CHEE <-MODALITY (3) << A-RELEASE-RP ...

DICOM ECHO FROM THE UI2 TO ANOTHER MODALITY (pc-fusionar):
12: 50: 38,403 INFO [org.dcm4che3.net.Connection] (default task-9) Initiate connection from /0.0.0.0:0 to pc-fusionar:104

at this point DCM4CHEE is freeze in console, but response in sucesive commands

Best regards

[Nicolas Roduit]

As you can see in the log, the calling AE Title "PACS-CONNECTOR" is rejected. If you have defined restriction on C-FIND SCP, add "PACS-CONNECTOR" to the AE Title list.

[Gunter Zeilinger]

Seems you activated Validate Calling AE Hostname at Network AE or Device level, but did not add a configuration for PACS-CONNECTOR

--
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+unsubscribe@googlegroups.com.

[Gustavo Fernandez Guirland]

I publish as I solved it:
1) I built an LDIF file based on the sample-device.ldif with PACS-CONNECTOR data
2) I added it to LDAP with [hostdcm4chee-arc] # ldapadd -xWD "cn = admin, dc = dcm4che, dc = org" -f samplePACSCONNECTORgus.ldif

3) From the UI2 I did an Open Patient in the viewer with POSITIVE result THIS TIME, but with a WARN and ERROR that is not completely clear cause and consequences

*LOG from the console:
17: 14: 58,646 INFO [stdout] (default task-30) 2017-06-07 17: 14: 58,645 [default task-30] INFO owsJnlpLauncher 1 - templatePath = file: /opt/wildfly-10.1.0.Final /standalone/tmp/vfs/temp/temp1d1d4cfc73d19955/weasis-pacs-connector.war-787a81c358701116/weasis.jnlp
17: 14: 58,649 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket [addr = / 127.0.0.1, port = 47984, localport = 11112]
17: 14: 58,652 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE <-PACS-CONNECTOR (12) >> A-ASSOCIATE-RQ
17: 14: 58,653 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE <-PACS-CONNECTOR (12) << A-ASSOCIATE-AC
17: 14: 58,653 INFO [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE <-PACS-CONNECTOR (12) >> 1: C-FIND-RQ [pcid = 1, prior = 0
  Cuid = 1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query / Retrieve Information Model - FIND
  Tsuid = 1.2.840.10008.1.2 - Implicit VR Little Endian
17: 14: 58,654 INFO [org.dcm4chee.arc.query.scp.CommonCFindSCP] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE <-PACS-CONNECTOR (12): Process C-FIND RQ:
(0008,0020) DA [] StudyDate
(0008,0030) TM [] StudyTime
(0008,0050) SH [] AccessionNumber
(0008,0052) CS [STUDY] QueryRetrieveLevel
(0008,0061) CS [] ModalitiesInStudy
(0008,0090) PN [] ReferringPhysicianName
(0008,1030) LO [] StudyDescription
(0010,0010) PN [] Patient
(0010,0020) LO [00003] PatientID
(0010,0021) LO [] IssuerOfPatientID
(0010.0030) DA [] PatientBirthDate
(0010,0040) CS [] PatientSex
(0020,000D) UI [] StudyInstanceUID
(0020.0010) SH [] StudyID

17: 14: 58,660 INFO [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE <-PACS-CONNECTOR (12) << 1: C-FIND-RSP [pcid = 1, status = Ff00H
  Cuid = 1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query / Retrieve Information Model - FIND
  Tsuid = 1.2.840.10008.1.2 - Implicit VR Little Endian
17: 14: 58,662 INFO [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE <-PACS-CONNECTOR (12) << 1: C-FIND-RSP [pcid = 1, status = 0H
  Cuid = 1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query / Retrieve Information Model - FIND
  Tsuid = 1.2.840.10008.1.2 - Implicit VR Little Endian
(EE-ManagedExecutorService-default-Thread-2) Accept connection Socket [addr = / 127.0.0.1, port = 44311, localport = 11112] 17: 14: 58,665 INFO [org.dcm4che3.net.Connection]
17: 14: 58,666 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE <-PACS-CONNECTOR (12) >> A-RELEASE-RQ
17: 14: 58,666 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE <-PACS-CONNECTOR (12) << A-RELEASE-RP
17: 14: 58,668 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE <-PACS-CONNECTOR (13) >> A-ASSOCIATE-RQ
17: 14: 58,668 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE <-PACS-CONNECTOR (13) << A-ASSOCIATE-AC
17: 14: 58,669 INFO [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE <-PACS-CONNECTOR (13) >> 1: C-FIND-RQ [pcid = 1, prior = 0
  Cuid = 1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query / Retrieve Information Model - FIND
  Tsuid = 1.2.840.10008.1.2 - Implicit VR Little Endian
17: 14: 58,670 INFO [org.dcm4chee.arc.query.scp.CommonCFindSCP] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE <-PACS-CONNECTOR (13): Process C-FIND RQ:
(0008,0052) CS [SERIES] QueryRetrieveLevel
(0008,0060) CS [] Modality
(0008,103E) LO [] SeriesDescription
(0020,000D) UI [1.2.392.200046.100.2.1.400046.4453.20050708124912] StudyInstan
(0020,000E) UI [] SeriesInstanceUID
(0020,0011) IS [] SeriesNumber
17:14:58,677 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(13) << 1:C-FIND-RSP[pcid=1, status=ff00H
  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
17:14:58,679 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(13) << 1:C-FIND-RSP[pcid=1, status=ff00H
  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
17:14:58,679 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(13) << 1:C-FIND-RSP[pcid=1, status=0H
  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
17:14:58,681 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/127.0.0.1,port=58311,localport=11112]
17:14:58,682 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE<-PACS-CONNECTOR(13) >> A-RELEASE-RQ
17:14:58,682 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE<-PACS-CONNECTOR(13) << A-RELEASE-RP
17:14:58,682 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(14) >> A-ASSOCIATE-RQ
17:14:58,683 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(14) << A-ASSOCIATE-AC
17:14:58,684 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(14) >> 1:C-FIND-RQ[pcid=1, prior=0
  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
17:14:58,684 INFO  [org.dcm4chee.arc.query.scp.CommonCFindSCP] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(14): Process C-FIND RQ:
(0008,0018) UI [] SOPInstanceUID
(0008,0052) CS [IMAGE] QueryRetrieveLevel
(0020,000D) UI [1.2.392.200046.100.2.1.400046.4453.20050708124912] StudyInstan
(0020,000E) UI [1.2.392.200046.100.2.1.400046.4453.20050708124912.1] SeriesIns
(0020,0013) IS [] InstanceNumber

17:14:58,707 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE<-PACS-CONNECTOR(14) << 1:C-FIND-RSP[pcid=1, status=ff00H
  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
17:14:58,708 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE<-PACS-CONNECTOR(14) << 1:C-FIND-RSP[pcid=1, status=0H
  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
17:14:58,709 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(14) >> A-RELEASE-RQ
17:14:58,710 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(14) << A-RELEASE-RP
17:14:58,710 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/127.0.0.1,port=58257,localport=11112]
17:14:58,716 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) DCM4CHEE<-PACS-CONNECTOR(12): close Socket[addr=localhost/127.0.0.1,port=47984,localport=11112]
17:14:58,717 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(15) >> A-ASSOCIATE-RQ
17:14:58,717 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(15) << A-ASSOCIATE-AC
17:14:58,718 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(15) >> 1:C-FIND-RQ[pcid=1, prior=0
  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
17:14:58,718 INFO  [org.dcm4chee.arc.query.scp.CommonCFindSCP] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(15): Process C-FIND RQ:
(0008,0018) UI [] SOPInstanceUID
(0008,0052) CS [IMAGE] QueryRetrieveLevel
(0020,000D) UI [1.2.392.200046.100.2.1.400046.4453.20050708124912] StudyInstan
(0020,000E) UI [1.2.392.200046.100.2.1.400046.4453.20050708124912.2] SeriesIns
(0020,0013) IS [] InstanceNumber

17:14:58,733 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-3) DCM4CHEE<-PACS-CONNECTOR(13): close Socket[addr=localhost/127.0.0.1,port=44311,localport=11112]
17:14:58,737 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE<-PACS-CONNECTOR(15) << 1:C-FIND-RSP[pcid=1, status=ff00H
  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
17:14:58,738 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-14) DCM4CHEE<-PACS-CONNECTOR(15) << 1:C-FIND-RSP[pcid=1, status=0H
  cuid=1.2.840.10008.5.1.4.1.2.2.1 - Study Root Query/Retrieve Information Model - FIND
  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian
17:14:58,740 INFO  [stdout] (pool-6-thread-4) 2017-06-07 17:14:58,739 [pool-6-thread-4] INFO  o.w.d.m.t.ManifestBuilder Build Manifest in 92 ms [id=4]
17:14:58,740 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(15) >> A-RELEASE-RQ
17:14:58,740 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-13) DCM4CHEE<-PACS-CONNECTOR(15) << A-RELEASE-RP
17:14:58,760 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) DCM4CHEE<-PACS-CONNECTOR(14): close Socket[addr=localhost/127.0.0.1,port=58311,localport=11112]
17:14:58,791 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-4) DCM4CHEE<-PACS-CONNECTOR(15): close Socket[addr=localhost/127.0.0.1,port=58257,localport=11112]
17:15:12,233 INFO  [stdout] (default task-22) 2017-06-07 17:15:12,233 [default task-22] INFO  o.w.s.RequestManifest    Consume ManifestBuilder with id=$

>>>>>> HERE THE WARN and ERROR:
17:15:12,392 WARN  [org.hibernate.validator.messageinterpolation.AbstractMessageInterpolator] (default task-17) HV000168: The message descriptor 'tiene que corresponder a la expresión regular "([1-9]\d?})|100"' contains an unbalanced meta character '}' parameter.
17:15:12,394 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-17) RESTEASY002020: Unhandled asynchronous exception, sending back 500: java.lang.NullPointerException
    at org.dcm4chee.arc.wado.WadoURI.toString(WadoURI.java:191)
    at org.jboss.resteasy.api.validation.ResteasyViolationException.convertArrayToString(ResteasyViolationException.java:425)
    at org.jboss.resteasy.api.validation.ResteasyViolationException.convertViolation(ResteasyViolationException.java:406)
    at org.jboss.resteasy.api.validation.ResteasyViolationException.convertViolations(ResteasyViolationException.java:365)
    at org.jboss.resteasy.api.validation.ResteasyViolationException.getReturnValueViolations(ResteasyViolationException.java:191)
    at org.jboss.resteasy.api.validation.ResteasyViolationExceptionMapper.toResponse(ResteasyViolationExceptionMapper.java:50)
    at org.jboss.resteasy.api.validation.ResteasyViolationExceptionMapper.toResponse(ResteasyViolationExceptionMapper.java:25)
    at org.jboss.resteasy.core.ExceptionHandler.executeExceptionMapper(ExceptionHandler.java:100)
    at org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:243)
    at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:175)
    at org.jboss.resteasy.core.SynchronousDispatcher.asynchronousExceptionDelivery(SynchronousDispatcher.java:444)
    at org.jboss.resteasy.core.AbstractAsynchronousResponse.internalResume(AbstractAsynchronousResponse.java:196)
    at org.jboss.resteasy.plugins.server.servlet.Servlet3AsyncHttpRequest$Servlet3ExecutionContext$Servle3AsychronousResponse.resume(Servlet3AsyncHttpRequest.java:114)
    at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:303)
    at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249)
    at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236)
    at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:402)
    at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
    at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
    at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
    at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
    at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
    at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
    at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
    at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
    at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
    at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
    at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
    at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
    at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
    at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
    at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
    at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
    at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
    at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
    at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
    at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
    at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
    at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)
    at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:805)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:748)

17:15:12,408 WARN  [org.hibernate.validator.messageinterpolation.AbstractMessageInterpolator] (default task-26) HV000168: The message descriptor 'tiene que corresponder a la expresión regular "([1-9]\d?})|100"' contains an unbalanced meta character '}' parameter.
17:15:12,411 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-26) RESTEASY002020: Unhandled asynchronous exception, sending back 500: java.lang.NullPointerException
    at org.dcm4chee.arc.wado.WadoURI.toString(WadoURI.java:191)
    at org.jboss.resteasy.api.validation.ResteasyViolationException.convertArrayToString(ResteasyViolationException.java:425)
    at org.jboss.resteasy.api.validation.ResteasyViolationException.convertViolation(ResteasyViolationException.java:406)
    at org.jboss.resteasy.api.validation.ResteasyViolationException.convertViolations(ResteasyViolationException.java:365)
    at org.jboss.resteasy.api.validation.ResteasyViolationException.getReturnValueViolations(ResteasyViolationException.java:191)
    at org.jboss.resteasy.api.validation.ResteasyViolationExceptionMapper.toResponse(ResteasyViolationExceptionMapper.java:50)
    at org.jboss.resteasy.api.validation.ResteasyViolationExceptionMapper.toResponse(ResteasyViolationExceptionMapper.java:25)
    at org.jboss.resteasy.core.ExceptionHandler.executeExceptionMapper(ExceptionHandler.java:100)
    at org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:243)
    at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:175)
    at org.jboss.resteasy.core.SynchronousDispatcher.asynchronousExceptionDelivery(SynchronousDispatcher.java:444)
    at org.jboss.resteasy.core.AbstractAsynchronousResponse.internalResume(AbstractAsynchronousResponse.java:196)
    at org.jboss.resteasy.plugins.server.servlet.Servlet3AsyncHttpRequest$Servlet3ExecutionContext$Servle3AsychronousResponse.resume(Servlet3AsyncHttpRequest.java:114)
    at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:303)
    at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249)
    at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236)
    at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:402)
    at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
    at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
    at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
    at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
    at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
    at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
    at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
    at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
    at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
    at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
    at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
    at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
    at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
    at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
    at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
    at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
    at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
    at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
    at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
    at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
    at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
    at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)
    at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:805)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:748)

* AND FINALLY the GET and I can view the stuides for patient:
17:15:12,550 INFO  [org.dcm4chee.arc.wado.WadoURI] (default task-21) Process GET /dcm4chee-arc/aets/DCM4CHEE/wado?requestType=WADO&studyUID=1.2.392.200046.100.2.1.400046.4453.20050708124912&seriesUID=1.2.392.200046.100.2.1.400046.4453.20050708124912.1&objectUID=1.2.392.200046.100.2.1.400046.4453.20050708124912.1.1.1&contentType=application%2Fdicom&transferSyntax=* from nu...@10.202.151.161
17:15:12,557 INFO  [org.dcm4chee.arc.wado.WadoURI] (default task-18) Process GET /dcm4chee-arc/aets/DCM4CHEE/wado?requestType=WADO&studyUID=1.2.392.200046.100.2.1.400046.4453.20050708124912&seriesUID=1.2.392.200046.100.2.1.400046.4453.20050708124912.2&objectUID=1.2.392.200046.100.2.1.400046.4453.20050708124912.2.1.1&contentType=application%2Fdicom&transferSyntax=* from nu...@10.202.151.161

Best Regards

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

[leogrande]

In my case, when I activated "Validate Calling AE Hostname" via UI2 and then set it to 'False' via ldap (UI2 currently doesn't allow to change it back to False from True) I kept getting this error:

 [org.dcm4chee.arc.impl.ArchiveAssociationHandler] (EE-ManagedExecutorService-default-Thread-6) DCM4CHEE<-PACS-CONNECTOR(2): Calling AE not configured

I hope this will be fixed in the next release.

I guess, Gunter meant that you need to add 'PACS-CONNECTOR' AE to:

 device list-child 0bject-Network AEs-select your AE title (in my case "DCM4CHEE") - attributes "Preferred Calling AE Title".

It works for me and it doesn't require a PACS-CONNECTOR device creation.

[gunterze]

On Friday, June 9, 2017 at 3:46:21 PM UTC+2, leogrande wrote:

In my case, when I activated "Validate Calling AE Hostname" via UI2 and then set it to 'False' via ldap (UI2 currently doesn't allow to change it back to False from True) I kept getting this error:

 [org.dcm4chee.arc.impl.ArchiveAssociationHandler] (EE-ManagedExecutorService-default-Thread-6) DCM4CHEE<-PACS-CONNECTOR(2): Calling AE not configured

I hope this will be fixed in the next release.

I guess, Gunter meant that you need to add 'PACS-CONNECTOR' AE to:

 device list-child 0bject-Network AEs-select your AE title (in my case "DCM4CHEE") - attributes "Preferred Calling AE Title".

No. With Validate Calling AE Hostname = true you have to configure external DICOM peer application as Remote Application Enties with the correct hostname or IP address of its connections. s.Validate hostname or IP address of association requester