[
https://issues.apache.org/activemq/browse/AMQ-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58593#action_58593
]
Konstantin Skaburskas commented on AMQ-1928:
--------------------------------------------
Hi,
Could you please let us know what is the time line of providing the exception
for clients?
If I interpret "Fix Version/s: 5.4.0" correctly then, this means to be fixed in
5.4.0. What would be an approximate date for the release?
We see there still no proper exception for client in apache-activemq-5.3.1,
when setting this
<transportConnector name="openwire"
uri="tcp://0.0.0.0:61616?maximumConnections=2"/>
after sometime client just bails out with
javax.jms.JMSException: Wire format negotiation timeout: peer did not send his
wire format.
Will it work for STOMP as well?
Thank you,
Konstantin
> Limit the maximum number of connections to a Broker
> ---------------------------------------------------
>
> Key: AMQ-1928
> URL: https://issues.apache.org/activemq/browse/AMQ-1928
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 4.1.1, 4.1.2, 5.0.0, 5.1.0
> Reporter: Rob Davies
> Assignee: Bruce Snyder
> Fix For: 5.4.0
>
>
> Add a property (maximumConnections) to TcpTransportSever to limit a maximum
> number of active connections
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
