Hi all,
I've been wondering about this for some time, but from my observations
it looks like connections (to the C++ broker) take much longer
(noticeably!!) from JMS than from C++ clients (qpid::messaging).
I was idly playing with qpid-printevents and firing up Java and C++
consumers and the subscription event was pretty much instantaneous with
the C++ consumer but ~seconds with the JMS consumer. I don't think it's
accounted for by JVM startup time as my JMS client prints a message on
startup before creating a Connection and the subscription event is
noticeably after that.
I've not systematically checked the elapsed time of the various bits of:
Context jndi = new InitialContext(props);
ConnectionFactory connectionFactory =
(ConnectionFactory)jndi.lookup("ConnectionFactory");
connection = connectionFactory.createConnection();
yet, but as the qpid::messaging C++ client is so fast I can't imagine
that there's something fundamental that should cause creating JMS
connections to be so much slower.
Judging by the standard Qpid tools I suspect that the python connection
startup suffers similar issues.
Any thoughts as to what this is due to? Should I raise a Jira?
I guess mostly connections are created infrequently, but I was musing
over the idea of creating a "Qpid crawler" to crawl over and map out
various brokers in a large federated topology - clearly connection
delays will slow that sort of application down.
Cheers,
Frase
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
