Found the problem. I resolved it by increasing the send buffer and using the ExecutorFilter for the write event.
On Mon, Jul 6, 2009 at 10:14 PM, David Rosenstrauch<[email protected]> wrote: > Oscar wrote: >> >> Hi all, >> >> >> We took a stress test on our App. >> 50 clients, 10 requests per second. >> our App broadcasts the message to all the clients after receiving the >> request, that is, server will send 50*10*50 requests to clients. >> >> The App outputs the result of getScheduledWriteByes and >> getScheduledWriteMessages. >> We found that the value increased endlessly. >> >> At last, there were lots of WriteTimeoutException and >> WriteToClosedSessionException and sessions were closed. >> >> Mina: M6 >> Linux platform >> Java 1.6 >> >> How can I resolve the problem? >> >> Thank you, >> Oscar > > Not sure if this is your issue or not, but I found that MINA was throwing > lots of WriteToClosedSessionExceptions when I would have my client just drop > a connection instead of closing it cleanly. (i.e., have the client send > some sort of "close session" command, and have the server call > session.close().) > > Perhaps try having your stress test app issue "close session" commands and > see if that fixes the problem. > > HTH, > > DR >
