that is perfectly sensible if you want individual control over clients ability to connect or need different qos. The only limits are OS/JVM related.
On 1 August 2014 10:19, khandelwalanuj <khandelwal.anu...@gmail.com> wrote: > Hi, > > I have a use case where I want to open more than one tcp and stomp connector > (using different ports) in ActiveMQ broker. I have already tried in my test > setup and it is able to connect and send/receive messages properly, it is > working fine. > But I want to understand that Is there any harm in specifying such > configuration Or is there any limit on number of such TCP/STOMP connection ? > > -------------- > <amq:transportConnector name="TcpTransport" > uri="tcp://0.0.0.0:61616" /> > > <amq:transportConnector name="TcpTransport2" > uri="tcp://0.0.0.0:61617" /> > > <amq:transportConnector name="StompTransport" > uri="stomp://0.0.0.0:61613" /> > > <amq:transportConnector name="StompTransport2" > uri="stomp://0.0.0.0:61618" /> > > -------------- > > Thanks, > Anuj > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Multiple-TCP-and-stomp-connections-to-the-ActiveMQ-broker-tp4684016.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
