ExceededMaximumConnections ERROR using maxConnections with NIO transport on Fuse Message Broker7.0

Solution Unverified - Updated -

Issue

We are using Fuse Messsage Broker in standalone mode. We've configured maxConnections on a trasnport connector using NIO transport:

What can we do to avoid this error:

2014-07-08 22:16:11,399 [onnections=1600] ERROR TransportConnector             - Could not accept connection : org.apache.activemq.transport.tcp.ExceededMaximumConnectionsException: Exceeded the max
imum number of allowed client connections. See the 'maximumConnections' property on the TCP transport configuration URI in the ActiveMQ configuration file (e.g., activemq.xml)
2014-07-08 22:16:12,943 [onnections=1600] ERROR TransportConnector             - Could not accept connection : org.apache.activemq.transport.tcp.ExceededMaximumConnectionsException: Exceeded the max
imum number of allowed client connections. See the 'maximumConnections' property on the TCP transport configuration URI in the ActiveMQ configuration file (e.g., activemq.xml)
2014-07-08 22:16:16,521 [onnections=1600] ERROR TransportConnector             - Could not accept connection : org.apache.activemq.transport.tcp.ExceededMaximumConnectionsException: Exceeded the max
imum number of allowed client connections. See the 'maximumConnections' property on the TCP transport configuration URI in the ActiveMQ configuration file (e.g., activemq.xml)

Environment

Fuse Message Broker 7.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.