On 04/04/2016 23:10, Thad Humphries wrote:
> In docs/config/http.xml, lines #1430 and #1648 use "certificateValidation".
> However when I go to "#SSL_Support_-_SSLHostConfig" I find the attribute
> "certificateVerification", *not *"certificate*Validation*". I think one or
> the other is an error (
Hello Ivan,
From: John D. Ament
Sent: 05 April 2016 03:11
To: Tomcat Users List
Subject: Re: Information about incident ID 2205106170494020972
Is it at all possible that you have some network level security that's
blocking your access to this port?
On Mon
Hi.
Thanks for the answer. But i didn't quite catch, what i should do?
Eclipse refused to start Tomcat. I don't have any annotations i my
application.
Basil.
From: Violeta Georgieva
Sent: Monday, April 04, 2016 10:30 AM
To: Tomcat Users List
Subject: Re: Exception Both the UrlPattern and va
Chris,
Thanks for the response. As I have mentioned, there are bugs in
application code that prevents WebAppClassLoader from GC collection.
Wondering what happens when two instances are running one is pinned due
to application bugs and one newly deployed. For instance, would the
pinned instan
Rallavagu,
On 4/4/16 8:13 PM, Rallavagu wrote:
> Tomcat 7.0.47, JDK 7
>
> When an app is hot deployed in-place by simply copying the .war file
> into webapps directory, the old webappclassloader is not cleared
> completely because of inefficient context shutdown from the app. In this
> case, two
Tobias,
On 4/4/16 4:49 AM, Tobias Soloschenko wrote:
> I just figured out that this issue might depend on the file names of APR
> 1.5.2 - if I create links in the lib folder that reflects the names of
> 1.4.8 - tomcat throws an exception that the version of APR can not be
> resolved:
>
> ln -s li
Is it at all possible that you have some network level security that's
blocking your access to this port?
On Mon, Apr 4, 2016 at 10:03 PM Yin, Ivan wrote:
> Hi,
>
> I am sure this error message doesn't come from that webapp since there is
> no "incident ID" in the webapp.
> In addition, I search
Hi,
I am sure this error message doesn't come from that webapp since there is no
"incident ID" in the webapp.
In addition, I searched this error in google and I found a lot of similar error
messages coming from different webapps deployed on tomcat so I thought it might
come from Tomcat.
The or
> From: Yin, Ivan [mailto:ivan@sap.com]
> Subject: Information about incident ID 2205106170494020972
> When I tried to click one button in the web application deployed in Tomcat 7,
> it throws
> an error message as below:
> This page can't be displayed. Contact support for additional infor
Hi experts,
When I tried to click one button in the web application deployed in Tomcat 7,
it throws an error message as below:
This page can't be displayed. Contact support for additional information.
The incident ID is: 2205106170494020972.
May I know what is the meaning of this incident ID a
Tomcat 7.0.47, JDK 7
When an app is hot deployed in-place by simply copying the .war file
into webapps directory, the old webappclassloader is not cleared
completely because of inefficient context shutdown from the app. In this
case, two instances of WebAppClassLoader are running for the same
In docs/config/http.xml, lines #1430 and #1648 use "certificateValidation".
However when I go to "#SSL_Support_-_SSLHostConfig" I find the attribute
"certificateVerification", *not *"certificate*Validation*". I think one or
the other is an error (and I think "certificateVerification" is the correc
Hello everybody.
Tomcat 9 has a different behaviour than Tomcat 8, during the management of
MessageHandler.onMessage:
- in Tomcat 8:
Thread.currentThread().getContextClassLoader() returns an instance of
org.apache.catalina.loader.WebappClassLoader
- in Tomcat 9
Thread.currentThread().getCont
Hi,
2016-04-01 16:28 GMT+03:00 Svetlin Zarev :
>
> Hello,
>
>
>
> I have a custom authenticator valve which failed with an exception that
> never got logged by tomcat.
>
> After a little bit of digging in tomcat’s source it turned out that there
> is no valve responsible for logging
>
> exception
Hi,
I just figured out that this issue might depend on the file names of APR
1.5.2 - if I create links in the lib folder that reflects the names of
1.4.8 - tomcat throws an exception that the version of APR can not be
resolved:
ln -s libapr-1.0.dylib libtcnative-1.0.dylib
ln -s libapr-1.a libtcn
Hi,
2016-04-04 9:53 GMT+03:00 basilk :
>
> Hi.
>
> I try to start tomcat 8.0.33 in debug mode under Eclipse Mars.2.
> I get the following errors:
>
> SEVERE: A child container failed during start
> java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: Failed to start com
I have found that the current release 2.2 is not working for me, and there
are two issues that have been fixed in trunk development, that fixes the
problems I encounter. I have built the trunk version (2.3-SNAPSHOT) plugin
locally, and that works fine for me.
I prefer not to use SNAPSHOT, and I wo
17 matches
Mail list logo