You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2014/11/05 21:26:34 UTC
[jira] [Commented] (QPID-6153) [JMS 1.0 Client] Connection store
channel max as a signed short while the value is an unsigned short
[ https://issues.apache.org/jira/browse/QPID-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199005#comment-14199005 ]
Robbie Gemmell commented on QPID-6153:
--------------------------------------
I duplicated this with QPID-6193, which has a commit against it to resolve the issue, so I will close this JIRA out.
> [JMS 1.0 Client] Connection store channel max as a signed short while the value is an unsigned short
> ----------------------------------------------------------------------------------------------------
>
> Key: QPID-6153
> URL: https://issues.apache.org/jira/browse/QPID-6153
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.26, 0.28, 0.30
> Reporter: Timothy Bish
>
> The JMS 1.0 client stores the channel max value as a signed short in ConnectionEndpoint.java and checks against that value when creating new sessions. If the remote sends anything larger than 32767 this value goes negative and you cannot create any new sessions from the client. The default for that feild per spec is 65535 which will appear if for instance you add some connection properties on the remote end as was recent done in ActiveMQ and don't set an explicit channel max value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org