https://bz.apache.org/bugzilla/show_bug.cgi?id=57129
--- Comment #44 from Mateusz Matela <mateusz.mat...@gmail.com> --- (In reply to mgrigorov from comment #42) > As Mark mentioned since recently Tomcat added functionality to scan the jars > in parallel. No matter whether the jars are sorted or not the results from > the parallel scanning will be shuffled. My app doesn't even use annotation scanning. A lot of legacy apps don't. Look, you can't save everyone who may have strange ideas about resource loading in the future. What we have now doesn't even save anyone, it only potentially makes them suffer earlier in hopes it would be less severe. But in order to achieve that, it makes lots of people suffer a lot right now. Mostly people, who just try to run their legacy app in a new Tomcat, because Tomcat 7 EOL approaches. That's mostly apps that won't use any fancy new features and may potentially never bump into this problem otherwise. > They really need to know about this problem and start fixing their > application! OK, if this is such a serious and prevalent problem, then the solution should not be "oh, let's have the system behave non-deterministically. But only if the underlying file system is also non-deterministic." Do you see how that sounds? Maybe Tomcat should scan the jars at context loading, detect all the duplicated resource paths and list them in logs with a big warning. What we have now definitely causes more pain than it saves. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
