Posts by royrohan

    # This file contains configuration information for the DICOM server

    # Do not edit unless you know what you are doing


    [sscscp]

    MicroPACS = sscscp


    # Network configuration: server name and TCP/IP port#

    MyACRNema = CONQUEST7119C

    TCPPort = 5679


    # Host, database, username and password for database

    SQLHost = localhost

    SQLServer = D:\dicomserver\dicomserver1419d1\Data\dbase\conquest.db3

    Username =

    Password =

    SqLite = 1

    DoubleBackSlashToDB = 0

    UseEscapeStringConstants = 0


    # Configure server

    ImportExportDragAndDrop = 1

    ZipTime = 05:

    UIDPrefix = 1.2.826.0.1.3680043.2.135.737131.84593541

    EnableComputedFields = 1


    FileNameSyntax = 4


    # Configuration of compression for incoming images and archival

    DroppedFileCompression = un

    IncomingCompression = un

    ArchiveCompression = as


    # For debug information

    PACSName = CONQUEST7119C

    OperatorConsole = 127.0.0.1

    DebugLevel = 1


    # Configuration of disk(s) to store images

    MAGDeviceFullThreshHold = 30

    MAGDevices = 1

    MAGDevice0 = d:\dicomserver\dicomserver1419d1\data\

    Hi Marcel,


    Our application has 60 sec timeout.

    The Protocol error time difference is inconsistent:

    5/15/2019 12:48:15 PM [CONQUEST7119C] ReadAheadThread: warning - resolving deadlock due to erratic incoming order

    5/15/2019 12:48:23 PM [CONQUEST7119C] Protocol error 0 in PDU:Read



    Thanks,

    Rohan

    Hello Mercel,


    The memory peaked at 97% while transferring the files. Following is the error it generated while kept the debugging level at "1":


    5/15/2019 12:28:53 PM [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000009_15566492280008.dcm

    5/15/2019 12:28:53 PM [CONQUEST7119C] Image Loaded from Read Ahead Thread, returning TRUE

    5/15/2019 12:28:58 PM [CONQUEST7119C] ReadAheadThread: readahead > 0020

    5/15/2019 12:29:00 PM [CONQUEST7119C] ReadAheadThread: warning - resolving deadlock due to erratic incoming order

    5/15/2019 12:29:00 PM [CONQUEST7119C] ReadAheadThread: readahead > 0021

    5/15/2019 12:29:01 PM [CONQUEST7119C] ReadAheadThread: warning - resolving deadlock due to erratic incoming order

    5/15/2019 12:29:02 PM [CONQUEST7119C] ReadAheadThread: readahead > 0022

    5/15/2019 12:29:03 PM [CONQUEST7119C] ReadAheadThread: warning - resolving deadlock due to erratic incoming order

    5/15/2019 12:29:18 PM [CONQUEST7119C] ReadAheadThread: readahead > 0023

    5/15/2019 12:29:20 PM [CONQUEST7119C] ReadAheadThread: warning - resolving deadlock due to erratic incoming order

    5/15/2019 12:29:40 PM [CONQUEST7119C] Protocol error 0 in PDU:Read

    5/15/2019 12:29:40 PM [CONQUEST7119C] Retrieve: remote connection dropped after 8 images, 89 not sent


    Thanks,

    Rohan

    Hi Marcel,


    Following is the Log from Conquest:


    [CONQUEST7119C] Monitoring for files in: d:\dicomserver\dicomserver1419d1\data\incoming

    [CONQUEST7119C] DGATE (1.5.0-alpha-test1, build Mon Mar 18 11:19:20 2019, bits 64) is running as threaded server

    [CONQUEST7119C] Database type: built-in SQLite driver

    [CONQUEST7119C] User interface test: local server is running!

    [CONQUEST7119C]

    [CONQUEST7119C] UPACS THREAD 1: STARTED AT: Tue May 14 11:48:21 2019

    [CONQUEST7119C] Calling Application Title : "EDGE"

    [CONQUEST7119C] Called Application Title : "CONQUEST7119C "

    [CONQUEST7119C] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

    [CONQUEST7119C] Presentation Context 0 "1.2.840.10008.5.1.4.1.2.2.1" 1

    [CONQUEST7119C] (StudyRootQuery) search level: STUDY

    [CONQUEST7119C] C-Find (StudyRoot) located 1 records

    [CONQUEST7119C] UPACS THREAD 1: ENDED AT: Tue May 14 11:48:22 2019

    [CONQUEST7119C] UPACS THREAD 1: TOTAL RUNNING TIME: 1 SECONDS

    [CONQUEST7119C]

    [CONQUEST7119C] UPACS THREAD 12: STARTED AT: Tue May 14 11:48:55 2019

    [CONQUEST7119C] Calling Application Title : "EDGE "

    [CONQUEST7119C] Called Application Title : "CONQUEST7119C "

    [CONQUEST7119C] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

    [CONQUEST7119C] Presentation Context 0 "1.2.840.10008.5.1.4.1.2.2.2" 1

    [CONQUEST7119C] C-Move Destination: "EDGE "

    [CONQUEST7119C] Number of Images to send: 97

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000001_15566491930000.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000002_15566491990001.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000003_15566492140002.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000004_15566492170003.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000005_15566492170004.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000006_15566492170005.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000007_15566492170006.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000008_15566492170007.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000009_15566492280008.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000010_15566492340009.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000011_1556649242000a.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000012_1556649243000b.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000013_1556649244000c.dcm

    [CONQUEST7119C] Sending file : d:\dicomserver\dicomserver1419d1\data\xxxxxxxxx\1.2.840.710410.0.785.32755.6926805104.189.7_0000_000014_1556649249000d.dcm

    [CONQUEST7119C] ***VR:ReAlloc out of memory allocating 249521472 bytes

    [CONQUEST7119C] ***A fatal error occurred (out of memory) - closing server

    It happens whenever we are sending multiple studies and one or more among the studies are large in size.

    Can we modify the default time out seconds?

    I'm using version: 1.4.19b


    This is the error description, we are getting:


    2019-02-11 11:47:06 EST ERROR-|DicomServiceTemplate:248| Exception while read operation: Read timed out

    java.net.SocketTimeoutException: Read timed out

    at java.net.SocketInputStream.socketRead0(Native Method)[:1.8.0_65]

    at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)[:1.8.0_65]

    at java.net.SocketInputStream.read(SocketInputStream.java:170)[:1.8.0_65]

    at java.net.SocketInputStream.read(SocketInputStream.java:141)[:1.8.0_65]

    at com.archimed.dicom.network.PduBuffer.readFully(PduBuffer.java:94)[109:dicom-services-dicom-runtime-assembly:18.1.0]

    at com.archimed.dicom.network.PduBuffer.read(PduBuffer.java:71)[109:dicom-services-dicom-runtime-assembly:18.1.0]

    at com.archimed.dicom.network.PduReader.read(PduReader.java:25)[109:dicom-services-dicom-runtime-assembly:18.1.0]

    at com.archimed.dicom.network.AssociationIO.read(AssociationIO.java:87)[109:dicom-services-dicom-runtime-assembly:18.1.0]

    ........

    ........

    .......

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]

    at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]

    Caused by: java.net.SocketTimeoutException: Read timed out

    at java.net.SocketInputStream.socketRead0(Native Method)[:1.8.0_65]

    at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)[:1.8.0_65]

    at java.net.SocketInputStream.read(SocketInputStream.java:170)[:1.8.0_65]

    at java.net.SocketInputStream.read(SocketInputStream.java:141)[:1.8.0_65]

    at com.archimed.dicom.network.PduBuffer.readFully(PduBuffer.java:94)[109:dicom-services-dicom-runtime-assembly:18.1.0]

    at com.archimed.dicom.network.PduBuffer.read(PduBuffer.java:71)[109:dicom-services-dicom-runtime-assembly:18.1.0]

    at com.archimed.dicom.network.PduReader.read(PduReader.java:25)[109:dicom-services-dicom-runtime-assembly:18.1.0]

    at com.archimed.dicom.network.AssociationIO.read(AssociationIO.java:87)[109:dicom-services-dicom-runtime-assembly:18.1.0]

    ....

    Hello,


    While trying to access data in my ConQuest server using DCMTK library, I'm getting the following error:

    "Requested service endpoint not properly configured : ERR00021 - java.io.IOException: Specified length (27265442) of PDU exceeds limit: 1048576"


    In the DCMTK library the maximum PDU size mentioned is : 1048576

    File being sent from Conquest has size: 26MB (which converts to almost to 27265442)


    Please shed some light on it. Thanks in advance.


    Thanks,

    Rohan

    Just a correction: The conquest application is running on Windows machine(not in VM) and it is in a private network(behind the proxy). And there's an application running on a separate Linux machine in the same private network. The application on Linux is trying to establish a connection to conquest( running on windows) and it's not able to create the association. Then it throws the SocketTimeoutException.

    I'm facing some issue while trying to connect to my local Conquest server remotely. It's throwing error that association is not established and throws socket error:


    java.net.SocketTimeoutException: connect timed out

    at java.net.PlainSocketImpl.socketConnect(Native Method)[:1.8.0_65]

    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)[:1.8.0_65]

    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)[:1.8.0_65]

    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)[:1.8.0_65]

    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)[:1.8.0_65]

    at java.net.Socket.connect(Socket.java:589)[:1.8.0_65]




    We have an application running on Linux machine and the ConQuest is running on a Linux machine. While I can send data from my conquest system to the linux system, it's not allowing the other way around and throwing socket error. I've checked the Windows firewall and it allows all the ports for conquest. I created a rule to allow port 5678 specifically to all application.


    Please let me know your thoughts.