sing: pattern="%v %h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
>> \"%{User-Agent}i\" \"%{cookie}i\"" />
>>
>> I am running: tomcat 8.5.23openjdk version "1.8.0_232"
>> Redhat 7.7 We are using an internal
ot;%{User-Agent}i\" \"%{cookie}i\"" />
>
> I am running:
> tomcat 8.5.23 openjdk version "1.8.0_232" Redhat 7.7
> We are using an internal proxy.
> Why do we have missing fields
Hello
The server provides the localhost_access_log files with the following fields
missing %{cookie} %{Referer} %u
I am using: pattern="%v %h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-Agent}i\" \"%{cookie}i\"" /&
may find enabling Tomcat's debug logging for HTTP/2 instructive.
>
> Mark
>
>
> >
> > -Original Message-
> > From: Mark Thomas
> > Sent: martes, 26 de febrero de 2019 13:45
> > To: users@tomcat.apache.org
> > Subject: Re: tomcat 8.5.23 can not modify
---
> From: Mark Thomas
> Sent: martes, 26 de febrero de 2019 13:45
> To: users@tomcat.apache.org
> Subject: Re: tomcat 8.5.23 can not modify maxconcurrentstream setting
>
> See
> https://github.com/apache/tomcat/blob/8.5.x/test/org/apache/coyote/http2/TestHttp2Section_5_1.j
>> See
>>
https://github.com/apache/tomcat/blob/8.5.x/test/org/apache/coyote/http2/TestHttp2Section_5_1.java#L174
>From what I see in the test a STREAM_REFUSED is returned when a the
maxConcurrentStream is set to one. Yet I'd like to understand how this
value is changed internally. I think the
as
Sent: martes, 26 de febrero de 2019 13:45
To: users@tomcat.apache.org
Subject: Re: tomcat 8.5.23 can not modify maxconcurrentstream setting
See
https://github.com/apache/tomcat/blob/8.5.x/test/org/apache/coyote/http2/TestHttp2Section_5_1.java#L174
Mark
On 26/02/2019 11:01, Helena Carbajo wrot
See
https://github.com/apache/tomcat/blob/8.5.x/test/org/apache/coyote/http2/TestHttp2Section_5_1.java#L174
Mark
On 26/02/2019 11:01, Helena Carbajo wrote:
> I'm trying to modify the value of MaxConcurrentStream for the tomcat server
> in order to check that it returns a STREAM_REFUSED when the
I'm trying to modify the value of MaxConcurrentStream for the tomcat server in
order to check that it returns a STREAM_REFUSED when the client uses more
streams, but I don't manage to change the default unlimited value.
I've been inspecting the tomcat server code with a debugger and I saw it ent
I'm trying to modify the value of MaxConcurrentStream for the tomcat server in
order to check that it returns a STREAM_REFUSED when the client uses more
streams, but I don't manage to change the default unlimited value.
I've been inspecting the tomcat server code with a debugger and I saw it ente
On Tue, Feb 12, 2019 at 11:37 AM Herb Burnswell
wrote:
>
>
> On Tue, Feb 12, 2019 at 11:26 AM Mark Thomas wrote:
>
>> On 12/02/2019 19:21, Herb Burnswell wrote:
>> > All,
>> >
>> > Tomcat: 8.5.23
>> > OS: RHEL 7.5
>> >
>&
On Tue, Feb 12, 2019 at 11:26 AM Mark Thomas wrote:
> On 12/02/2019 19:21, Herb Burnswell wrote:
> > All,
> >
> > Tomcat: 8.5.23
> > OS: RHEL 7.5
> >
> > I am attempting to set up Tomcat to use two keystore's with SNI. Tomcat
> > starts succe
On 12/02/2019 19:21, Herb Burnswell wrote:
> All,
>
> Tomcat: 8.5.23
> OS: RHEL 7.5
>
> I am attempting to set up Tomcat to use two keystore's with SNI. Tomcat
> starts successfully but but I receive a timeout when trying to access
> either of the defined server nam
All,
Tomcat: 8.5.23
OS: RHEL 7.5
I am attempting to set up Tomcat to use two keystore's with SNI. Tomcat
starts successfully but but I receive a timeout when trying to access
either of the defined server names.
Here is a single server name configuration that works successfully:
Here i
Hi.
Glad if I could be of even limited help.
It would be nice if you sent to the list a complete layout of your solution, to put into
the Tomcat FAQ (e.g. like here : https://wiki.apache.org/tomcat/HowTo, in section 3
Configuration)
That may help someone else in the future.
On 20.09.2018 15:
André,
I was able to use the reference you made about making tomcatAuthentication
false. With this Tomcat setting combined with HTTPD's mod_proxy_ajp proxy
rules I was able to get this working. I am still testing this but looks
clear to me that this is the solution. Thanks for the quick responses
Hi.
Much better..
I don't know if I will be able to help you, considering my little knowledge of Kerberos,
but I'm sure that someone else now will be.
On 19.09.2018 16:08, Thomas Delaney wrote:
Here is more detail into what I went through for setting up Apache Tomcat.:
I configured each Apache
Here is more detail into what I went through for setting up Apache Tomcat.:
I configured each Apache Tomcat instance using this bit of documentation:
SPNEGO
http://spnego.sourceforge.net/
I also used this documentation in order to get my workstation to accept
Kerberos authentication and not defaul
On 19.09.2018 13:57, André Warnier (tomcat) wrote:
On 18.09.2018 23:24, Thomas Delaney wrote:
Hello All,
I have recently configured Apache Tomcat on a SuSe Enterprise 12 SP3 server
to get Kerberos SSO working with a web client application. I have also in
addition configured Apache HTTPD 2.4.29
On 18.09.2018 23:24, Thomas Delaney wrote:
Hello All,
I have recently configured Apache Tomcat on a SuSe Enterprise 12 SP3 server
to get Kerberos SSO working with a web client application. I have also in
addition configured Apache HTTPD 2.4.29 on the same machine.When I reach
that website I am f
Hello All,
I have recently configured Apache Tomcat on a SuSe Enterprise 12 SP3 server
to get Kerberos SSO working with a web client application. I have also in
addition configured Apache HTTPD 2.4.29 on the same machine.When I reach
that website I am failing to get SSO working. The web server is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Lawrence,
On 2/27/18 12:42 PM, Lawrence Lim wrote:
> Our company's standard is Java 8. That's the main reason for
> choosing Tomcat 8 over the latest.
I think Felix was asking why you were installing Tomcat 8.5.23 instead
of Tomc
elix Schumacher [mailto:felix.schumac...@internetallee.de]
Sent: Sunday, February 25, 2018 3:44 AM
To: users@tomcat.apache.org
Subject: Re: [External] RE: Tomcat 8.5.23
Am Freitag, den 23.02.2018, 15:26 + schrieb Lawrence Lim:
> I installed tomcat via untar, something tar -zxf apache-tomcat-
> 8.5.23.tar.gz
Am Freitag, den 23.02.2018, 15:26 + schrieb Lawrence Lim:
> I installed tomcat via untar, something tar -zxf apache-tomcat-
> 8.5.23.tar.gz.
Any reason for not using the latest available tomcat?
>
> I am running Java 8 and no security manager I know of.
OK
>
> I alrea
On 16 Feb 2018 4:40 am, "Lawrence Lim" wrote:
Hi,
I just installed tomcat 8.5.23. I am having problems deploying web apps via
manager. To reproduce:
1. Login to tomcat manager
2. Go to " WAR file to deploy"
3. Pick a war file
Error message
I installed tomcat via untar, something tar -zxf apache-tomcat-8.5.23.tar.gz.
I am running Java 8 and no security manager I know of.
I already did a chmod 777 in the tomcat directory.
Regards,
Lawrence Lim
Software Developer
—
ENBRIDGE
TEL: 780-969-6208
10175 101 St NW, Edmonton
t;enbridge.com
>Integrity. Safety. Respect.
>
>-Original Message-
>From: Satish Chhatpar 02 [mailto:chhatp...@cpwplc.com]
>Sent: Thursday, February 15, 2018 10:58 AM
>To: users@tomcat.apache.org
>Subject: [External] Re: Tomcat 8.5.23
>
>Which op
I undeploy.
> >>
> >> Lawrence Lim Software Developer -
> >>
> >> ENBRIDGE TEL: 780-969-6208 10175 101 St NW, Edmonton, Alberta
> >> T5J 0H3
> >>
> >> enbridge.com Integrity. Safety. Respect.
> >>
> >> -Original Me
t;> [mailto:chhatp...@cpwplc.com] Sent: Thursday, February 15, 2018
>> 10:58 AM To: users@tomcat.apache.org Subject: [External] Re:
>> Tomcat 8.5.23
>>
>> Which operating system? Did you check the logs?
>>
>> Sent using OWA for iPhone
ailto:chhatp...@cpwplc.com]
> Sent: Thursday, February 15, 2018 10:58 AM
> To: users@tomcat.apache.org
> Subject: [External] Re: Tomcat 8.5.23
>
> Which operating system?
> Did you check the logs?
>
> Sent using OWA for iPhone
>
. Safety. Respect.
-Original Message-
From: Satish Chhatpar 02 [mailto:chhatp...@cpwplc.com]
Sent: Thursday, February 15, 2018 10:58 AM
To: users@tomcat.apache.org
Subject: [External] Re: Tomcat 8.5.23
Which operating system?
Did you check the logs?
Sent using OWA for iPhone
Which operating system?
Did you check the logs?
Sent using OWA for iPhone
From: Lawrence Lim
Sent: Thursday, February 15, 2018 11:09:54 PM
To: users@tomcat.apache.org
Subject: Tomcat 8.5.23
Hi,
I just installed tomcat 8.5.23. I am having problems deploying
Hi,
I just installed tomcat 8.5.23. I am having problems deploying web apps via
manager. To reproduce:
1. Login to tomcat manager
2. Go to " WAR file to deploy"
3. Pick a war file
Error message: FAIL - File upload failed, no file
Workaround: Cop
ctPort="${bio-ssl-localhost.https.port}"
> scheme="https"
> secure="true"
> maxHttpHeaderSize="16384">
>
>
> Problem
> ---
>
> The new version of tomcat has a changed code that is causing my application
> from not able to lo
ctPort="${bio-ssl-localhost.https.port}"
> scheme="https"
> secure="true"
> maxHttpHeaderSize="16384"
>
>
> Problem
> ---
>
> The new version of tomcat has a changed code that is causing my application
> from not able
Context
---
Exact tomcat version, Operating Systems, other configurations-
Current Tomcat version - 8.5.15
Operating Systems - Windows/ Linux
Upgrading to tomcat version - 8.5.23
Application - Java Application.
I have an application with tomcat, say fooapp. I also have a custom
keystore
On 23 November 2017 at 17:20, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Richard,
>
> On 11/23/17 8:28 AM, Richard Tearle wrote:
>> Yes I read through that thread, but we don't really like Java key
>> stores, and I don't think the work around would work for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Richard,
On 11/23/17 8:28 AM, Richard Tearle wrote:
> Yes I read through that thread, but we don't really like Java key
> stores, and I don't think the work around would work for us.
Java keystores are ... awful.
> Instead, I did what perhaps I s
On 23 November 2017 at 05:33, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Richard,
>
> On 11/22/17 8:40 AM, Richard Tearle wrote:
>> Hello
>>
>> Apache Tomcat 8.5.23 Centos 7.4 (3.10.0-514.16.1.el7.x86_64) Java
>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Richard,
On 11/22/17 8:40 AM, Richard Tearle wrote:
> Hello
>
> Apache Tomcat 8.5.23 Centos 7.4 (3.10.0-514.16.1.el7.x86_64) Java
> 1.8.0_152 (with jce) Running in Docker Container
>
> I'm upgrading our applications from
apache.org[mailto:users@tomcat.apache.org]
>> Betreff: Trouble with TLS/SSL and Tomcat 8.5.23
>> Hello
>>
>> Apache Tomcat 8.5.23
>> Centos 7.4 (3.10.0-514.16.1.el7.x86_64)
>> Java 1.8.0_152 (with jce)
>> Running in Docker Container
>>
>> I
Richard,
> Gesendet: Mittwoch, 22. November 2017 um 14:40 Uhr
> Von: "Richard Tearle"
> mailto:richard.tea...@northgateps.com]>
> An: users@tomcat.apache.org[mailto:users@tomcat.apache.org]
> Betreff: Trouble with TLS/SSL and Tomcat 8.5.23
> Hello
>
&
Hello
Apache Tomcat 8.5.23
Centos 7.4 (3.10.0-514.16.1.el7.x86_64)
Java 1.8.0_152 (with jce)
Running in Docker Container
I'm upgrading our applications from Apache Tomcat 8.0.47 to 8.5.23,
but when trying to get TLS/SSL working on a connector I get the
following error:
2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Darin,
On 11/3/17 5:17 PM, dbol...@dsginc.biz wrote:
> From: Christopher Schultz To:
> users@tomcat.apache.org Date: 11/02/2017 02:28 PM Subject:
> Re: TomCat 8.5.23 application not responding
>
>
>
> Darin,
>
>
From: Christopher Schultz
To: users@tomcat.apache.org
Date: 11/02/2017 02:28 PM
Subject:Re: TomCat 8.5.23 application not responding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Darin,
On 11/2/17 12:55 PM, dbol...@dsginc.biz wrote:
> I have a TomCat 8.5.23 service runn
From: Christopher Schultz
To: users@tomcat.apache.org
Date: 11/02/2017 02:28 PM
Subject:Re: TomCat 8.5.23 application not responding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Darin,
On 11/2/17 12:55 PM, dbol...@dsginc.biz wrote:
> I have a TomCat 8.5.23 service runn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Darin,
On 11/2/17 12:55 PM, dbol...@dsginc.biz wrote:
> I have a TomCat 8.5.23 service running on a Windows 2008 R2. It is
> currently running a third party web commerce application. It will
> run great until randomly one day the ap
I have a TomCat 8.5.23 service running on a Windows 2008 R2. It is
currently running a third party web commerce application. It will run
great until randomly one day the application will stop responding. When
you try to go to the application URL it sits and spins. I look at the
catalina
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
George,
On 10/27/17 10:55 AM, George S. wrote:
> I'm seeing some strange ssl errors. They're not reproducible
> consistently, and I think they're because the PRNG is initializing
> after the Connector. Here's some log output:
>
> 26-Oct-2017 17:04
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
(This turned out to be quite long. I honestly think it's worth reading.)
On 10/27/17 5:32 PM, André Warnier (tomcat) wrote:
> There seem to be a recrudescence of interventions on this list
> about SSL/HTTPS, and associated discussions about
On 28.10.2017 00:54, Bob Hall wrote:
> On Friday, October 27, 2017, 2:32:50 PM PDT, André Warnier (tomcat)
wrote:
> > > There seem to be a recrudescence of interventions on this list about
SSL/HTTPS, and
associated discussions about the usage of various randomness sources.> I found
thi
> On Friday, October 27, 2017, 2:32:50 PM PDT, André Warnier (tomcat)
> wrote:
> > > There seem to be a recrudescence of interventions on this list about
>SSL/HTTPS, and
> associated discussions about the usage of various randomness sources.> I
> found this article interesting :> https:/
There seem to be a recrudescence of interventions on this list about SSL/HTTPS, and
associated discussions about the usage of various randomness sources.
I found this article interesting :
https://www.2uo.de/myths-about-urandom/
---
On 27.10.2017 16:55, George S. wrote:
I'm seeing some strange ssl errors. They're not reproducible consistently, and
I think
they're because the PRNG is initializing after the Connector. Here's some log
output:
26-Oct-2017 17:04:08.380 INFO [main] org.apache.coyote.AbstractProtocol.start
Star
I'm seeing some strange ssl errors. They're not reproducible
consistently, and I think they're because the PRNG is initializing after
the Connector. Here's some log output:
26-Oct-2017 17:04:08.380 INFO [main] org.apache.coyote.AbstractProtocol.start Starting
ProtocolHandler ["http-nio-8080"]
On Thu, Oct 26, 2017 at 3:00 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Chris,
>
> On 10/16/17 9:43 AM, Chris Cheshire wrote:
>> On Fri, Oct 13, 2017 at 5:00 PM, Christopher Schultz
>> wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>
>>> When you say yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris and Keiichi,
On 10/17/17 5:31 PM, Chris Cheshire wrote:
> On Tue, Oct 17, 2017 at 3:44 AM, Keiichi Fujino
> wrote:
>> Hi
>>
>> You have set
>> factory="org.apache.tomcat.jdbc.pool.DataSourceFactory". In other
>> words, you do not use (tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 10/16/17 9:43 AM, Chris Cheshire wrote:
> On Fri, Oct 13, 2017 at 5:00 PM, Christopher Schultz
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>
>> When you say you have "autocommit disabled in mysql config" what
>> do you mean?
>>
>
>
are comparing with checksum of a different file? E.g.
windows-x86.zip vs windows-x64.zip vs .zip ?
The correct sha1:
5992ca5bf02a6ae6d901eb22e7d3309061b26e42 *apache-tomcat-8.5.23-windows-x86.zip
sha256:
acca2ce6217da70beb8f6b0d58054f2133276bd7328ff51ca51ae0125c1cf586
*apache-tomcat-8.5.23-wi
Hi,
I downloaded the file from all mirror sites (including backups), but I get a
different checksum than the one on the apache site. I am using fsum sha1. Are
the checksums on the site incorrect, or is fsum wrong?
Bill
On Tue, Oct 17, 2017 at 3:44 AM, Keiichi Fujino wrote:
> Hi
>
> You have set factory="org.apache.tomcat.jdbc.pool.DataSourceFactory".
> In other words, you do not use (tomcat)DBCP, you are using Tomcat jdbc-pool.
That's what I meant sorry. Was comparing to commons-dbcp and went
dyslexic on the ac
Hi
You have set factory="org.apache.tomcat.jdbc.pool.DataSourceFactory".
In other words, you do not use (tomcat)DBCP, you are using Tomcat jdbc-pool.
In DBCP, the default of rollbackOnReturn attribute is true.
However, in Tomcat jdbc-pool, the default of rollbackOnReturn( and
commitOnReturn
) att
On Fri, Oct 13, 2017 at 5:00 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> When you say you have "autocommit disabled in mysql config" what do
> you mean?
>
/etc/my.cnf :
[mysqld]
autocommit=0
This turns off autocommit off as a default for all connections. I need
this at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
Sorry, I had the autocommit true/false values mixed up in my mind.
When you say you have "autocommit disabled in mysql config" what do
you mean?
On 10/13/17 10:17 AM, Chris Cheshire wrote:
>
>
> As a further test I just took out my explic
As a further test I just took out my explicit rollback in my
DAOFactory close() method, and swapped back to commons dbcp. Added an
update that wasn't explicitly committed, and it correctly did not get
committed when the connection was closed. Swapped back to tomcat dbcp
and repeated, it got commi
On Thu, Oct 12, 2017 at 11:16 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Chris,
>
> On 10/11/17 5:21 PM, Chris Cheshire wrote:
>> Working on a migration from 7 to 8.5, and in it I am now using the
>> tomcat dbcp, instead of apache commons dbcp.> I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 10/11/17 5:21 PM, Chris Cheshire wrote:
> Working on a migration from 7 to 8.5, and in it I am now using the
> tomcat dbcp, instead of apache commons dbcp.> I have found that
> with no other changes to the db code (except the factory para
Working on a migration from 7 to 8.5, and in it I am now using the
tomcat dbcp, instead of apache commons dbcp. I have found that with no
other changes to the db code (except the factory param for the
resource), it is working fine other than there is an implicit commit
happening when I close a conn
On Thu, Oct 5, 2017 at 7:11 PM, Eirik Lykken
wrote:
>
> 05-Oct-2017 17:13:32.535 SEVERE
> [https-openssl-nio2-94.229.64.230-443-exec-19701]
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process Error
> reading request, ignored
> java.lang.IllegalStateException
> at org.apache.c
Dear All,
We are running Tomcat 8.5.23 production server on a CentOS 6.9 machine, Oracle
JVM 1.8.0_144, and OpenSSL 1.1.0f. The server hosts a web application where
almost all the traffic is https.
We used to have a Http11NioProtocol connector with Java SSL using HTTP 1.1 but
we switched to
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 8.5.23.
Tomcat 8.x users should normally be using 8.5.x releases in preference
to 8.0.x releases.
Apache Tomcat 8 is an open source software implementation of the Java
Servlet, JavaServer Pages, Java Unified Expression
71 matches
Mail list logo
