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

Emmanuel Lecharny resolved DIRMINA-789.
---------------------------------------
    Resolution: Not a Problem

Again, it's all about waiting for the previous message to have been sent to the 
peer (ie, waiting for the messageSent event to be received).

> Possible Deadlock/Out of memory when sending large amounts of data using Nio
> ----------------------------------------------------------------------------
>
>                 Key: DIRMINA-789
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-789
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-RC1
>         Environment: Windows Vista 64-bit Java 5 and Java 6
>            Reporter: Sai Pullabhotla
>             Fix For: 2.0.8
>
>         Attachments: MinaClient.java, RandomDataServer.java
>
>
> This is a followup to the post on the DEV mailing list, 
> http://old.nabble.com/Help-needed-with-OutOfMemory-error-and-or-GC-Issues-Dead-Locks-td28849756.html.
>  
> I've even simplified the test cases so now it just has one simple NioServer, 
> and an NioClient. The MinaClient class creates 5 concurrent connections to 
> the RandomDataServer. Upon a successful connection, the server is setup to 
> send 500MB worth of random text data. The MinaClient just saves the received 
> data to a temp file in the working directory. When I run this code with small 
> amounts of data, it works fine, but with 500MB, I did not have success yet. 
> Some times, I get OOM on the server. Some times, nothing happens. 
> I've declared several constants in each class that you could change to try 
> various settings such as changing the amount of data served by the server, 
> whether or not to use an executor filter/IoEventThrottle etc. 
> Both classes have main methods, and I was running them as stand alone 
> applications on the same PC. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to