I find that if some IoSession has been paritially closed by inpatient client when they are queued, we can't actually use them anymore. So that explain the write.join failure. Also since those queued method are submitted without orginal timing properties, it seems that they are all submitted at once. So I used a SynchronuseQueue for ThreadPool, with min and max thread number bound and discard policy. The protocol implemented allows request dropping, since client can retry.
vondart wrote: > > 1. I used IoSession.write().join(timeout) to send back a message, but at > certain times, those message just timeout, and never appear in tcpdump > file. > 2. IoHandlerAdapter calls sessionCreated method for tcp connections not > appeared in tcpdump files, and each time with a looks like real remote > port number. > does those two problems indicate some threading problems? I changed mina > default executeModel to a thread pool with bounded queue. > > DaFENG > Coder > Telecommunication && Network Industry > Pudong > Shanghai > China > > > > -- View this message in context: http://www.nabble.com/a-question-tp23815035p23851635.html Sent from the Apache MINA User Forum mailing list archive at Nabble.com.
