Hi Mark,
I just applied the patchset to the released source tarball of 8.0.36 and with
performing some cycling and deployments of applications I confirm the issue has
gone as expected.
with thanks again
Guido
>-Original Message-
>From: Guido Jäkel [mailto:g.jae...@dnb.de]
>Sent: Thu
Hi
I am getting the following exception:
2016-07-18 07:46:52.667 /http/httpmodule WARN null - error during upload
| java.net.SocketTimeoutException
| at
org.apache.tomcat.util.net.NioBlockingSelector.read(NioBlockingSelector.java:202)
| at
org.apache.tomcat.util.net.NioSelectorPool
On 18 July 2016 12:06:42 CEST, "Steffen Heil (Mailinglisten)"
wrote:
Tomcat version?
Mark
>Hi
>
>
>I am getting the following exception:
>
>2016-07-18 07:46:52.667 /http/httpmodule WARN null - error during
>upload
>| java.net.SocketTimeoutException
>| at
>org.apache.tomcat.util.net.NioB
8.0.26
> -Ursprüngliche Nachricht-
> Von: Mark Thomas [mailto:ma...@apache.org]
> Gesendet: Montag, 18. Juli 2016 13:37
> An: Tomcat Users List
> Betreff: Re: SocketTimeoutException in CoyoteInputStream
>
> On 18 July 2016 12:06:42 CEST, "Steffen Heil (Mailinglisten)"
> wrote:
>
> Tom
On 6 July 2016 at 00:09, Christopher Schultz
wrote:
> > From what I understand a buffer overflow would only happen for
> > FD_SET if the fd_set gets over 1024 descriptors. I made sure that
> > my ulimit for open files is set and applied large enough, so that's
> > not it.
>
> There's nothing magi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 7/18/16 8:53 AM, Michael Diener wrote:
> On 6 July 2016 at 00:09, Christopher Schultz
> wrote:
>
>>> From what I understand a buffer overflow would only happen for
>>> FD_SET if the fd_set gets over 1024 descriptors. I made sure
>>> t
Hi.
I am using Tomcat 8.0.36 with Atmosphere 2.4.5 (
https://github.com/Atmosphere/atmosphere ) to implement WebSockets with
fallbacks such as long polling.
I am writing tests using Tomcat JSR356 implementation.
I studied your WebSocket samples and I am using a fake trustore :
Clien
On Thu, Jul 14, 2016 at 8:15 AM, Ognjen Blagojevic <
ognjen.d.blagoje...@gmail.com> wrote:
> Sean,
>
> On 13.7.2016 21:56, Sean Son wrote:
>
>> Thank you for your answer guys. Is there anywhere in the Tomcat config
>> files that I would need to specify the DNS name? Like in Apache we
>> would spe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 7/18/16 10:10 AM, Christopher Schultz wrote:
> Michael,
>
> On 7/18/16 8:53 AM, Michael Diener wrote:
>> On 6 July 2016 at 00:09, Christopher Schultz
>> wrote:
>
From what I understand a buffer overflow would only happen
fo
On 18.07.2016 16:33, Sean Son wrote:
On Thu, Jul 14, 2016 at 8:15 AM, Ognjen Blagojevic <
ognjen.d.blagoje...@gmail.com> wrote:
Sean,
On 13.7.2016 21:56, Sean Son wrote:
Thank you for your answer guys. Is there anywhere in the Tomcat config
files that I would need to specify the DNS name? L
On Mon, Jul 18, 2016 at 10:47 AM, André Warnier (tomcat)
wrote:
> On 18.07.2016 16:33, Sean Son wrote:
>
>> On Thu, Jul 14, 2016 at 8:15 AM, Ognjen Blagojevic <
>> ognjen.d.blagoje...@gmail.com> wrote:
>>
>> Sean,
>>>
>>> On 13.7.2016 21:56, Sean Son wrote:
>>>
>>> Thank you for your answer guys.
Hi
> With jdk 1.8.0.45 our ldap communication is giving results. As soon as we
> change tomcat to use jdk1.8.0_51, I am getting below
> exception. I am not sure security changes in jdk 1.8.0_51 preventing the ldap
> certificate loaded in cacerts in java not communicating
> properly to our ldap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 7/18/16 10:10 AM, Christopher Schultz wrote:
> Michael,
>
> On 7/18/16 8:53 AM, Michael Diener wrote:
>> On 6 July 2016 at 00:09, Christopher Schultz
>> wrote:
>
From what I understand a buffer overflow would only happen
fo
Thanks Steffen for letting me know. Did you also post your issue in java
community? Did you get any response? Currently we are using 1.8.0_45. In the
future we have requirement to upgrade and got stuck here.
-Original Message-
From: Steffen Heil (Mailinglisten) [mailto:li...@steffen-heil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steffen,
On 7/18/16 10:54 AM, Steffen Heil (Mailinglisten) wrote:
>> With jdk 1.8.0.45 our ldap communication is giving results. As
>> soon as we change tomcat to use jdk1.8.0_51, I am getting below
>> exception. I am not sure security changes in j
Hi
> > I am not sure that this related, be we were having issues after
> > updating from 1.8.0_31 to 1.8.0_72 with certificates signed by
> > root-cas that have a md5 signature. While the CA signature in the CA
> > certificate does not provide any security, a bug in the jre rejected
> > the certi
Steffen,
Is it also possible to test your stuff with jdk1.8.0_51 so that we will know
something must be wrong with security in jdk1.8.0_51?
Appreciate your help
Ambica.
-Original Message-
From: Sanka, Ambica [mailto:asa...@atpco.net]
Sent: Monday, July 18, 2016 11:00 AM
To: Tomcat Users
Am 18.07.2016 um 17:14 schrieb Sanka, Ambica:
Steffen,
Is it also possible to test your stuff with jdk1.8.0_51 so that we will know
something must be wrong with security in jdk1.8.0_51?
Appreciate your help
Ambica.
You may want to follow the changes in
http://www.oracle.com/technetwork/java/
On 18/07/2016 16:25, l.pe...@senat.fr wrote:
Hi.
I am using Tomcat 8.0.36 with Atmosphere 2.4.5 (
https://github.com/Atmosphere/atmosphere ) to implement WebSockets
with fallbacks such as long polling.
I am writing tests using Tomcat JSR356 implementation.
I studied your WebSocket samples a
Thank you for both!
On Fri, Jul 15, 2016 at 3:04 AM, Rainer Jung
wrote:
> Am 12.07.2016 um 19:44 schrieb Wayne Li:
>
>> Hi,
>>
>> I have a servlet/jsp application running on tomcat 7.0.47. There are no
>> static html files.
>> Now I am try to use apache 2.4.7 (Ubuntu)
>> as the front and forward
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steffen,
On 7/18/16 11:14 AM, Steffen Heil (Mailinglisten) wrote:
> Hi
>
>
>>> I am not sure that this related, be we were having issues
>>> after updating from 1.8.0_31 to 1.8.0_72 with certificates
>>> signed by root-cas that have a md5 signatur
On 18/07/2016 16:25, l.pe...@senat.fr wrote:
> Hi.
>
> I am using Tomcat 8.0.36 with Atmosphere 2.4.5 (
> https://github.com/Atmosphere/atmosphere ) to implement WebSockets with
> fallbacks such as long polling.
Can you reproduce this without Atmosphere? If not, that suggests an
Atmosphere bug. I
On 18/07/2016 13:55, Steffen Heil (Mailinglisten) wrote:
> 8.0.26
>> Tomcat version?
>>> I am getting the following exception:
>>>
>>> 2016-07-18 07:46:52.667 /http/httpmodule WARN null - error during
>>> upload
>>> | java.net.SocketTimeoutException
>>> | at
>>> org.apache.tomcat.util.n
23 matches
Mail list logo