-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Konstantin,

On 3/10/14, 4:47 PM, Konstantin Kolinko wrote:
> 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.

No, I have to attach "insecurely" no matter what. What happens to me
is *after* falling back to an insecure connection.

I gave up using jconsole after a while and used VisualVM exclusively
to track-down the cause because it would give me better information
(would connect with a mild error, JMX didn't work). I was able to
reproduce it with the small test case I attached to the BZ issue.

> I guess they somehow broke/tightened AttachAPI?
> 
> Removing "-Djava.io.tmpdir" from catalina.bat does not help.


I'll see if I can get a Windows VM running to try another environment.
It's entirely possible this is a Mac / Oracle VM thing.

> 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 removed everything in the webapps/ directory and restarted. I may or
may not have cleaned-out the work directory. There were no web
applications deployed at all. I can confirm that other web
applications (written by my team) can be deployed without causing this
problem.

> 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 wouldn't have expected that they would. The only thing I could think
of was that maybe there was some kind of non-serializable object that
the remote client (jconsole) was attempting to access that for some
reason caused the whole thing to die. I would have expected a nicer
error... not something like "can't connect using Attach API" and
having both jconsole and YourKit fail utterly and VisualVM connecting
yet without JMX support.

> I wonder whether your issue is reproducible with Java 8 release 
> candidates, that some Oracle people were advertising on dev
> mailing list.

I could give that a try. I can also fall-back to Java 6, as Apple
still has packages for Java 6 i386 and x86_64 (both of which I have
installed and available).

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTHijxAAoJEBzwKT+lPKRY4vAQAJXROFkP430767lmFqA1TB8k
hQYoFvvj51MUYVt9Xoyv9GW0TYFWcBkVXeGRp5YhDMMr1pgueFaxcXmSEBwccTV3
OvIdqDm+eZFQcFGSm/6kzFMXIwJRcC0tym7PsmvUFYSAUkWGGGDpxpjbU5Yk79ZZ
4KB4c6DcAEUwxcaLi3TTcS6YB1/cZ6VoTy4onjqgMprQ6DhWFieWkfQKIlryamEi
APpw407K/qBt79YPoKBrld1Kcbvn3aKDFuJjs4JHMDLtjKRcrWITZXXCStAMe8rk
ugIXch0RP25H+XvK3nfmF8kw6MLNNSS3g7rDsYnIPIsQltD0HucL8+c7IoID8842
OuURHAUw1n+Cd6pW3wE+Av9Zivo3iPw72iAI8kZYn/z9T1lbc0M6w4/3e8bKysST
/gkExlj+CZ6SPy+qpl47ojX07ZktVosW4zJi7P+KtjxYOzLEnag+0tz0nTeB6kRs
jnPNg+cCv+FnWLW43KB3+1QbM8YEaCzhO8DyLYdFi9v+TJ2Hoyp4+wAJjvqLXdm+
OPwlF1UdNiSwENmqgzfMEJ7Fw10fXR8zA3ffXMkvopj5APZe/4UjZRDEEfq8baHe
UbBRBtTAft3Za1xOMpuT+RoNzBKVo2YlSCVzlTC2jVlwu9nZAYQLMfTzLKso8zmk
tHx/jbDh8g56qXVQClJL
=erew
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to