Hi,
We have found the reason why we saw this. We were using Spring's autowire
functionality, since that was on by default in WebWork:
<beans default-autowire="autodetect">
...
<!-- The filter chain. -->
<bean id="filterChainBuilder"
class="org.apache.mina.integration.spring.DefaultIoFilterChainBuilderFactory
Bean">
...
</bean>
<!-- The IoAcceptor which binds to port 12399 -->
<bean id="ioAcceptor"
class="org.apache.mina.integration.spring.IoAcceptorFactoryBean">
<property name="target">
<bean class="org.apache.mina.transport.socket.nio.SocketAcceptor" />
</property>
<property name="bindings">
<list>
<bean class="org.apache.mina.integration.spring.Binding">
<property name="address"><bean
class="java.net.InetSocketAddress"><constructor-arg value="12399"
type="int"/></bean></property>
<property name="handler" ref="lobbyHandler" />
<property name="serviceConfig">
<bean
class="org.apache.mina.transport.socket.nio.SocketAcceptorConfig">
<property name="filterChainBuilder" ref="filterChainBuilder"
/>
<property name="reuseAddress" value="true" />
</bean>
</property>
</bean>
</list>
</property>
</bean>
...
</beans>
Apparently, the filterChainBuilder bean got wired into the default filter
chain builder slot as well as the configuration-specific slot. So it seems
like a word of warning is in place: don't use autowire... :) When we set it
to 'no', we solved the problem.
Best,
Petter
Cell: +46 704 40 30 25
Direct: +46 8 442 75 95
Fax: +46 8 24 05 08
www.jadestone.se
Björns Trädgårdsgränd 1, 116 21 Stockholm, Sweden
