Further, Apache Tomcat 7 reached end of life as of 31 March 2021 and is
no longer supported by this community.
This means we no longer assess Tomcat 7 against reported security
vulnerabilities so even if your client is running the latest Tomcat 7
version available, 7.0.109, there have been a n
I hope this helps
https://lists.apache.org/thread/m3bhytsh3yrhsxvo98vcyx4q6w0m1d4v
On Fri, Jan 28, 2022, 9:58 AM Tim Funk wrote:
> Out of the box, no version of Apache Tomcat uses any log4j version.
>
> If log4j is used, it is by a specific application (not provided by the ASF)
> deployed to Tom
Out of the box, no version of Apache Tomcat uses any log4j version.
If log4j is used, it is by a specific application (not provided by the ASF)
deployed to Tomcat. (Or an admin changed the default install to add it)
-Tim
On Fri, Jan 28, 2022 at 10:36 AM Samuel Anderson-Burrell | Cloud21
wrote:
Mark,
On 1/4/22 17:50, Mark Thomas wrote:
On 04/01/2022 19:23, Robert J. Carr wrote:
I've been using tomcat for many years but unfortunately I'm stuck on
version 7 (long story). I recently picked up a new workstation, an Apple
M1 MacBook (M1 Max - macOS 12.1), and I installed the ARM version
On Tue, Jan 4, 2022 at 2:50 PM Mark Thomas wrote:
>
>
> On 04/01/2022 19:23, Robert J. Carr wrote:
> > I've been using tomcat for many years but unfortunately I'm stuck on
> > version 7 (long story). I recently picked up a new workstation, an Apple
> > M1 MacBook (M1 Max - macOS 12.1), and I ins
On Tue, Jan 4, 2022 at 2:50 PM Mark Thomas wrote:
>
> On 04/01/2022 19:23, Robert J. Carr wrote:
> > I've been using tomcat for many years but unfortunately I'm stuck on
> > version 7 (long story). I recently picked up a new workstation, an Apple
> > M1 MacBook (M1 Max - macOS 12.1), and I insta
On 04/01/2022 19:23, Robert J. Carr wrote:
I've been using tomcat for many years but unfortunately I'm stuck on
version 7 (long story). I recently picked up a new workstation, an Apple
M1 MacBook (M1 Max - macOS 12.1), and I installed the ARM version of Azul
Zulu (1.8.0_312), and by all accou
, February 3, 2020 7:32 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat 7: logs for failure request with unsupported cipher and
unsupported SSL protocol
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Manish,
On 2/2/20 11:20 PM, Palod, Manish wrote:
> Thanks Chris for considering this for fut
ant to prepare some patches/PRs, it's much more likely to go the way
you hope.
- -chris
> -Original Message- From: Christopher Schultz
> Sent: Saturday, February 1, 2020
> 9:54 PM To: users@tomcat.apache.org Subject: Re: Tomcat 7: logs for
> failure request with unsuppo
Thanks Chris for considering this for future release.
In future will the fix be ported into Tomcat 7 also?
Regards
Manish
-Original Message-
From: Christopher Schultz
Sent: Saturday, February 1, 2020 9:54 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat 7: logs for failure request
l Message- From: Christopher Schultz
> Sent: Saturday, February 1, 2020
> 12:03 AM To: users@tomcat.apache.org Subject: Re: Tomcat 7: logs
> for failure request with unsupported cipher and unsupported SSL
> protocol
>
> Manish,
>
> On 1/30/20 3:12 AM, Palod, Manish wr
Thanks Chris for the updates.
I will look forward for future release with enhanced info about connection.
Regards
Manish
-Original Message-
From: Christopher Schultz
Sent: Saturday, February 1, 2020 12:03 AM
To: users@tomcat.apache.org
Subject: Re: Tomcat 7: logs for failure request
n for every failure.
That requirement is impossible to meet.
- -chris
> -Original Message- From: Christopher Schultz
> Sent: Wednesday, January 29, 2020
> 9:32 PM To: users@tomcat.apache.org Subject: Re: Tomcat 7: logs for
> failure request with unsupported cipher and unsupported SSL
users@tomcat.apache.org
Subject: Re: Tomcat 7: logs for failure request with unsupported cipher and
unsupported SSL protocol
CAUTION: External email. Do not click links or open attachments unless you
recognize the sender and know the content is safe.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 1
On 29/01/2020 16:02, Christopher Schultz wrote:
> Mark,
>
> On 1/29/20 7:56 AM, Mark Thomas wrote:
>> On 29/01/2020 12:40, Palod, Manish wrote:
>>> Hi All,
>>>
>>>
>>> I am using tomcat 7 and in our server we support connection only
>>> with "TLSv1.2" and cipher
>>> "TLS_ECDHE_RSA_WITH_AES_128_GCM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 1/29/20 7:56 AM, Mark Thomas wrote:
> On 29/01/2020 12:40, Palod, Manish wrote:
>> Hi All,
>>
>>
>> I am using tomcat 7 and in our server we support connection only
>> with "TLSv1.2" and cipher
>> "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256".
On 29/01/2020 12:40, Palod, Manish wrote:
> Hi All,
>
>
> I am using tomcat 7 and in our server we support connection only with
> "TLSv1.2" and cipher "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256".
>
>
>
> Following is the Access valve pattern
> "%{E M/d/y @ hh:mm:ss.S a z}t %a (%{X-Forwarded-For}i
On 01/12/2019 23:04, Mark Thomas wrote:
I'm with you. And likely our setup is special in a way. However, I've
rarely seen that you have to re-enter credentials in a professional web
application like Google or Facebook, for example.
Yes. But if those apps were running on Tomcat I doubt that
On 29/11/2019 11:48, Klein, Carsten wrote:
> However, we are developing Ajax-driven
> B2B client applications, which terminate / end the session when they
> detect loss of authentication. Technically, these apps periodically send
> keep-alive messages to the server (in order to keep the session
On 28/11/2019 10:20, Mark Thomas wrote:
On 28/11/2019 08:03, Klein, Carsten wrote:
Hi there,
Thanks for answering my questions. See my remarks inline:
in all recent Tomcat versions the standard session implementation
declares authentication related fields as 'transient', so both the
session
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Carsten,
> in all recent Tomcat versions the standard session implementation
> declares authentication related fields as 'transient', so both the
> session's authType as well as it's authenticated Principal is not
> saved and restored across resta
On 28/11/2019 08:03, Klein, Carsten wrote:
> Hi there,
>
> in all recent Tomcat versions the standard session implementation
> declares authentication related fields as 'transient', so both the
> session's authType as well as it's authenticated Principal is not saved
> and restored across restarts
Message-
From: Mark Thomas
Sent: Tuesday, October 8, 2019 1:01 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat 7 HTTPS and LDAP authentication issue
On 08/10/2019 19:52, John Beaulaurier -X (jbeaulau - ADVANCED NETWORK
INFORMATION INC at Cisco) wrote:
> Hi Mark,
>
> How are you config
SSLProtocol="all" />
>
> How are you configuring TLS for LDAP?
>
> Do you mean inside Tomcat?
Yes. Or is the authentication happening in httpd?
Mark
>
> Thanks
> -John
>
> -Original Message-
> From: Mark Thomas
> Sent: Tuesday, Octob
Hi Mark,
How are you configuring TLS for the Connector?
How are you configuring TLS for LDAP?
Do you mean inside Tomcat?
Thanks
-John
-Original Message-
From: Mark Thomas
Sent: Tuesday, October 8, 2019 11:07 AM
To: users@tomcat.apache.org
Subject: Re: Tomcat 7 HTTPS and LDAP
On 08/10/2019 18:55, John Beaulaurier -X (jbeaulau - ADVANCED NETWORK
INFORMATION INC at Cisco) wrote:
> Hello,
>
> We have an application running on Tomcat 7.0.96. The application handles
> authentication by accessing an internal LDAPS host by using credentials, a
> keystore, and the
> LDAPS ho
On 20/03/2019 10:05, Mark Thomas wrote:
> On 19/03/2019 23:49, James H. H. Lampert wrote:
>> In response to my question:
>>
I've just (same customer as before) been asked about
ECDHE-ECDSA-CHACHA20-POLY1305 and ECDHE-RSA-CHACHA20-POLY1305
and I can't find either one on the Sun o
On 19/03/2019 23:49, James H. H. Lampert wrote:
> In response to my question:
>
>>> I've just (same customer as before) been asked about
>>> ECDHE-ECDSA-CHACHA20-POLY1305 and ECDHE-RSA-CHACHA20-POLY1305
>>>
>>> and I can't find either one on the Sun or IBM JSSE cipher lists for
>>> Java 8.
>
> On
Ramesh,
On Thu, Apr 26, 2018 at 11:45 AM, Naga Ramesh wrote:
> Team,
>
>
>
> I have configured the tomcat7 & 8 versions on our AWS environment, but how
> much memory need to give min and max for each tomcat. ( max to max how much
> need to give the max vlaue)
>
>
>
> Server: AWS linux
>
> RAM:
Chris - The header logging is a good idea. We'll add that. In the meantime,
it looks like it might have been premature to indicate that "the problem
persists with HTTP/1.1". The one instance that I found was a red herring,
so to date the problem has *not* recurred since addressing the HTTP/1.0
issu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chad,
On 2/27/18 9:02 PM, Chad Stansbury wrote:
> Thanks for your response. Unfortunately it doesn't appear to be a
> bad cookie name or value, as the identical set of cookies are
> passed (and parsed correctly) on requests that immediately precede
Hello Chris -
Thanks for your response. Unfortunately it doesn't appear to be a bad
cookie name or value, as the identical set of cookies are passed (and
parsed correctly) on requests that immediately precede and follow the
failing request. That's pretty clear from both the Wireshark and Tomcat
ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chad,
On 2/27/18 9:44 AM, Chad Stansbury wrote:
> We've been troubleshooting an issue where our web application is
> getting a very occasional request that contains no cookies even
> though a Wireshark on the application server shows those cookies
>
On 20/09/17 10:47, Konstantin Ryadov wrote:
>
> Hello!
> Could you explain context path (e.g. described on
> https://tomcat.apache.org/tomcat-7.0-doc/config/context.html ) value set in
> server.xml limitations?
> Does it exist any context path validation (unescaped symbols, whitespaces and
> s
On Wed, Sep 20, 2017 at 5:47 PM, Konstantin Ryadov
wrote:
>
> Hello!
> Could you explain context path (e.g. described on
> https://tomcat.apache.org/tomcat-7.0-doc/config/context.html ) value set
> in server.xml limitations?
> Does it exist any context path validation (unescaped symbols, whitespa
On Tue, Sep 19, 2017 at 9:53 AM, Suvendu Sekhar Mondal
wrote:
> Radhika,
>
> On Tue, Sep 19, 2017 at 2:21 PM, Peddi, Radhika (Radhika)
> wrote:
>> Hi,
>>
>> We have upgraded RHEL 7.2 to RHEL 7.4. After upgrade when we are running
>> performance testing of our application we are seeing below erro
Radhika,
On Tue, Sep 19, 2017 at 2:21 PM, Peddi, Radhika (Radhika)
wrote:
> Hi,
>
> We have upgraded RHEL 7.2 to RHEL 7.4. After upgrade when we are running
> performance testing of our application we are seeing below error in
> catalina.out.
>
> java.lang.OutOfMemoryError: unable to create new
On 19/09/17 09:51, Peddi, Radhika (Radhika) wrote:
> Hi,
>
> We have upgraded RHEL 7.2 to RHEL 7.4. After upgrade when we are running
> performance testing of our application we are seeing below error in
> catalina.out.
>
> java.lang.OutOfMemoryError: unable to create new native thread Exceptio
Thanks for the response we will try this.
Regards,
Radhika
-Original Message-
From: Zdeněk Henek [mailto:vrab...@gmail.com]
Sent: Tuesday, September 19, 2017 2:27 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat 7 giving java.lang.OutOfMemoryError: unable to create new
native thread
Hi,
try configure HTTP NIO
https://tomcat.apache.org/tomcat-7.0-doc/config/http.html#NIO_specific_configuration
or upgrade to Tomcat 8 where HTTP NIO is on by default.
This could help in case your server is able to process the requests e.g.
you have spike where you have to process thousands of re
On Wed, Jun 14, 2017 at 2:33 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Chris,
>
> On 6/14/17 10:17 AM, Chris Cheshire wrote:
>> On Tue, Jun 13, 2017 at 6:06 PM, Mark Thomas
>> wrote:
>>
>>> On 13/06/17 22:01, Mark Thomas wrote:
On 13/06/17 15:27,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 6/14/17 10:17 AM, Chris Cheshire wrote:
> On Tue, Jun 13, 2017 at 6:06 PM, Mark Thomas
> wrote:
>
>> On 13/06/17 22:01, Mark Thomas wrote:
>>> On 13/06/17 15:27, Chris Cheshire wrote:
>>
>>
>>
I'm bewildered at why tomcat operate
On Tue, Jun 13, 2017 at 6:06 PM, Mark Thomas wrote:
> On 13/06/17 22:01, Mark Thomas wrote:
> > On 13/06/17 15:27, Chris Cheshire wrote:
>
>
>
> >> I'm bewildered at why tomcat operates this way when it comes to Numbers
> and
> >> Strings. Why is it insistent on coercion when null and zero are
>
On 13/06/17 22:01, Mark Thomas wrote:
> On 13/06/17 15:27, Chris Cheshire wrote:
>> I'm bewildered at why tomcat operates this way when it comes to Numbers and
>> Strings. Why is it insistent on coercion when null and zero are absolutely
>> not the same value. If this is because of autoboxing,
On 13/06/17 15:27, Chris Cheshire wrote:
> On Tue, Jun 6, 2017 at 2:29 PM, Mark Thomas wrote:
>
>> On 31/05/17 23:31, Chris Cheshire wrote:
>>> I am using tomcat 7 on CentOS 7 and I need to pass a null value to tag
>>> attributes of type Long/Integer/Float, however it is *always* coerced to
>>> z
5
-XX:+UseTLAB
-XX:G1HeapRegionSize=32m -XX:-UseAdaptiveSizePolicy -XX:MaxMetaspaceSize=512m
-XX:-UseSplitVerifier "
-Original Message-
From: Chris Cheshire [mailto:yahoono...@gmail.com]
Sent: Tuesday, June 13, 2017 7:58 PM
To: Tomcat Users List
Subject: Re: tomcat 7, null tag attributes
On Tue, Jun 6, 2017 at 2:29 PM, Mark Thomas wrote:
> On 31/05/17 23:31, Chris Cheshire wrote:
> > I am using tomcat 7 on CentOS 7 and I need to pass a null value to tag
> > attributes of type Long/Integer/Float, however it is *always* coerced to
> > zero.
> >
> > <%@attribute name="parentId" requ
On 31/05/17 23:31, Chris Cheshire wrote:
> I am using tomcat 7 on CentOS 7 and I need to pass a null value to tag
> attributes of type Long/Integer/Float, however it is *always* coerced to
> zero.
>
> <%@attribute name="parentId" required="true" rtexprvalue="true"
> type="java.lang.Long" %>
>
> C
Awesome, this will point me in the right direction on where to look and how
to get this deployed. Thanks!
On Thu, Jun 1, 2017 at 11:55 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Kerry,
>
> On 6/1/17 10:47 AM, Kerry Hazel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 6/1/17 10:51 AM, Chris Cheshire wrote:
> 7.0.77 (latest version in EPEL repository)
>
> On Thu, Jun 1, 2017 at 10:27 AM, Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
> Chris,
>
> On 5/31/17 6:31 PM, Chris Cheshire wro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kerry,
On 6/1/17 10:47 AM, Kerry Hazelton wrote:
> I am attempting to deploy a managed antivirus agent to two
> different machines - one runs RHEL 7.3, kernel version 3.10.0-514;
> the other runs Microsoft Windows 2012 R2 - and both are hosting web
7.0.77 (latest version in EPEL repository)
On Thu, Jun 1, 2017 at 10:27 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Chris,
>
> On 5/31/17 6:31 PM, Chris Cheshire wrote:
> > I am using tomcat 7 on CentOS 7 and I need to pas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 5/31/17 6:31 PM, Chris Cheshire wrote:
> I am using tomcat 7 on CentOS 7 and I need to pass a null value to
> tag attributes of type Long/Integer/Float, however it is *always*
> coerced to zero.
>
> <%@attribute name="parentId" required="
On 10/03/17 14:07, Subhro Paul wrote:
> Hi All,
>
> We need to install tomcat 7.0.68 or higher version on Sun Solaris 10. Can you
> let me know if there is any version compatibility matrix for Tomcat 7 ?
http://tomcat.apache.org/whichversion.html
The OS doesn't matter. What matters is the Java
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kyle,
On 10/19/16 4:21 PM, Edwards, Kyle wrote:
> I'm attempting to deploy a JSR-356 (WebSocket) application to a
> Tomcat server. The application works beautifully on my local
> IntelliJ/Tomcat 7.0.52 environment, but when I deploy it to the
> s
I think I figured it out. It looks like this version of Tomcat in Ubuntu
doesn't ship with the WebSocket implementation, as per this ticket:
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1326687
I will upgrade Tomcat and come back if I have any more problems.
Kyle
-Original Messag
z
> [mailto:ch...@christopherschultz.net] Sent: Tuesday, August 23,
> 2016 1:43 PM To: Tomcat Users List
> Subject: Re: Tomcat 7 context.xml update questions
>
> John,
>
> On 8/22/16 1:08 PM, John Beaulaurier -X (jbeaulau - ADVANCED
> NETWORK INFORMATION INC at Cisco) wrote:
server status page at hostname:port/manger/status
I was hoping to see that attribute setting noted looking at "Complete Server
Status"
-John
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Tuesday, August 23, 2016 1:43 PM
To: Tomcat U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
On 8/22/16 1:08 PM, John Beaulaurier -X (jbeaulau - ADVANCED NETWORK
INFORMATION INC at Cisco) wrote:
> I have two questions regarding an update to the context.xml file.
> First I understood that any changes made to the context.xml file
> wo
2016-06-30 23:32 GMT+09:00 Nir Dweck :
> I am using tomcat connection pool (tomcat 7) in my application (java
> application) to connect to a remote Oracle DB on an Azure machine. My
> connection pool configuration is as follow:
>
> PoolProperties p = new PoolProperties();
> p.setUrl(connS
Thanks folks, appreciate your time and suggestions!
On 3 Jul 2016 3:44 a.m., "Christopher Schultz"
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Daniel,
>
> On 7/1/16 6:28 PM, Daniel Savard wrote:
> > 2016-07-01 16:21 GMT-04:00 Christopher Schultz
> > >> :
> >
> >> -BEGIN PG
On 7/1/16 11:35 PM, Nir Dweck wrote:
> -Original Message-
> From: Phil Steitz [mailto:phil.ste...@gmail.com]
> Sent: Friday, July 01, 2016 9:16 PM
> To: users@tomcat.apache.org
> Subject: Re: tomcat 7 connection pool validation interval
>
> On 7/1/16 7:1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel,
On 7/1/16 6:28 PM, Daniel Savard wrote:
> 2016-07-01 16:21 GMT-04:00 Christopher Schultz
> > :
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Greg,
>>
>> On 7/1/16 3:03 AM, Greg Beresnev wrote:
>>> Thanks Daniel - any idea whi
-Original Message-
From: Phil Steitz [mailto:phil.ste...@gmail.com]
Sent: Friday, July 01, 2016 9:16 PM
To: users@tomcat.apache.org
Subject: Re: tomcat 7 connection pool validation interval
On 7/1/16 7:14 AM, Nir Dweck wrote:
> -Original Message-
> From: Phil
2016-07-01 16:21 GMT-04:00 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Greg,
>
> On 7/1/16 3:03 AM, Greg Beresnev wrote:
> > Thanks Daniel - any idea which cipher in particular needs to be
> > absent in order for the SHA-1-based connection/authentication was
> > r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Greg,
On 7/1/16 3:03 AM, Greg Beresnev wrote:
> Thanks Daniel - any idea which cipher in particular needs to be
> absent in order for the SHA-1-based connection/authentication was
> rejected/failed?
I'm afraid Daniel may have confused the issue, be
On 7/1/16 7:14 AM, Nir Dweck wrote:
> -Original Message-
> From: Phil Steitz [mailto:phil.ste...@gmail.com]
> Sent: Thursday, June 30, 2016 6:57 PM
> To: Tomcat Users List
> Subject: Re: tomcat 7 connection pool validation interval
>
>
>
>>> On Jun 30, 2
-Original Message-
From: Phil Steitz [mailto:phil.ste...@gmail.com]
Sent: Thursday, June 30, 2016 6:57 PM
To: Tomcat Users List
Subject: Re: tomcat 7 connection pool validation interval
>> On Jun 30, 2016, at 9:32 AM, Nir Dweck wrote:
>>
>> I am using tomcat connec
On 01/07/2016 08:03, Greg Beresnev wrote:
> Thanks Daniel - any idea which cipher in particular needs to be absent in
> order for the SHA-1-based connection/authentication was rejected/failed?
I recommend using SSLLabs to test your site.
Also, the version of Java you use is important. See this pa
Thanks Daniel - any idea which cipher in particular needs to be absent in
order for the SHA-1-based connection/authentication was rejected/failed?
regards,
Greg
On Fri, Jul 1, 2016 at 4:53 PM, Daniel Savard
wrote:
> 2016-06-30 23:05 GMT-04:00 Greg Beresnev :
>
> > Hi,
> >
> > We're in the pr
2016-06-30 23:05 GMT-04:00 Greg Beresnev :
> Hi,
>
> We're in the process of updating our web application to stop using SHA-1
> certificates and I was wondering if there was some way to configure Tomcat
> (we're on version 7.0.39 - yes, I know, we are pretty old-school and should
> get with the
> On Jun 30, 2016, at 9:32 AM, Nir Dweck wrote:
>
> I am using tomcat connection pool (tomcat 7) in my application (java
> application) to connect to a remote Oracle DB on an Azure machine. My
> connection pool configuration is as follow:
>
>PoolProperties p = new PoolProperties();
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tanming,
On 6/21/16 9:04 AM, tanming1...@163.com wrote:
> Hi, I had done some stress tests on Apache Tomcat/7.0.47 and found
> that tomcat didn't taken full advantage of hardware resources. I
> had used Apache Benchmark tool(ab) to do benckmark,and
Thank you David!!
-Gokul
On Thu, Jun 2, 2016 at 6:16 AM, David kerber wrote:
> On 6/2/2016 6:50 AM, Gokul wrote:
>
>> Hello,
>>
>> I am running tomcat 7.0.65.
>>
>> Currently the tomcat is running on JDK 1.6. Can someone please confirm if
>> there is any performance impact if tomcat 7 would run
On 6/2/2016 6:50 AM, Gokul wrote:
Hello,
I am running tomcat 7.0.65.
Currently the tomcat is running on JDK 1.6. Can someone please confirm if
there is any performance impact if tomcat 7 would run on JDK 1.6.
I have never noticed any, though I haven't done any formal tests. I
sincerely doub
On 17.05.2016 18:14, Mark Thomas wrote:
On 17/05/2016 16:49, André Warnier (tomcat) wrote:
Hello experts.
What does the following mean,
The constant values are from the Java virtual machine specification and
related to new features added in Java 7.
Those errors mean that the byte scanning co
On 17/05/2016 16:49, André Warnier (tomcat) wrote:
> Hello experts.
>
> What does the following mean,
The constant values are from the Java virtual machine specification and
related to new features added in Java 7.
Those errors mean that the byte scanning code (o.a.t.u.bcel, copied from
Apache C
On 5/17/2016 11:49 AM, André Warnier (tomcat) wrote:
Hello experts.
What does the following mean, and/or (better) what do we have to do to
get rid of these ?
Note : below is only a small sample, there are hundreds of these
in-between (about 2.3 MB of logfile worth of them).
It looks to me lik
Richard,
On 4/17/16 12:51 PM, rich...@xentu.com wrote:
> On 2016-04-17 14:29, Konstantin Kolinko wrote:
>> 2016-04-17 15:26 GMT+03:00 :
>>> I posted this same query at stackoverflow a couple of days back, but
>>> with no
>>> response, although I've simplified the issue very slightly since then.
>
On 2016-04-17 14:29, Konstantin Kolinko wrote:
2016-04-17 15:26 GMT+03:00 :
I posted this same query at stackoverflow a couple of days back, but
with no
response, although I've simplified the issue very slightly since then.
http://stackoverflow.com/questions/36653744/tomcat-7-wrong-realm-bein
2016-04-17 15:26 GMT+03:00 :
> I posted this same query at stackoverflow a couple of days back, but with no
> response, although I've simplified the issue very slightly since then.
>
> http://stackoverflow.com/questions/36653744/tomcat-7-wrong-realm-being-used
>
> I have a realm defined in server.
ilto:ch...@christopherschultz.net]
Sent: Monday, March 07, 2016 10:33 AM
To: Tomcat Users List
Subject: Re: Tomcat 7 Web Service Shutdown Can't Stop Threads
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
On 3/7/16 9:51 AM, Chris Brown wrote:
> Tomcat is shutting down the web service
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
On 3/7/16 9:51 AM, Chris Brown wrote:
> Tomcat is shutting down the web service when I deploy a new .war
> file.
Okay. You said you were closing the connection pool, though:
On 3/4/16 2:13 PM, Chris Brown wrote:
> I added a ServletContextLis
...@ncci.com
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, March 07, 2016 9:47 AM
To: Tomcat Users List
Subject: Re: Tomcat 7 Web Service Shutdown Can't Stop Threads
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
On 3/7/16 8:
doing or how they should be terminated.
- -chris
> -Original Message- From: Christopher Schultz
> [mailto:ch...@christopherschultz.net] Sent: Friday, March 04, 2016
> 4:33 PM To: Tomcat Users List Subject: Re: Tomcat 7 Web Service
> Shutdown Can't Stop Threads
>
> Ch
Consultant
National Council on
Compensation Insurance
901 Peninsula Corporate Circle
Boca Raton, FL 33487-1362
(P) 561-893-2324
chris_br...@ncci.com
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Friday, March 04, 2016 4:33 PM
To: Tomcat Users List
S
Chris sing a song for us.
Em 04/03/2016 16:13, "Chris Brown" escreveu:
> Tomcat version: 7.0.42
> Server OS: Sun Solaris
> UCP Version: Oracle 12c
> Oracle Driver: ojdbc7
> JDK version: 1.8.0_31
>
> Issue Description:
> When tomcat shuts down our web service during a hot deployment threads are
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
On 3/4/16 2:13 PM, Chris Brown wrote:
> Tomcat version: 7.0.42 Server OS: Sun Solaris UCP Version: Oracle
> 12c Oracle Driver: ojdbc7
That doesn't look like an Oracle JDBC driver version I've seen before.
Can you clarify?
> JDK version: 1.8.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Qadeer,
On 2/14/16 1:50 PM, Qadeer Khan wrote:
>
> Hello,
>
> I am trying to hookup ssl connection between mod_Cluster load
> balancer and tomcat 7 and seems to be following everything but when
> I start tomcat server, I am getting the following err
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill,
On 2/4/16 12:52 PM, Bill Kelm wrote:
> Not sure if anyone has seen this before, whenever we go to
> configure the SSL connector and set the connector port to 8443, on
> tomcat startup they are getting rewritten to another random port.
>
> So
George,
Thanks for the lead to the startup script. That was exactly it, in our
configuration our CATALINA_BASE is /usr/share/tomcat7 and that is what was
triggering the random port assignment:
if [ "$CATALINA_HOME" != "/usr/share/tomcat" -a "$RETVAL" -eq "0" ]; then
# Create a tomcat di
On 2/4/2016 10:52 AM, Bill Kelm wrote:
Not sure if anyone has seen this before, whenever we go to configure the
SSL connector and set the connector port to 8443, on tomcat startup they
are getting rewritten to another random port.
So we will have:
and I end up with this in the ser
Am 07.01.2016 um 11:50 schrieb ANISH S IYER:
hello
while am deploying java application in webapps,say test contains spring and
hibernate,with mysql db. it work normally
while i also deploy another apps in in the tomcat say demo, all deployment
are okay, but it accesses the database of test, ins
On 30 September 2015 16:13:38 BST, Kernel freak wrote:
>Hi guys,
>
>I am trying to setup https on tomcat, but not having much luck since 5
>hours. I am always getting no_cypher_overlap errror.
>The certificate is not self-signed, but issued. The crt file I am
>importing
>for both root and tomcat a
On 9/30/2015 11:13 AM, Kernel freak wrote:
Hi guys,
I am trying to setup https on tomcat, but not having much luck since 5
hours. I am always getting no_cypher_overlap errror.
This error means that your server and the client browser don't have any
cypers in common (there are none that they ca
On 22/09/2015 01:31, Igor Cicimov wrote:
> On 21/09/2015 7:47 PM, "Mark Thomas" wrote:
>>
>> On 21/09/2015 10:45, Igor Cicimov wrote:
>>> On Mon, Sep 21, 2015 at 6:21 PM, Mark Thomas wrote:
>>>
On 21/09/2015 08:37, Igor Cicimov wrote:
> Hi all,
>
> After enabling the APR/Native c
On 21/09/2015 7:47 PM, "Mark Thomas" wrote:
>
> On 21/09/2015 10:45, Igor Cicimov wrote:
> > On Mon, Sep 21, 2015 at 6:21 PM, Mark Thomas wrote:
> >
> >> On 21/09/2015 08:37, Igor Cicimov wrote:
> >>> Hi all,
> >>>
> >>> After enabling the APR/Native connector I can see the following
warning
> >>
On 21/09/2015 10:45, Igor Cicimov wrote:
> On Mon, Sep 21, 2015 at 6:21 PM, Mark Thomas wrote:
>
>> On 21/09/2015 08:37, Igor Cicimov wrote:
>>> Hi all,
>>>
>>> After enabling the APR/Native connector I can see the following warning
>>> messages upon tomcat restart:
>>>
>>> WARNING: [SetAllProper
On Mon, Sep 21, 2015 at 6:21 PM, Mark Thomas wrote:
> On 21/09/2015 08:37, Igor Cicimov wrote:
> > Hi all,
> >
> > After enabling the APR/Native connector I can see the following warning
> > messages upon tomcat restart:
> >
> > WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting
>
On 21/09/2015 08:37, Igor Cicimov wrote:
> Hi all,
>
> After enabling the APR/Native connector I can see the following warning
> messages upon tomcat restart:
>
> WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property
> 'SSLDisableCompression' to 'true' did not find a matching
1 - 100 of 869 matches
Mail list logo
