https://issues.apache.org/bugzilla/show_bug.cgi?id=56989
--- Comment #4 from Konstantin Kolinko <knst.koli...@gmail.com> --- You may try running with a debugger http://wiki.apache.org/tomcat/FAQ/Developing#Debugging With a breakpoint in static method SecurityContextHolder.initialize(). It may be interesting to know what stack trace will be at that point and what class loaders will be invoked. > c) When a request next goes to war2, the SecurityContextHolder class for > war2 is loaded from the war2 (correctly) but it's static field STILL > points to the strategy object created in (b), from war1! That would mean that the interface (the class used to declare the static field) were also loaded from "war1". There is no reflection API in use here (neither when declaring field, nor when creating strategy instance - it is created with Java "new" operator), so it will be loaded from the same class loader that loaded the calling class. So how can it be loaded from different war? What jars are in this classloader's class path? -- 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
