Re: JVM Crash in tcnative due to concurrency/timing in HTTP/2

2017-06-23 Thread Rémy Maucherat
2017-06-23 16:20 GMT-05:00 Mark Thomas : > On 23/06/17 17:52, l...@kreuser.name wrote: > >> Am 23.06.2017 um 17:32 schrieb Mark Thomas : > > > > >>> However I still see a timing problem, as it is not always happening. > Maybe 5 out of 7 are NULL. If I send more requests immediately after each > o

Re: JVM Crash in tcnative due to concurrency/timing in HTTP/2

2017-06-23 Thread Mark Thomas
On 23/06/17 17:52, l...@kreuser.name wrote: >> Am 23.06.2017 um 17:32 schrieb Mark Thomas : >>> However I still see a timing problem, as it is not always happening. Maybe >>> 5 out of 7 are NULL. If I send more requests immediately after each other >>> NULL is more frequent. >> >> Thanks for

Re: JVM Crash in tcnative due to concurrency/timing in HTTP/2

2017-06-23 Thread logo
Mark, > Am 23.06.2017 um 17:32 schrieb Mark Thomas : > > On 23/06/17 16:02, l...@kreuser.name wrote: >> Mark, >>> >>> Am 23.06.2017 um 15:17 schrieb Mark Thomas : >>> >>> On 13/06/17 11:57, Mark Thomas wrote: On 13/06/17 10:13, Kreuser, Peter wrote: > Mark, > >> On 09/06/17 1

Re: JVM Crash in tcnative due to concurrency/timing in HTTP/2

2017-06-23 Thread Mark Thomas
On 23/06/17 16:02, l...@kreuser.name wrote: > Mark, >> >> Am 23.06.2017 um 15:17 schrieb Mark Thomas : >> >> On 13/06/17 11:57, Mark Thomas wrote: >>> On 13/06/17 10:13, Kreuser, Peter wrote: Mark, > On 09/06/17 16:02, Kreuser, Peter wrote: >> Hi all, >> >> Sorry for the l

Re: JVM Crash in tcnative due to concurrency/timing in HTTP/2

2017-06-23 Thread logo
Mark, > > Am 23.06.2017 um 15:17 schrieb Mark Thomas : > > On 13/06/17 11:57, Mark Thomas wrote: >> On 13/06/17 10:13, Kreuser, Peter wrote: >>> Mark, >>> On 09/06/17 16:02, Kreuser, Peter wrote: > Hi all, > > Sorry for the long text. I hope somebody can help me track down the

Re: AW: JVM Crash in tcnative due to concurrency/timing in HTTP/2

2017-06-23 Thread Mark Thomas
On 13/06/17 11:57, Mark Thomas wrote: > On 13/06/17 10:13, Kreuser, Peter wrote: >> Mark, >> >>> On 09/06/17 16:02, Kreuser, Peter wrote: Hi all, Sorry for the long text. I hope somebody can help me track down the problem I'm facing with Tomcat (8.5.15), tcnative (1.2.12), open

Re: AW: JVM Crash in tcnative due to concurrency/timing in HTTP/2

2017-06-13 Thread Mark Thomas
On 13/06/17 10:13, Kreuser, Peter wrote: > Mark, > >> On 09/06/17 16:02, Kreuser, Peter wrote: >>> Hi all, >>> >>> Sorry for the long text. I hope somebody can help me track down the problem >>> I'm facing with Tomcat (8.5.15), tcnative (1.2.12), openssl (1.1.0e) and >>> HTTP/2. JVM is zulu-8.21

AW: JVM Crash in tcnative due to concurrency/timing in HTTP/2

2017-06-13 Thread Kreuser, Peter
Mark, > On 09/06/17 16:02, Kreuser, Peter wrote: > > Hi all, > > > > Sorry for the long text. I hope somebody can help me track down the problem > > I'm facing with Tomcat (8.5.15), tcnative (1.2.12), openssl (1.1.0e) and > > HTTP/2. JVM is zulu-8.21.0.1 (1.8.0_131-b11) > > No need to apologis

Re: JVM Crash in tcnative due to concurrency/timing in HTTP/2

2017-06-12 Thread Rémy Maucherat
2017-06-12 17:07 GMT-05:00 Mark Thomas : > On 09/06/17 16:02, Kreuser, Peter wrote: > > Hi all, > > > > Sorry for the long text. I hope somebody can help me track down the > problem I'm facing with Tomcat (8.5.15), tcnative (1.2.12), openssl > (1.1.0e) and HTTP/2. JVM is zulu-8.21.0.1 (1.8.0_131-b

Re: JVM Crash in tcnative due to concurrency/timing in HTTP/2

2017-06-12 Thread Mark Thomas
On 09/06/17 16:02, Kreuser, Peter wrote: > Hi all, > > Sorry for the long text. I hope somebody can help me track down the problem > I'm facing with Tomcat (8.5.15), tcnative (1.2.12), openssl (1.1.0e) and > HTTP/2. JVM is zulu-8.21.0.1 (1.8.0_131-b11) No need to apologise. There was enough inf

JVM Crash in tcnative due to concurrency/timing in HTTP/2

2017-06-09 Thread Kreuser, Peter
Hi all, Sorry for the long text. I hope somebody can help me track down the problem I'm facing with Tomcat (8.5.15), tcnative (1.2.12), openssl (1.1.0e) and HTTP/2. JVM is zulu-8.21.0.1 (1.8.0_131-b11) I've added (already for a long time) the logging of the ssl_cipher to the accesslog. For som