You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Nuno Santos (JIRA)" <qp...@incubator.apache.org> on 2007/01/13 00:23:27 UTC
[jira] Created: (QPID-290) Java broker does not honor maximum
number of channels threshold
Java broker does not honor maximum number of channels threshold
---------------------------------------------------------------
Key: QPID-290
URL: https://issues.apache.org/jira/browse/QPID-290
Project: Qpid
Issue Type: Bug
Components: AMQP Compliance, Java Broker
Affects Versions: M2
Reporter: Nuno Santos
Priority: Minor
Attachments: AMQMinaProtocolSession.java-20070112.patch
The Java broker does not honor the maximum number of channels threshold, it just keeps creating new channels as requested (it does however send out peer notifications of the threshold being reached).
I've created a patch, which I'll upload, but by sending an exception at this point the whole connection is brought down, which seems a bit too drastic in this situation... the AQMP spec isn't too clear on what action would be appropriate (actually, it's not clear on what exception code should be used either -- I'm using 530/not-allowed for now).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (QPID-290) Java broker does not honor maximum
number of channels threshold
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie resolved QPID-290.
---------------------------------
Resolution: Fixed
Completed: At revision: 531526
> Java broker does not honor maximum number of channels threshold
> ---------------------------------------------------------------
>
> Key: QPID-290
> URL: https://issues.apache.org/jira/browse/QPID-290
> Project: Qpid
> Issue Type: Bug
> Components: AMQP Compliance, Java Broker
> Affects Versions: M2
> Reporter: Nuno Santos
> Priority: Minor
> Attachments: AMQMinaProtocolSession.java-20070112.patch
>
>
> The Java broker does not honor the maximum number of channels threshold, it just keeps creating new channels as requested (it does however send out peer notifications of the threshold being reached).
> I've created a patch, which I'll upload, but by sending an exception at this point the whole connection is brought down, which seems a bit too drastic in this situation... the AQMP spec isn't too clear on what action would be appropriate (actually, it's not clear on what exception code should be used either -- I'm using 530/not-allowed for now).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-290) Java broker does not honor maximum
number of channels threshold
Posted by "Nuno Santos (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nuno Santos updated QPID-290:
-----------------------------
Attachment: AMQMinaProtocolSession.java-20070112.patch
> Java broker does not honor maximum number of channels threshold
> ---------------------------------------------------------------
>
> Key: QPID-290
> URL: https://issues.apache.org/jira/browse/QPID-290
> Project: Qpid
> Issue Type: Bug
> Components: AMQP Compliance, Java Broker
> Affects Versions: M2
> Reporter: Nuno Santos
> Priority: Minor
> Attachments: AMQMinaProtocolSession.java-20070112.patch
>
>
> The Java broker does not honor the maximum number of channels threshold, it just keeps creating new channels as requested (it does however send out peer notifications of the threshold being reached).
> I've created a patch, which I'll upload, but by sending an exception at this point the whole connection is brought down, which seems a bit too drastic in this situation... the AQMP spec isn't too clear on what action would be appropriate (actually, it's not clear on what exception code should be used either -- I'm using 530/not-allowed for now).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira