You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@etch.apache.org by "scott comer (JIRA)" <ji...@apache.org> on 2008/11/17 14:51:44 UTC

[jira] Created: (ETCH-6) if free pool exceeds maximum number of threads the exception thrown will kill the connection

if free pool exceeds maximum number of threads the exception thrown will kill the connection
--------------------------------------------------------------------------------------------

                 Key: ETCH-6
                 URL: https://issues.apache.org/jira/browse/ETCH-6
             Project: Etch
          Issue Type: Bug
          Components: csharp-binding, java-binding
    Affects Versions: 1.0.1, 1.0.0
         Environment: seen in java binding 1.0.1, presumed in csharp binding as well, and version 1.0.0 of both of those.
            Reporter: scott comer
             Fix For: 1.0.2


when the free pool detects that the number of threads in the thread group has been exceeded, the exception that is thrown isn't returned to the message sender, but instead hits the message receiver thread at the lowest level, causing it to take the connection down. this problem occurs in StubBase.java or .cs as it tries to dispatch the message.

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


[jira] Assigned: (ETCH-6) if free pool exceeds maximum number of threads the exception thrown will kill the connection

Posted by "scott comer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ETCH-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

scott comer reassigned ETCH-6:
------------------------------

    Assignee: scott comer

> if free pool exceeds maximum number of threads the exception thrown will kill the connection
> --------------------------------------------------------------------------------------------
>
>                 Key: ETCH-6
>                 URL: https://issues.apache.org/jira/browse/ETCH-6
>             Project: Etch
>          Issue Type: Bug
>          Components: csharp-binding, java-binding
>    Affects Versions: 1.0.0, 1.0.1
>         Environment: seen in java binding 1.0.1, presumed in csharp binding as well, and version 1.0.0 of both of those.
>            Reporter: scott comer
>            Assignee: scott comer
>             Fix For: 1.0.2
>
>
> when the free pool detects that the number of threads in the thread group has been exceeded, the exception that is thrown isn't returned to the message sender, but instead hits the message receiver thread at the lowest level, causing it to take the connection down. this problem occurs in StubBase.java or .cs as it tries to dispatch the message.

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


[jira] Resolved: (ETCH-6) if free pool exceeds maximum number of threads the exception thrown will kill the connection

Posted by "scott comer (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ETCH-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

scott comer resolved ETCH-6.
----------------------------

    Resolution: Fixed

> if free pool exceeds maximum number of threads the exception thrown will kill the connection
> --------------------------------------------------------------------------------------------
>
>                 Key: ETCH-6
>                 URL: https://issues.apache.org/jira/browse/ETCH-6
>             Project: Etch
>          Issue Type: Bug
>          Components: csharp-binding, java-binding
>    Affects Versions: 1.0.0, 1.0.1
>         Environment: seen in java binding 1.0.1, presumed in csharp binding as well, and version 1.0.0 of both of those.
>            Reporter: scott comer
>            Assignee: scott comer
>             Fix For: 1.0.2
>
>
> when the free pool detects that the number of threads in the thread group has been exceeded, the exception that is thrown isn't returned to the message sender, but instead hits the message receiver thread at the lowest level, causing it to take the connection down. this problem occurs in StubBase.java or .cs as it tries to dispatch the message.

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