Each one will keep a socket open.. it's really an OS question...
I would create some sort of pool though. On Wed, Dec 16, 2020 at 5:49 AM Mohan Kumar <mku...@netsurion.com.invalid> wrote: > > Hi Clebert, > > Thanks for your reply. > > Is there any limit on number of concurrent connection at Artemis Broker level? > Ex : If we connect 10000 persistent connection, does Artemis broker handle > without any problem? > > Thanks, > Mohan > > -----Original Message----- > From: Clebert Suconic <clebert.suco...@gmail.com> > Sent: Wednesday, December 16, 2020 7:41 AM > To: users@activemq.apache.org > Subject: Re: ActiveMQ Artemis Client interface (AMQP vs REST) > > CAUTION: This email originated from outside of the organization. Do not click > links or open attachments unless you recognize the sender and know the > content is safe. > > > I think you would be best on deploying your own Rest Interface. > > Like if you have a REST method that would then produce, have the producer on > the Rest server.. and do your own facade. > > I haven't seen any commits on the REst Interface for Artemis in a while. > > That is, you use AMQP or whatever protocol at your REST endpoint... > and you talk to the server through your implementation. > > On Mon, Dec 14, 2020 at 2:58 AM Mohan Kumar <mku...@netsurion.com.invalid> > wrote: > > > > Hi, > > > > Based on the suggestion from Justin Bertram I am posting my query here. > > > > We are new to ActiveMQ Artemis world. > > When we started in ActiveMQ Artemis Broker we choose AMQP protocol to > > produce and consume data from broker. > > But as per the suggestion we received from ActiveMQ Artemis consultant we > > switched from AMQP to REST interface. > > > > Reason to switch from AMQP to REST > > > > * As per the suggestion > > > > Using AMQP, one of the problem we run into managing the connections come > > and go it is hard to get lot of insight into what's going on the broker. > > > > So it is challenging to manage and troubleshoot. > > > > broker aren't built with the intension of serving very large numbers of > > endpoints they built with the intension of moving messages quickly between > > endpoints. > > > > Rest: The tooling which are available in HTTP, and for scaling and for > > frontend and it is really for superior to broker itself > > > > > > > > > > > > * When we create 10000 connection using AMQP, It creates 10000 > > connections in Artemis broker(i.e. 10000 clients : 10000 connection in > > Artemis broker) > > > > But using rest, 10000 clients connecting to HTTP server, creates 10000 > > connection at HTTP server and there is only one connection from HTTP server > > to REST interface. > > > > So there is less load in broker(less number of connection in broker) and > > connection management comes to REST layer. > > > > > > > > > > Our requirement is, > > sensors (client which connect to Artemis server) in concurrent way we are > > using AMQP acceptor in broker We would like to know: > > 1. What would be maximum concurrent connection could be handled by > > Artemis broker (includes both publisher and subscriber) 2. Does broker > > connection has any dependency with acceptor (STOMP, AMQP, HTTP etc...) > > > > Thanks, > > Mohan > > > > > -- > Clebert Suconic -- Clebert Suconic
