Thank you helix84, I guess it really does just boil down to the reloadable attribute. We even had that change as part of our upgrade notes -- lesson learned! Now I know where the changes are to be made intimately.
As I mentioned in my last post, though, our live, production server has kept its reloadable attribute set to 'true' for year(s) and does not reflect this behavior which leads me to presume that Tomcat on Windows may have changed. Both Tomcat and Windows and Java are different versions, though, between our old and new systems. Thanks so much for your help and recommendations. It was very encouraging and appreciated! To put it all in one place, *the problematic configuration was having reloadable set to true for my Tomcat 'contexts'* on the following architecture: *Windows Server 2012 R2* *Tomcat: 8.0.23* *DSpace: 5.4* *Java: jre1.8.0_65* -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
