Re: mod-jk (1.2.37) crashes Apache 2 (2.4.7) occasionally with a buffer overflow on Ubuntu 14.04 x64

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 > >

Re: mod-jk (1.2.37) crashes Apache 2 (2.4.7) occasionally with a buffer overflow on Ubuntu 14.04 x64

-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

Websockets : differents behaviours on connection when using WS or WSS

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 :

Re: Need help setting up SSL on Tomcat 8

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

Re: java

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

Re: Need help setting up SSL on Tomcat 8

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

Re: Websockets : differents behaviours on connection when using WS or WSS

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

Re: mod-jk (1.2.37) crashes Apache 2 (2.4.7) occasionally with a buffer overflow on Ubuntu 14.04 x64

-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

Re: Need help setting up SSL on Tomcat 8

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?

AW: AW: java

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

RE: java

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

AW: java

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

Re: mod-jk (1.2.37) crashes Apache 2 (2.4.7) occasionally with a buffer overflow on Ubuntu 14.04 x64

-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

Re: AW: java

-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

RE: java

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)

Re: mod_jk errors

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)

Re: Websockets : differents behaviours on connection when using WS or WSS

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.

Re: AW: SocketTimeoutException in CoyoteInputStream

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 >>>

Re: AW: AW: java

-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

RE: A complex issue concerning the application lifecycle, MBeans and Spring

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:

SocketTimeoutException in CoyoteInputStream

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

Re: SocketTimeoutException in CoyoteInputStream

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

AW: SocketTimeoutException in CoyoteInputStream

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