You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Jeff Genender (JIRA)" <ji...@apache.org> on 2007/09/19 23:08:12 UTC
[jira] Created: (DIRMINA-441) SocketConnection cannot be manually
closed (for v1.1.2)
SocketConnection cannot be manually closed (for v1.1.2)
-------------------------------------------------------
Key: DIRMINA-441
URL: https://issues.apache.org/jira/browse/DIRMINA-441
Project: MINA
Issue Type: Bug
Components: Core
Affects Versions: 1.1.2
Reporter: Jeff Genender
Fix For: 1.1.3
The SocketConnection cannot be closed. Currently it will wait a certain amount of timeout as specified by the worker timeout to shut down the connection. This can result in OOM and hanging clients until thee timeouts occur. Mina should allow the SocketConnection to be closed manually if the connection is known to be completed.
Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-441) SocketConnection cannot be manually
closed (for v1.1.2)
Posted by "Jeff Genender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Genender updated DIRMINA-441:
----------------------------------
Attachment: DIRMINA-441-jgenender.patch
> SocketConnection cannot be manually closed (for v1.1.2)
> -------------------------------------------------------
>
> Key: DIRMINA-441
> URL: https://issues.apache.org/jira/browse/DIRMINA-441
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.2
> Reporter: Jeff Genender
> Fix For: 1.1.3
>
> Attachments: DIRMINA-441-jgenender.patch
>
>
> The SocketConnection cannot be closed. Currently it will wait a certain amount of timeout as specified by the worker timeout to shut down the connection. This can result in OOM and hanging clients until thee timeouts occur. Mina should allow the SocketConnection to be closed manually if the connection is known to be completed.
> Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRMINA-441) SocketConnection cannot be manually
closed (for v1.1.2)
Posted by "Jeff Genender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Genender closed DIRMINA-441.
---------------------------------
Resolution: Fixed
Agreed...will close it out.
> SocketConnection cannot be manually closed (for v1.1.2)
> -------------------------------------------------------
>
> Key: DIRMINA-441
> URL: https://issues.apache.org/jira/browse/DIRMINA-441
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.2
> Reporter: Jeff Genender
> Fix For: 1.1.3
>
> Attachments: DIRMINA-441-jgenender.patch, DIRMINA-441-jgenender.patch
>
>
> The SocketConnection cannot be closed. Currently it will wait a certain amount of timeout as specified by the worker timeout to shut down the connection. This can result in OOM and hanging clients until thee timeouts occur. Mina should allow the SocketConnection to be closed manually if the connection is known to be completed.
> Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-441) SocketConnection cannot be manually
closed (for v1.1.2)
Posted by "Jeff Genender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Genender updated DIRMINA-441:
----------------------------------
Attachment: (was: DIRMINA-441-jgenender.patch)
> SocketConnection cannot be manually closed (for v1.1.2)
> -------------------------------------------------------
>
> Key: DIRMINA-441
> URL: https://issues.apache.org/jira/browse/DIRMINA-441
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.2
> Reporter: Jeff Genender
> Fix For: 1.1.3
>
> Attachments: DIRMINA-441-jgenender.patch, DIRMINA-441-jgenender.patch
>
>
> The SocketConnection cannot be closed. Currently it will wait a certain amount of timeout as specified by the worker timeout to shut down the connection. This can result in OOM and hanging clients until thee timeouts occur. Mina should allow the SocketConnection to be closed manually if the connection is known to be completed.
> Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-441) SocketConnection cannot be manually
closed (for v1.1.2)
Posted by "Jeff Genender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Genender updated DIRMINA-441:
----------------------------------
Attachment: DIRMINA-441-jgenender.patch
This patch is better and thread safe.
> SocketConnection cannot be manually closed (for v1.1.2)
> -------------------------------------------------------
>
> Key: DIRMINA-441
> URL: https://issues.apache.org/jira/browse/DIRMINA-441
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.2
> Reporter: Jeff Genender
> Fix For: 1.1.3
>
> Attachments: DIRMINA-441-jgenender.patch, DIRMINA-441-jgenender.patch
>
>
> The SocketConnection cannot be closed. Currently it will wait a certain amount of timeout as specified by the worker timeout to shut down the connection. This can result in OOM and hanging clients until thee timeouts occur. Mina should allow the SocketConnection to be closed manually if the connection is known to be completed.
> Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-441) SocketConnection cannot be manually
closed (for v1.1.2)
Posted by "Jeff Genender (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Genender updated DIRMINA-441:
----------------------------------
Attachment: DIRMINA-441-jgenender.patch
This patch is better and its thread safe.
> SocketConnection cannot be manually closed (for v1.1.2)
> -------------------------------------------------------
>
> Key: DIRMINA-441
> URL: https://issues.apache.org/jira/browse/DIRMINA-441
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.2
> Reporter: Jeff Genender
> Fix For: 1.1.3
>
> Attachments: DIRMINA-441-jgenender.patch, DIRMINA-441-jgenender.patch
>
>
> The SocketConnection cannot be closed. Currently it will wait a certain amount of timeout as specified by the worker timeout to shut down the connection. This can result in OOM and hanging clients until thee timeouts occur. Mina should allow the SocketConnection to be closed manually if the connection is known to be completed.
> Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-441) SocketConnection cannot be manually
closed (for v1.1.2)
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530745 ]
Trustin Lee commented on DIRMINA-441:
-------------------------------------
Apart from DIRMINA-443, we have to just add more documentation instead of adding any methods; we already decided to freeze the API.
> SocketConnection cannot be manually closed (for v1.1.2)
> -------------------------------------------------------
>
> Key: DIRMINA-441
> URL: https://issues.apache.org/jira/browse/DIRMINA-441
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.2
> Reporter: Jeff Genender
> Fix For: 1.1.3
>
> Attachments: DIRMINA-441-jgenender.patch, DIRMINA-441-jgenender.patch
>
>
> The SocketConnection cannot be closed. Currently it will wait a certain amount of timeout as specified by the worker timeout to shut down the connection. This can result in OOM and hanging clients until thee timeouts occur. Mina should allow the SocketConnection to be closed manually if the connection is known to be completed.
> Patch is attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.