It is doing that. Normally a queue/topic-consumer is a long-running
client that will basically just do work whenever a message arrives. It
will normally not connect to see if there is a message and than
disconnect to repeat things later on.
If you have different requirements, that obviously changes things. You
can probably work around it by reducing the timeout a lot, or perhaps by
first checking whether there actually are messages (although, with
PHP/Stomp that's not trivial) in the queue before listening to it.
Best regards,
Arjen
On 21-2-2012 11:38, alexandry wrote:
Please disregard the question, i look into source code of php stomp
implementation and it seems, like has frame is simply wait max wait period
of 2 sec to see if message will appear.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AMQ-stomp-php-performance-issues-tp4406306p4406615.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
