You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2007/08/02 12:14:53 UTC

[jira] Updated: (DIRMINA-302) Unbounded nature of writeRequestQueue can cause OutOfMemoryException

     [ https://issues.apache.org/jira/browse/DIRMINA-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trustin Lee updated DIRMINA-302:
--------------------------------

      Component/s:     (was: Core)
                   Filter
    Fix Version/s: 2.0.0-M1

Will fix this in 2.0.0-M1 because it's very important for a scalable server.

> Unbounded nature of writeRequestQueue can cause OutOfMemoryException
> --------------------------------------------------------------------
>
>                 Key: DIRMINA-302
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-302
>             Project: MINA
>          Issue Type: Bug
>          Components: Filter
>    Affects Versions: 1.0.0
>            Reporter: Martin Ritchie
>             Fix For: 2.0.0-M1
>
>         Attachments: WriteBufferLimitFilterBuilder.java
>
>
> As referenced in the following JIRAs:
>  DIRMINA-206 Prevent OutOfMemoryError when a server or a client is overloaded
>  DIRMINA-144 Traffic shaping filter
>  DIRMINA-262 Controlling rate of writes in Mina 0.8.2
> Raised to hightlight the problem. There are a number of approaches that have been mentioned and could be used as an approach.
> Limiting the queue to number of requests or total size. 
> Then either blocking on a write or throwing an exception.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Updated: (DIRMINA-302) Unbounded nature of writeRequestQueue can cause OutOfMemoryException

Posted by Trustin Lee <tr...@gmail.com>.
On 8/3/07, mat <fo...@gmail.com> wrote:
> Which means: instead of let users "GUESS" the traffic rate, the mina core
> will take care of that?

It will be provided as a form of an IoFilter rather than being tightly
integrated with core.  But I think we need more discussion about how
to control the traffic rate *automatically* if user doesn't set any
limit value.  I think approaching from manual options and then
providing another layer that controls the manual traffic throttling
filter might be reasonable.

Trustin
-- 
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6

Re: [jira] Updated: (DIRMINA-302) Unbounded nature of writeRequestQueue can cause OutOfMemoryException

Posted by mat <fo...@gmail.com>.
Which means: instead of let users "GUESS" the traffic rate, the mina core
will take care of that?

On 8/3/07, Trustin Lee <tr...@gmail.com> wrote:
>
> On 8/3/07, mat <fo...@gmail.com> wrote:
> > WriteThrottleFilter is different from this solution?
>
> No, we will merge ReadThrottleFilter and WriteThrottleFilter to
> provider better user experience.
>
> Trustin
> --
> what we call human nature is actually human habit
> --
> http://gleamynode.net/
> --
> PGP Key ID: 0x0255ECA6
>

Re: [jira] Updated: (DIRMINA-302) Unbounded nature of writeRequestQueue can cause OutOfMemoryException

Posted by Trustin Lee <tr...@gmail.com>.
On 8/3/07, mat <fo...@gmail.com> wrote:
> WriteThrottleFilter is different from this solution?

No, we will merge ReadThrottleFilter and WriteThrottleFilter to
provider better user experience.

Trustin
-- 
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6

Re: [jira] Updated: (DIRMINA-302) Unbounded nature of writeRequestQueue can cause OutOfMemoryException

Posted by mat <fo...@gmail.com>.
WriteThrottleFilter is different from this solution?

On 8/2/07, Trustin Lee (JIRA) <ji...@apache.org> wrote:
>
>
>     [
> https://issues.apache.org/jira/browse/DIRMINA-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Trustin Lee updated DIRMINA-302:
> --------------------------------
>
>      Component/s:     (was: Core)
>                   Filter
>    Fix Version/s: 2.0.0-M1
>
> Will fix this in 2.0.0-M1 because it's very important for a scalable
> server.
>
> > Unbounded nature of writeRequestQueue can cause OutOfMemoryException
> > --------------------------------------------------------------------
> >
> >                 Key: DIRMINA-302
> >                 URL: https://issues.apache.org/jira/browse/DIRMINA-302
> >             Project: MINA
> >          Issue Type: Bug
> >          Components: Filter
> >    Affects Versions: 1.0.0
> >            Reporter: Martin Ritchie
> >             Fix For: 2.0.0-M1
> >
> >         Attachments: WriteBufferLimitFilterBuilder.java
> >
> >
> > As referenced in the following JIRAs:
> >  DIRMINA-206 Prevent OutOfMemoryError when a server or a client is
> overloaded
> >  DIRMINA-144 Traffic shaping filter
> >  DIRMINA-262 Controlling rate of writes in Mina 0.8.2
> > Raised to hightlight the problem. There are a number of approaches that
> have been mentioned and could be used as an approach.
> > Limiting the queue to number of requests or total size.
> > Then either blocking on a write or throwing an exception.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>