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 "Ian Boston (JIRA)" <se...@james.apache.org> on 2010/06/04 18:32:54 UTC
[jira] Created: (JAMES-1014) Terminating Open Connections
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
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
[jira] Commented: (JAMES-1014) Terminating Open Connections
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876131#action_12876131 ]
Norman Maurer commented on JAMES-1014:
--------------------------------------
It seems to be a bug in NETTY. I just filled a Bugreport:
https://jira.jboss.org/browse/NETTY-324
> 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
>
> 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
[jira] Commented: (JAMES-1014) Terminating Open Connections
Posted by "Ian Boston (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875872#action_12875872 ]
Ian Boston commented on JAMES-1014:
-----------------------------------
With commit 951509
I still have the problem, connect with iMail connection doctor on OSX creates an open socked
dhcp-65:imap ieb$ lsof | grep 8143
Mail 297 ieb 32u IPv6 0x0adac940 0t0 TCP localhost:55980->localhost:8143 (ESTABLISHED)
java 36786 ieb 400u IPv6 0x0a5301f0 0t0 TCP localhost:8143->localhost:55980 (ESTABLISHED)
dhcp-65:imap ieb$
I then cause the OSGi bundle to reload causing destroy() to be invoked
05.06.2010 07:00:50.017 *INFO* [Background Update org.sakaiproject.nakamura.imap (121)] org.sakaiproject.nakamura.imap.NakamuraNioImapServer Dispose IMAP Service
CPU goes to 100%
If I now tell iMail to take that imap connection off line, which should close the connection, I get the remainder of the reload operation
05.06.2010 07:05:57.516 *WARN* [Background Update org.sakaiproject.nakamura.imap (121)] org.apache.sling.jcr.base.internal.loader.Loader Custom node type definition org/apache/james/imap/jcr/imap.cnd not found in bundle org.sakaiproject.nakamura.imap
05.06.2010 07:05:57.557 *INFO* [FelixDispatchQueue] org.sakaiproject.nakamura.imap BundleEvent STOPPED
05.06.2010 07:05:57.558 *INFO* [FelixDispatchQueue] org.sakaiproject.nakamura.imap BundleEvent UNRESOLVED
05.06.2010 07:05:57.565 *INFO* [FelixDispatchQueue] org.sakaiproject.nakamura.imap BundleEvent UPDATED
05.06.2010 07:05:57.568 *INFO* [FelixDispatchQueue] org.apache.felix.framework FrameworkEvent PACKAGES REFRESHED
05.06.2010 07:05:57.574 *INFO* [FelixDispatchQueue] org.sakaiproject.nakamura.imap BundleEvent RESOLVED
05.06.2010 07:05:57.577 *INFO* [Background Update org.sakaiproject.nakamura.imap (121)] org.sakaiproject.nakamura.securityloader.Loader Trying to Load security from bundle org.sakaiproject.nakamura.imap.
05.06.2010 07:05:57.736 *INFO* [SCR Component Actor] org.apache.felix.scr Running task: Enable Component: org.sakaiproject.nakamura.imap.NakamuraNioImapServer (179)
05.06.2010 07:05:57.736 *INFO* [FelixDispatchQueue] org.sakaiproject.nakamura.imap BundleEvent STARTED
05.06.2010 07:05:57.801 *INFO* [SCR Component Actor] org.sakaiproject.nakamura.imap.NakamuraNioImapServer Autodiscovery is enabled - trying to discover your system's DNS Servers
05.06.2010 07:05:57.804 *INFO* [SCR Component Actor] org.sakaiproject.nakamura.imap.NakamuraNioImapServer Adding autodiscovered server 192.168.1.254
05.06.2010 07:05:57.805 *INFO* [SCR Component Actor] org.sakaiproject.nakamura.imap.NakamuraNioImapServer DNS Server is: 192.168.1.254
05.06.2010 07:05:57.813 *INFO* [SCR Component Actor] org.sakaiproject.nakamura.imap.NakamuraNioImapServer Registered cache, resolver and search paths as DNSJava defaults
05.06.2010 07:05:59.753 *INFO* [FelixDispatchQueue] org.sakaiproject.nakamura.imap BundleEvent STOPPED
05.06.2010 07:05:59.756 *INFO* [FelixDispatchQueue] org.sakaiproject.nakamura.imap BundleEvent RESOLVED
05.06.2010 07:05:59.757 *INFO* [FelixPackageAdmin] org.sakaiproject.nakamura.securityloader.Loader Trying to Load security from bundle org.sakaiproject.nakamura.imap.
05.06.2010 07:05:59.764 *INFO* [FelixDispatchQueue] org.sakaiproject.nakamura.imap BundleEvent STARTED
05.06.2010 07:05:59.764 *INFO* [FelixDispatchQueue] org.apache.felix.framework FrameworkEvent PACKAGES REFRESHED
05.06.2010 07:06:13.029 *INFO* [SCR Component Actor] org.sakaiproject.nakamura.imap.NakamuraNioImapServer IMAP Service is running on: 192.168.1.6
05.06.2010 07:06:13.029 *INFO* [SCR Component Actor] org.sakaiproject.nakamura.imap.NakamuraNioImapServer IMAP Service handler hello name is: 192.168.1.6
05.06.2010 07:06:13.029 *INFO* [SCR Component Actor] org.sakaiproject.nakamura.imap.NakamuraNioImapServer IMAP Service handler connection timeout is: 360
05.06.2010 07:06:13.030 *INFO* [SCR Component Actor] org.sakaiproject.nakamura.imap.NakamuraNioImapServer IMAP Service connection backlog is: 200
> 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
>
> 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
[jira] Resolved: (JAMES-1014) Terminating Open Connections
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ 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
[jira] Commented: (JAMES-1014) Terminating Open Connections
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875874#action_12875874 ]
Norman Maurer commented on JAMES-1014:
--------------------------------------
Hi Ian,
thank you for the feedback. I sent a message to the Netty mailinglist and waiting now for the response. As soon as I get a response I will fix it.
> 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
>
> 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
[jira] Assigned: (JAMES-1014) Terminating Open Connections
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer reassigned JAMES-1014:
------------------------------------
Assignee: Norman Maurer
> 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
>
> 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