headers
Allen Reese | 9 Feb 21:07
Picon
Favicon

RE: Cores with FlushableGzipOutputStream

Try again now that I'm subscribed.

> -----Original Message-----
> From: Allen Reese
> Sent: Thursday, February 09, 2012 12:03 PM
> To: 'users <at> tomcat.apache.org'
> Cc: Lars Anderson
> Subject: Cores with FlushableGzipOutputStream
> 
> We've just upgraded from tomcat 6.0.33 to 6.0.35 and started having the
> JVM core on our production boxes.
> 
> I'm trying to determine what the next course of action should be here.
> I have an Oracle Support contract, but they don't seem to see this as a
> JVM issue, and blame it on a native lib.
> 
> 
> Thanks.
> 
> Allen Reese
> Core Platforms
> Yahoo!, Inc.
> 
> Running on linux x86-64, jdk 6u27, 6u29, 6u30, 7u2
> 
> We run several tests and the output is:
> 
> Jdk 	| Version	| flags
> 	|
> 6u30	| 6.0.33	| compression enabled
(Continue reading)

Permalink | Reply |
headers
ken dias | 9 Feb 21:17
Picon
Favicon

RE: Cores with FlushableGzipOutputStream


unsubscribe

> From: areese <at> yahoo-inc.com
> To: users <at> tomcat.apache.org
> CC: laraande <at> yahoo-inc.com
> Date: Thu, 9 Feb 2012 12:07:15 -0800
> Subject: RE: Cores with FlushableGzipOutputStream
> 
> Try again now that I'm subscribed.
> 
> 
> > -----Original Message-----
> > From: Allen Reese
> > Sent: Thursday, February 09, 2012 12:03 PM
> > To: 'users <at> tomcat.apache.org'
> > Cc: Lars Anderson
> > Subject: Cores with FlushableGzipOutputStream
> > 
> > We've just upgraded from tomcat 6.0.33 to 6.0.35 and started having the
> > JVM core on our production boxes.
> > 
> > I'm trying to determine what the next course of action should be here.
> > I have an Oracle Support contract, but they don't seem to see this as a
> > JVM issue, and blame it on a native lib.
> > 
> > 
> > Thanks.
> > 
> > Allen Reese
(Continue reading)

Permalink | Reply |
headers
Caldarale, Charles R | 9 Feb 21:27
Picon
Favicon

RE: Cores with FlushableGzipOutputStream

> From: Allen Reese [mailto:areese <at> yahoo-inc.com] 
> Subject: RE: Cores with FlushableGzipOutputStream

> I'm trying to determine what the next course of action should be here.
> I have an Oracle Support contract, but they don't seem to see this as a
> JVM issue, and blame it on a native lib.

> # Problematic frame:
> # C [libzip.so+0x77e3] char+0xa3

They conveniently forgot that's a library that comes with the JVM...

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use
only by the intended recipient. If you received this in error, please contact the sender and delete the
e-mail and its attachments from all computers.
Permalink | Reply |
headers
Mark Thomas | 9 Feb 21:53
Picon
Favicon
Gravatar

Re: Cores with FlushableGzipOutputStream

On 09/02/2012 20:07, Allen Reese wrote:
> Try again now that I'm subscribed.

If libzip.so is provided by the JVM installer (and I think it is) then
it is still a JVM problem. See [1] for an example where Oracle did
accept that an crash in libzip.so was a bug.

All changing the Tomcat code indicates is that some paths trigger the
bug and some don't. That does not absolve the JVM of responsibility.

Mark

[1] http://bugs.sun.com/view_bug.do?bug_id=6866479

> 
> 
>> -----Original Message-----
>> From: Allen Reese
>> Sent: Thursday, February 09, 2012 12:03 PM
>> To: 'users <at> tomcat.apache.org'
>> Cc: Lars Anderson
>> Subject: Cores with FlushableGzipOutputStream
>>
>> We've just upgraded from tomcat 6.0.33 to 6.0.35 and started having the
>> JVM core on our production boxes.
>>
>> I'm trying to determine what the next course of action should be here.
>> I have an Oracle Support contract, but they don't seem to see this as a
>> JVM issue, and blame it on a native lib.
>>
(Continue reading)

Permalink | Reply |
headers
Konstantin Kolinko | 9 Feb 22:00
Picon

Re: Cores with FlushableGzipOutputStream

2012/2/10 Allen Reese <areese <at> yahoo-inc.com>:
> Try again now that I'm subscribed.
>
>
>> -----Original Message-----
>> From: Allen Reese
>> Sent: Thursday, February 09, 2012 12:03 PM
>> To: 'users <at> tomcat.apache.org'
>> Cc: Lars Anderson
>> Subject: Cores with FlushableGzipOutputStream
>>
>> We've just upgraded from tomcat 6.0.33 to 6.0.35 and started having the
>> JVM core on our production boxes.
>>
>> I'm trying to determine what the next course of action should be here.
>> I have an Oracle Support contract, but they don't seem to see this as a
>> JVM issue, and blame it on a native lib.
>>
>>
>> Thanks.
>>
>> Allen Reese
>> Core Platforms
>> Yahoo!, Inc.
>>
>> Running on linux x86-64, jdk 6u27, 6u29, 6u30, 7u2
>>
>> We run several tests and the output is:
>>
>> Jdk   | Version       | flags
(Continue reading)

Permalink | Reply |
headers
Allen Reese | 9 Feb 22:27
Picon
Favicon

RE: Cores with FlushableGzipOutputStream


> -----Original Message-----
> From: Konstantin Kolinko [mailto:knst.kolinko <at> gmail.com]
> Sent: Thursday, February 09, 2012 1:00 PM
> To: Tomcat Users List
> Subject: Re: Cores with FlushableGzipOutputStream
> 
> 2012/2/10 Allen Reese <areese <at> yahoo-inc.com>:
> > Try again now that I'm subscribed.
> >
> >
> >> -----Original Message-----
> >> From: Allen Reese
> >> Sent: Thursday, February 09, 2012 12:03 PM
> >> To: 'users <at> tomcat.apache.org'
> >> Cc: Lars Anderson
> >> Subject: Cores with FlushableGzipOutputStream
> >>
> >> We've just upgraded from tomcat 6.0.33 to 6.0.35 and started having
> >> the JVM core on our production boxes.
> >>
> >> I'm trying to determine what the next course of action should be
> here.
> >> I have an Oracle Support contract, but they don't seem to see this
> as
> >> a JVM issue, and blame it on a native lib.
> >>
> >>
> >> Thanks.
> >>
(Continue reading)

Permalink | Reply |
headers
Allen Reese | 16 Feb 21:45
Picon
Favicon

RE: Cores with FlushableGzipOutputStream


> -----Original Message-----
> From: Allen Reese [mailto:areese <at> yahoo-inc.com]
> Sent: Thursday, February 09, 2012 1:28 PM
> To: Tomcat Users List
> Cc: Lars Anderson
> Subject: RE: Cores with FlushableGzipOutputStream
> 
> 
> 
> > -----Original Message-----
> > From: Konstantin Kolinko [mailto:knst.kolinko <at> gmail.com]
> > Sent: Thursday, February 09, 2012 1:00 PM
> > To: Tomcat Users List
> > Subject: Re: Cores with FlushableGzipOutputStream
> >
> > 2012/2/10 Allen Reese <areese <at> yahoo-inc.com>:
> > > Try again now that I'm subscribed.
> > >
> > >
> > >> -----Original Message-----
> > >> From: Allen Reese
> > >> Sent: Thursday, February 09, 2012 12:03 PM
> > >> To: 'users <at> tomcat.apache.org'
> > >> Cc: Lars Anderson
> > >> Subject: Cores with FlushableGzipOutputStream
> > >>
> > >> We've just upgraded from tomcat 6.0.33 to 6.0.35 and started
> having
> > >> the JVM core on our production boxes.
(Continue reading)

Permalink | Reply |
headers
Mark Thomas | 16 Feb 21:50
Picon
Favicon
Gravatar

Re: Cores with FlushableGzipOutputStream

On 16/02/2012 20:45, Allen Reese wrote:
> My question is, I have all of the data in pcap format, so I can extract the chunks, what is the best way to feed
this through.
> Do I decompress it all and write it all at once through the stream?
> Or is this going to matter based on what order the chunks got written in.

Based on the work we did on the previous JVM bug that we worked around,
you'll need to flush at the correct point. I would start by recreating
exactly what you see in the network trace and then start to merge chunks
to simplify as far as you can.

Mark
Permalink | Reply |
headers
Allen Reese | 16 Feb 21:54
Picon
Favicon

RE: Cores with FlushableGzipOutputStream


> -----Original Message-----
> From: Mark Thomas [mailto:markt <at> apache.org]
> Sent: Thursday, February 16, 2012 12:50 PM
> To: Tomcat Users List
> Subject: Re: Cores with FlushableGzipOutputStream
> 
> On 16/02/2012 20:45, Allen Reese wrote:
> > My question is, I have all of the data in pcap format, so I can
> extract the chunks, what is the best way to feed this through.
> > Do I decompress it all and write it all at once through the stream?
> > Or is this going to matter based on what order the chunks got written
> in.
> 
> Based on the work we did on the previous JVM bug that we worked around,
> you'll need to flush at the correct point. I would start by recreating
> exactly what you see in the network trace and then start to merge
> chunks to simplify as far as you can.

That's what I was afraid of.  It looks like it's gzipped and then chunked.  I guess I need to extract each chunk
and try flushing that.

--Allen

> Mark
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe <at> tomcat.apache.org
> For additional commands, e-mail: users-help <at> tomcat.apache.org
(Continue reading)

Permalink | Reply |

Gmane