On Jul 23, 2007, at 3:45 AM, Paddy O'Neill wrote:
This sounds similar to a problem that we encountered where mina was serving multiple sessions and forwarding to a single connection, similar to your environment. We found that the thread management in mina on the single connection side would not work efficiently and end up only allocating jobs to a single thread. This effectively caused the jobs to be executed sequentially, which in turn caused the backlog and memory buildup. I suspect that the issue is related to there only being a single connection on the IoConnector as we found that the jobs were allocated correctly across threads on the IoAcceptor side.
sure.. not unsurprising. that's how the ExecutorFilter works. what you did was the right thing.. recognizing you have some parallelization in processing of messages for your app and managing it yourself.
-pete -- [EMAIL PROTECTED] - http://fotap.org/~osi
smime.p7s
Description: S/MIME cryptographic signature
