2014-03-10 22:11 GMT+04:00 Christopher Schultz > > On 3/10/14, 1:20 PM, Christopher Schultz wrote: >> On 3/10/14, 12:58 PM, Christopher Schultz wrote: >>> All, >> >>> On 3/10/14, 12:52 PM, Christopher Schultz wrote: >>>> I stopped Tomcat, completely removed my web application, >>>> restarted Tomcat and I can connect without a problem. >> >>>> AFAIK, my application isn't doing anything with JMX. >> >>>> I'll try using my context.xml without any actual code >>>> involved. >> >>> Okay, I've discovered that if I deploy my web application but >>> remove WEB-INF/web.xml, I can still connect. Something my web >>> application is doing is breaking something. >> >>> I'll try to narrow-down what it is. >> >>> (Again, AFAIK, I'm not mucking-around with any of Tomcat's >>> internals... just a standard web application.)_ >> >> It looks like I can reproduce this with just Velocity and Velocity >> Tools. I'll keep narrowing it down. > > I have a minimal test which I've attached (sort of) to this Bugzilla > issue: > https://issues.apache.org/bugzilla/show_bug.cgi?id=56242 > > If anyone could give me some pointers at this stage, it would be > greatly appreciated. >
Win7, 32-bit JDK 7u51 Tomcat 8.0.3 If I connect with jconsole, it displays an odd error message with the following title, text and two buttons (I suppose some resource is missing, so it displays message keys instead of actual text): ConnectionFailedSSL1 ConnectionFailedSSL2 [Insecure] [Cancel] If I press "Insecure" button, it connects successfully and shows Catalina JMX beans. The above happens regardless of whether your web application is deployed or not. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
