[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mina-dev
Subject:    Re: usage of compression filter
From:       Ted Yu <yuzhihong () gmail ! com>
Date:       2010-01-26 21:03:50
Message-ID: 17e273101001261303x4616ca92ofde3999d6f91f7ea () mail ! gmail ! com
[Download RAW message or body]


We use 2.0.0-RC1

I don't have thread dump because I was experiencing timeout.

On Tue, Jan 26, 2010 at 12:46 PM, Emmanuel L=C5=BDcharny <elecharny@gmail.c=
om>wrote:

> Forwarded this mail to the correct mailing-list : dev@mina.apache.org.
>
> Which MINA version, btw ?
>
> Any thread dump available ?
>
> Ted Yu a =C3=A9crit :
>
>  Hi,
>> I see the following code from CompressionFilterTest:
>>        session.setAttribute(CompressionFilter.class.getName() +
>> ".Deflater",
>>                deflater);
>>        mockSession.setDefaultMatcher(new DataMatcher());
>>        mockSession.setReturnValue(null, MockControl.ONE);
>>
>>        session.setAttribute(CompressionFilter.class.getName() +
>> ".Inflater",
>>                inflater);
>> I am wondering if session.setAttribute() calls are required when we use
>> compression filter.
>>
>> Currently we use this code:
>> connector.getFilterChain().addLast("compression", new
>> CompressionFilter());
>>
>> connector is a NioSocketConnector.
>>
>> I observed a strange behavior with compression filter enabled: after
>> roughly
>> 570000 RPC calls, RPC call would timeout.
>> Without compression filte, there is no issue.
>>
>> Please help us with the usage of compression filter.
>>
>> Thanks
>>
>>
>>
>
>


[prev in list] [next in list] [prev in thread] [next in thread]