2014-03-10 23:51 GMT+04:00 Konstantin Kolinko <knst.koli...@gmail.com>: > 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. >
The same SSL attachment failure happens with JDK 7u51 + Tomcat 7.0.52. Those meaningless messages are a known bug https://bugs.openjdk.java.net/browse/JDK-8030878 but it does not explain why it fails in the first place. I guess they somehow broke/tightened AttachAPI? Removing "-Djava.io.tmpdir" from catalina.bat does not help. 2014-03-10 20:52 GMT+04:00 Christopher Schultz <ch...@christopherschultz.net>: > > 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. > What is the state of Tomcat when you "completely removed my web application"? Were there other web applications deployed on Tomcat? I my test I had standard webapps (at least docs, manager, ROOT) there. > AFAIK, my application isn't doing anything with JMX. >From a quick view, velocity 1.7 and velocity-tools 2.0 do not deal with JMX either. The only imports of javax.* are those of Servlet API. I wonder whether your issue is reproducible with Java 8 release candidates, that some Oracle people were advertising on dev mailing list. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
