Hi Trustin, It's not a bug, it was my fault.
I had a class handling the nio transfers using the java.nio package, which I ported to use mina. So whenever there was nothing in the queue, I suspended the write interest, which only makes sense for java.nio. In mina it does not :) Changed it and now it seems to work fine. Greetz, Stivo -------- Original-Nachricht -------- > Datum: Tue, 11 Mar 2008 11:21:52 +0900 > Von: "이희승 \\"(Trustin Lee)\\"" <[EMAIL PROTECTED]> > An: [email protected] > Betreff: Re: Scheduled Bytes are not sent > Hi Arno, > > If the small message is not flushed at all even after several dozen > milliseconds, that sounds like a problem in MINA. However small the > message is, it should be sent eventually even if there's no following > write. Do you have any simple reproducible test code so I can track it > down? > > Thanks, > > 2008-03-10 (월), 19:55 +0100, Arno Nym 쓰시길: > > Hi > > > > I use mina 1.1.6 for the opensource application tcpfile. I am mostly > > happy with it. > > (I use it for normal tcp connections) > > However, sometimes when I have just a very short message in the queue > > (<100 bytes) it will not be sent unless another message enters the > > queue. > > I dont want to use setTCPNoDelay... > > But is there some way I can set a timelimit or a bytelimit or flush it > > manually? I did not find any of these things anywhere. > > And I would not like to just add another message to make the limit with > > no content... > > > > Greetz, > > Stivo > > > -- > Trustin Lee - Principal Software Engineer, JBoss, Red Hat > -- > what we call human nature is actually human habit > -- > http://gleamynode.net/ -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
