You are viewing a plain text version of this content. The canonical link for it is here.

Posted to server-dev@james.apache.org by "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/06/10 10:10:18 UTC

[jira] Resolved: (JAMES-1014) Terminating Open Connections

     [ https://issues.apache.org/jira/browse/JAMES-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Norman Maurer resolved JAMES-1014.
----------------------------------

    Fix Version/s: 3.0-M1
       Resolution: Fixed

Fixed... It was not a bug in in netty, I just used it the wrong way :/

> Terminating Open Connections
> ----------------------------
>
>                 Key: JAMES-1014
>                 URL: https://issues.apache.org/jira/browse/JAMES-1014
>             Project: JAMES Server
>          Issue Type: Bug
>          Components: IMAPServer
>    Affects Versions: Trunk
>            Reporter: Ian Boston
>            Assignee: Norman Maurer
>             Fix For: 3.0-M1
>
>
> When I call destroy() on the AbstractAsyncServer ( from which the Imap Server extends) open connections remain open and the server does not unload the component. I see that destroy does try and tell the bootstrap to releaseExternalResource(), however if the imap client remains connected, the client is not kicked off by the server.
> I am unloading a component from OSGi which then hangs forever. 
> It would probably be fine if the JVM terminated, as it would kill the established sockets.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org