Hi Niklas, On 4/26/06, Niklas Therning <[EMAIL PROTECTED]> wrote: > > Luke Hubbard ([EMAIL PROTECTED]) wrote: > > Hi Guys, > > > > We have run into a issue in 0.9.3 that wasnt a problem with 0.9. > > reuseAddress property in spring has moved to socketAcceptorConfig. > > Thats fine, I just updated our config files, but the problem is it > doesnt > > seem to work. We set it to true, but inside mina we can see its set to > > false. With 0.9 it worked. Is this a know issue, should I add to jira > (not > > quite sure how but could find out). I quess I should have picked a > stable > > build but I needed some new methods you added to the Buffer. > > > > Thanks for all the hard work, let me know if you want more info, or me > to > > post this bug somewhere else? > > > > -- Luke > > > > It's probably a bug. Please report this to JIRA and I'll look into it. > If possible, please attach the relevant parts of your Spring config file > as well.
I am not familiar with Mina's codebase, but I found something that might be the root cause of the problem. (the codebase is according to 0.9.3) In class o.a.m.transport.socket.nio.SocketAcceptorConfig line 39, there's a declaration for sessionConfig and it's used in o.a.m.transport.socket.nio.support.SocketAcceptorDelegate line 408. The listening socket's reuseAddress property is set correctly o.a.m.transport.socket.nio.support.SocketAcceptorDelegate.registerNew(), but it's reset when a new socket session is created in line 408 with the 'sessionConfig' which has not been initialized correctly. IMHO the 'sessionConfig's properties need to be populated according to SocketAcceptorConfig's properties. I may be wrong but hope this will help. Thanks! > > /Niklas > -- Best Regards Steven Gong
