Cancellation requests lock

[Margus Väli <ma...@webmedia.ee>]

1.0.1, Using multiple bindings causes jvm not to stop on HUP signal:

  <bean 
    class="org.apache.mina.integration.spring.IoAcceptorFactoryBean">
    <property name="target">
      <bean
class="org.apache.mina.transport.socket.nio.SocketAcceptor" />
    </property>
    <property name="bindings">
      <list>
        <ref local="socketBinding1"/>
        <ref local="socketBinding2"/>   
      </list>
    </property>
  </bean>

in Spring DisposableBean's #destroy implementation method,
target.unbind() runs until line 215 in SocketAcceptor to block in
request.wait() for the 2nd binding, the 1st one passes and the
socket is closed.

A quick solution was to define another io acceptor factory bean for
the 2nd binding.

regards,
mv

Re: Cancellation requests lock

[Trustin Lee <tr...@gmail.com>]

On 1/16/07, Margus Väli <ma...@webmedia.ee> wrote:
>
> 1.0.1, Using multiple bindings causes jvm not to stop on HUP signal:
>
>   <bean
>     class="org.apache.mina.integration.spring.IoAcceptorFactoryBean">
>     <property name="target">
>       <bean
> class="org.apache.mina.transport.socket.nio.SocketAcceptor" />
>     </property>
>     <property name="bindings">
>       <list>
>         <ref local="socketBinding1"/>
>         <ref local="socketBinding2"/>
>       </list>
>     </property>
>   </bean>
>
> in Spring DisposableBean's #destroy implementation method,
> target.unbind() runs until line 215 in SocketAcceptor to block in
> request.wait() for the 2nd binding, the 1st one passes and the
> socket is closed.
>
> A quick solution was to define another io acceptor factory bean for
> the 2nd binding.


Is it easy to reproduce the problem?  If so, could you please send me the
code that I can run by myself?

Trustin
-- 
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41  4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4  455E 1C62 A7DC 0255 ECA6