My guess would be that an IOException or maybe another related exception would occur because MINA could not write the data. Depending on your filter chain, you may get an OOM error.
On Wed, Dec 24, 2008 at 4:36 AM, Steve Johns <[email protected]> wrote: > Can everyone answer my first question?Thanks. > > On Mon, Dec 15, 2008 at 7:40 PM, Ashish <[email protected]> wrote: > >> Not sure for 1.1.7, but here is what I can tell you from 2.0 >> >> Please NOTE that these may not be the accurate answers. >> >> On Sun, Dec 14, 2008 at 1:43 PM, Steve Johns >> <[email protected]> wrote: >> > Hi I have several quesions about MINA.I am using mina1.1.7. >> > 1)If server doesn't detect the session close signal and server keeps >> sending >> > large amount of message to that session.What will happen?OOM? >> >> No Clue >> >> > 2)How does MINA manage the internal queue for incoming and outcoming >> > messages?Is there anyway to control these queue size? >> >> For Queue Size, don't think we can control the size, as this is the >> construct used >> >> private final BlockingQueue<IoSession> waitingSessions = new >> LinkedBlockingQueue<IoSession>(); >> >> Using a different constructor we could have specified the size >> >> > 3)Adding the ExecutorFilter after decoder and encoder filter will cause >> > message receive no in order? >> >> Checkout Event Ordering details at >> >> http://mina.apache.org/report/trunk/xref/org/apache/mina/filter/executor/ExecutorFilter.html >> AFAIK, for an IoSession using OrderedThreadPool, it shall maintain the >> sequence >> >> > Thanks. >> > >> >
