* External Email - Caution * |
The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.
Eli,
Is there anything in any of the XNAT logs that mention NullPointerException?
--
Rick Herrick
XNAT Architect/Developer
Computational Imaging Laboratory
Washington University School of Medicine
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/CH2PR02MB6710BF6B83F2E636C7EBDF68FE1F9%40CH2PR02MB6710.namprd02.prod.outlook.com.
That’s actually some issue in dcm4che. Occasionally when it closes the connection to a PACS it throws an NPE for some reason. We catch those and just ignore them in other places, but I’ll wrap this particular instance up as well.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/61255234-4432-4443-9246-838cc27a6a40n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/6143331a-2f0c-4015-8aff-5f2c66b47178n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/CH2PR02MB6710E6FE23381CBA0E7AB133FE199%40CH2PR02MB6710.namprd02.prod.outlook.com.
Sending data to a receiver using dqrObjectIdentifier would have issues:
I was able to send a basic DICOM image to a receiver configured with dqrObjectIdentifier just using dcmsend (i.e. the study instance UID wasn’t configured for the RoutedStudyDicomProjectIdentifier, nothing in there for the study ID or study instance UID, etc.) and it worked without issue. I did the same with DicomBrowser with the same results.
Could you possibly share a sample of your data? Anonymized of course, but if you can share that, please verify that the scrubbed data still has the same failure when sent to your DQR receiver. Just a single frame would be sufficient, I think.
--
Rick Herrick
XNAT Architect/Developer
Computational Imaging Laboratory
Washington University School of Medicine
From:
xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of elijah....@gmail.com <elijah....@gmail.com>
Date: Tuesday, July 13, 2021 at 4:17 PM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: Re: [XNAT Discussion] DQR plugin - not able to import
* External Email - Caution * |
So the query works now, but the import does not.
It sits in the queue for a minute or two, and then query history shows a failure, though the image appears to have been sent successfully from the dcmtk and/or dcm4che PACS.
One clue might be that we get an error message when trying to send a DICOM image to the DQR receiver from the "Dicom Browser" tool, which makes us think there might be something about the "dqrObjectIdentifier" class that is rejecting the images (see attached error message). But we can send images to the standard receiver with no problem.
-Eli
On Friday, July 9, 2021 at 11:32:02 AM UTC-5 richie...@gmail.com wrote:
Yes, the newly provided .jar worked with both of our test PACS Servers..
On Thu, Jul 8, 2021 at 9:51 AM Moore, Charlie <moo...@wustl.edu> wrote:
Could you try your previous PACS with a new build of the plugin here: https://ci.xnat.org/job/Plugins_Develop/job/DICOM_Query_Retrieve/lastSuccessfulBuild/artifact/build/libs/dicom-query-retrieve-1.0.1-SNAPSHOT-xpl.jar ? I believe we've fixed the issue of the search failing when the PACS doesn't support Modalities In Study.
Thanks,
Charlie
From: xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of Richard Cole <richie...@gmail.com>
Sent: Wednesday, July 7, 2021 11:22 AM
To: xnat_di...@googlegroups.com <xnat_di...@googlegroups.com>
Subject: Re: [XNAT Discussion] DQR plugin - not able to import
* External Email - Caution *
Just to give an update. To eliminate any possible issues with the "Test PACS" we previously setup for testing, I created a fresh VM with dcm4chee basic setup and the result was a successful query of the PACS and I was able to get results.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/d522170b-f0bd-48ed-a535-f4da12a31f88n%40googlegroups.com.
Caused by: org.nrg.action.ServerException: java.lang.ClassNotFoundException: org.nrg.dqr.processors.UpdateRequestStatusArchiveProcessor
Yes, either one of those should work. You could also run this query:
DELETE FROM xhbm_archive_processor_instance WHERE id = 1;
You’ll need to restart to clear the Hibernate cache, but that should clear out the entry with the invalid class reference.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/f72f1b17-930e-4fc3-9804-fe4acd676efen%40googlegroups.com.
This ends up doing the same thing as the query I sent at the same time, but doesn’t require a restart. I’m interested to hear if it works properly 😊
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/CH2PR02MB6710E044795969238D98A7FCFE139%40CH2PR02MB6710.namprd02.prod.outlook.com.