On 8.6, and now on latest 8.8, a customer totally hung up the entire aware system by trying to upload a large .MOV file.
About a year ago, there were some 25+meg images that did this, and they just stopped uploading those. No more issues.
Today a guy in the field accidentally selected the .MOV instead of .JPG and crashed everything.
Nothing unusual in the logs - but nothing would respond when trying to log back in.
1) I know mark said he has lots of images uploading daily - but he also said they had a max file size.
2) I had a max filesize of 8000, so it makes me wonder when aware checks - because it shouldn't have even allowed the start. Doesn't make sense to take time to upload a big file AND THEN say, oh, thats too large.
3) I've since added a restriction for Images only, so I shouldn't have the .MOV issue again, but still this shouldn't have crashed requiring an Aware restart.