https://issues.apache.org/bugzilla/show_bug.cgi?id=56657
--- Comment #2 from Konstantin Kolinko <knst.koli...@gmail.com> --- Additional minor issue in the same place. There is no check that on the second mapping loop the "version" was applied to the same path as on the first loop. If there is the following configuration: ROOT#0 ROOT#latest bar#0 bar#1 Consider that a request for "bar#0" comes in. It performs a remapping loop to select the "0" version. Consider that bar#0 is paused and third remapping loop is required. If both "bar#0" and "bar#1" are undeployed before remapping, the version variable remains "0", but it is being applied to a different path. So it may select ROOT#0 instead of expected ROOT#latest. Given the complexity of configuration to observe this, it is kind of a theoretical issue. -- 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