https://issues.apache.org/bugzilla/show_bug.cgi?id=55618
--- Comment #6 from Sander Sõnajalg <sander.sonaj...@gmail.com> --- Hi, I'm now quite sure that it is the <listener> definition in web.xml. I'll do some more research.. it seems that tomcat 6.x/7.x detected the duplicate Listener instance and didn't execute it, while tomcat 8.x starts a duplicate Listener (I'm far from being competent enough here to say which approach is more desired.. you probably know it better). I'll test some more on my own... I just hope that the situation is not that old containers *require* <listener> element to be there and new ones *require it not to be there*, which would lead to a backwards compatibility problem. I'll research some more .. Thanks! -- 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
