Issue Number | 5106 |
---|---|
Summary | Summary Translation Queue Anomalies |
Created | 2022-04-20 12:39:50 |
Issue Type | Task |
Submitted By | Osei-Poku, William (NIH/NCI) [C] |
Assigned To | Osei-Poku, William (NIH/NCI) [C] |
Status | Closed |
Resolved | 2023-08-16 09:41:33 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.316120 |
There have been a few anomalies with the Summary Translation Queue recently on PROD. In the first place, some documents fail to be attached. The browser will spin forever and never attach the file. I am not sure if there is file size limit or not as I was able to easily attach a much smaller file without any problems. I was able to reproduce this behavior on QA this morning at about 9:35 AM with the same file that failed to be attached on PROD. No error messages are displayed. Just the indication in the browser of the spinning wheel. I have attached the file to this ticket. The user that reported this problem recently, first experienced it on March 14 at about 4:30 PM.
~bkline Sorry about the confusion of my last statement in my comment above:
I have not been able to reproduce this behavior on the lower tiers but will be on the lookout on PROD for when it happens again.
I reported 2 different issues in this ticket. One has to do with not being able to attach very large files. As stated above, I was able to reproduce this problem on the lower tiers. The second problem as stated in the second paragraph, has to do with users receiving notifications late. It is this second problem that I was not able to reproduce and I had said I would provide more information if it happens again. I hope this clarifies the issue.
Please split the two issues into separate tickets.
The new ticket number is OCECDR-5116
I have not heard of any delays recently so we will continue to monitor and report any delays.
Connected with Raymond Kobe. Raymond watched the Windows Event logs while I reproduced the failure, but saw nothing. Next he uninstalled the virus checker and rebooted the server and had me try again, but it still failed. Next step will be to loop in someone from the network team, so we can see if an intrusion detection rule is swallowing network packets.
I have reached out to Raymond K. for a status update on this issue.
According to Raymond K.
"Hello William the network team does not believe it is a networking issue. we schedule some troubleshooting time to look at browser settings"
The problem with the queue appears to have resolved itself. Users are no longer experiencing the problems reported in this ticket, so I am closing the ticket. Thanks!
File Name | Posted | User |
---|---|---|
Ch Vascular Tumors HP Spanish QC 3-14-22 KG.docx | 2022-04-20 12:39:45 | Osei-Poku, William (NIH/NCI) [C] |
Elapsed: 0:00:00.001412