Hi Trustin, It appears from the code that set addresses can only be used while the acceptor is not running (e.g as a start up config) - can you confirm if that is correct?. I am not sure that stopping, adding the new ports and restarting the acceptor is a reasonable approach. I am after a scalable way to dynamically add more ports to the acceptor (or create new acceptors that all share the processing threadpool) as I do not want hundreds of acceptors (1 for each new port) added as the app is running.
Is there any reason the previous bind method was removed in 2.0 - and what would be the best way to achieve the same thing? regards Steve Trustin Lee wrote: > > Hi Steve, > > On Nov 19, 2007 6:15 AM, steview <[EMAIL PROTECTED]> wrote: >> >> Hi, >> I have a requirement similar to the following >> >> A client connects on a well known port and then is issued a directive to >> another port to connect to (all this is tcp/ip based). >> >> This can be a growing list of ports (possibly thousands) - I want to deal >> with using the 2.0 mina trunk - however, I am struggling with the >> concepts >> in 2.0. >> In 1.x I believe I could have used the acceptor.bind(localAddress, >> handler, >> config) method to add these ports to the existing acceptor (which was >> laready running) . > > SimpleIoProcessorPool is not for acceptor/connector threads but for > I/O processor threads. > You could set multiple addresses to bind by calling setAddresses(). > Isn't it sufficient for you? > > Trustin > -- > what we call human nature is actually human habit > -- > http://gleamynode.net/ > -- > PGP Key ID: 0x0255ECA6 > > -- View this message in context: http://www.nabble.com/using-SimpleIoProcessorPool-in-multiple-acceptors-tf4831890s16868.html#a13825975 Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.
