path: root/idrop-swing/release_notes.txt
diff options
authorMike Conway <>2012-01-05 17:02:00 (GMT)
committer Mike Conway <>2012-01-05 17:02:00 (GMT)
commit84d593e21fb5d5bdb4ccd48a93bff023db249c69 (patch)
treea41b0276db566d2fd8e232f567de187593636366 /idrop-swing/release_notes.txt
parent0bce21243175200928e6c3a3c64e36a5e248a753 (diff)
I think I have it. Jargon, by default, has a setting for a max parallel threads of 4. This is done as typical client machines get a saturated network connection if more than that are specified. This is configurable. I set the max threads to zero in my data opr inp operation and I received the 0 threads response from iRODS in portal opr out. My test transfer is currently running via iDrop, when it completes, I'll follow up with Roger by putting out a new version of iDrop that allows the max threads to be set to 0 in the config panel.
Diffstat (limited to 'idrop-swing/release_notes.txt')
1 files changed, 4 insertions, 0 deletions
diff --git a/idrop-swing/release_notes.txt b/idrop-swing/release_notes.txt
index 47b650f..ab8c7a1 100644
--- a/idrop-swing/release_notes.txt
+++ b/idrop-swing/release_notes.txt
@@ -119,6 +119,10 @@ iRODS iDrop > -511017 on copy
[#314] in login preset mode, drag of top level folder for get oper results in no data found warning
+[#579] iDrop put transfer sets to 1 threads, completes leaving 0 len file
iRODS iDrop > refresh remote tree after transfer completes - if queue is small/empty 2011-02-10 07:00:51