How to upload dcm file to DCM4CHEE using RESTFUL API?

[oliverfchen]

Is there a function in RESTFUL API that can do the same thing as storescu in pynetdicom? Request sample, please.
follow this link: #194
and: https://www.leadtools.com/help/sdk/v20/dh/to/leadtools-dicomweb-stow-rs.html
not successful.

[gunterze]

dcm4chee-arc supports DICOM PS.3.18 Store Transaction by HTTP POST /dcm4chee-arc/aets/{aet}/rs/studies

Wiki: Store objects by STOW RS

[nuttycat]

I have the same problem when I use the ui2 web page to upload a dicom file.
There is an error in wildfly logs.

2021-09-29 14:29:25,632 WARN  [org.dcm4chee.arc.stow.StowRS] (default task-6) Failed to process Part #1{content-disposition=[form-data;name="file";filename="1.2.26.3680043.2.428.4.20140411090343.745526.0906374841.dcm"], content-type=[application/dicom]}
2021-09-29 14:29:25,633 WARN  [org.dcm4chee.arc.stow.StowRS] (default task-6) Response Internal Server Error caused by java.lang.NullPointerException
	at deployment.dcm4chee-arc-ear-5.24.1-psql.ear.dcm4chee-arc-store-5.24.1.jar//org.dcm4chee.arc.store.impl.StoreContextImpl.getSopClassUID(StoreContextImpl.java:103)
	at deployment.dcm4chee-arc-ear-5.24.1-psql.ear.dcm4chee-arc-war-5.24.1-unsecure.war//org.dcm4chee.arc.stow.StowRS.storeDicomObject(StowRS.java:468)
......
	at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
	at org.jboss.xnio@3.8.4.Final//org.xnio.XnioWorker$WorkerThreadFactory$1$1.run(XnioWorker.java:1280)
	at java.base/java.lang.Thread.run(Thread.java:829)

My docker compose file:

version: "3.8"
services:
  ldap:
    image: dcm4che/slapd-dcm4chee:2.4.57-24.1
    logging:
      driver: json-file
      options:
        max-size: "10m"
    env_file: docker-compose.env
    deploy:
      placement:
        constraints:
          - 'node.labels.nm == dev1'
    volumes:
      - /home/ubuntu/dcm4chee-swarm/v/ldap:/var/lib/openldap/openldap-data
      - /home/ubuntu/dcm4chee-swarm/v/slapd.d:/etc/openldap/slapd.d
  db:
    image: dcm4che/postgres-dcm4chee:13.3-24
    logging:
      driver: json-file
      options:
        max-size: "10m"
    env_file: docker-compose.env
    deploy:
      placement:
        constraints:
          - 'node.labels.nm == dev1'
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /etc/timezone:/etc/timezone:ro
      - /home/ubuntu/dcm4chee-swarm/v/db:/var/lib/postgresql/data
  arc:
    image: dcm4che/dcm4chee-arc-psql:5.24.1
    logging:
      driver: json-file
      options:
        max-size: "10m"
    ports:
      - "8081:8080"
    env_file: docker-compose.env
    environment:
      WILDFLY_CHOWN: /opt/wildfly/standalone /storage
      WILDFLY_WAIT_FOR: ldap:389 db:5432
    depends_on:
      - ldap
      - db
    deploy:
      placement:
        constraints:
          - 'node.labels.nm == dev1'
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /etc/timezone:/etc/timezone:ro
      - /home/ubuntu/dcm4chee-swarm/v/wildfly:/opt/wildfly/standalone
      - /home/ubuntu/dcm4chee-swarm/v/storage:/storage

[nuttycat]

But it works well with dcm4chee-arc-psql:5.23.1,postgres-dcm4chee:13.1-23,slapd-dcm4chee:2.4.56-23.1

[gunterze]

Seems, STOW-RS service got broken in 5.24.0: opened #3392

[nuttycat]

By the way, it works as expected when I use the dcm4che tool stowrs to upload the files.
Therefor,is there any difference between the ui2 js code and dcm4che java implemention?

[gunterze]

dcm4che/dcm4che#1042 causes, that the issue of the STOW-RS service of the archive gets not be triggered.

[oliverfchen]

The referred curl command did not work in the arc 5.24.0, 5.24.1, but worked in arc 5.22.6