You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "michael goulish (JIRA)" <ji...@apache.org> on 2015/06/18 16:26:00 UTC

[jira] [Commented] (PROTON-842) proton-c should honor channel_max

    [ https://issues.apache.org/jira/browse/PROTON-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591877#comment-14591877 ] 

michael goulish commented on PROTON-842:
----------------------------------------

-- please note -- 

This fix changes API behavior in one way:   pn_session can now return NULL if an attempt is made to create more sessions than are allowed by the value of channel_max.

Previously, limitation on number of session was enforced by SEGV.



> proton-c should honor channel_max
> ---------------------------------
>
>                 Key: PROTON-842
>                 URL: https://issues.apache.org/jira/browse/PROTON-842
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.9
>            Reporter: michael goulish
>            Assignee: michael goulish
>
> proton-c code should use  transport->channel_max and transport->remote_channel_max  to enforce a limit on the
> maximum number of simultaneously active sessions on a 
> connection.   
> I guess the limit should be the minimum of those
> two numbers, or, if neither side sets a limit, then 2^16.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)