activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Shannon <christopher.l.shan...@gmail.com>
Subject Re: two possible issues when integrating with spring-jms
Date Wed, 21 Sep 2016 14:01:17 GMT
To answer your first question, growing larger than Long.MAX_VALUE is
practically impossible. The value is 9,223,372,036,854,775,807.  Even if
you were to create 1 temporary queue every millisecond it would take over
292 million years to reach Long.MAX_VALUE

For your second question, there is no issue because each request would have
its own unique temporary queue for a response so they don't interfere.
When you use a temporary queue the message contains name of the unique
reply to destination.  So when you send a message to queue Q and it is
processed, the receive of the message can check to the JMSReplyTo property
to know where to send the response to.  This means that the order it is
processed doesn't really matter and shouldn't interfere.

On Wed, Sep 21, 2016 at 8:07 AM, ted_dong <492399154@qq.com> wrote:

> First Question:
> Method JmsInvokerClientInterceptor.doExecuteRequest(Session, Queue,
> Message)
> is trying to create a TemporaryQueue then delete it. However, for each
> TemporaryQueue, connection will use LongSequenceGenerator to generate a
> incrementing queue name, what if sequence id grow bigger than
> Long.MAX_VALUE.
>
> Second Question:
> Again, for doExecuteRequest, if two thread is calling this method. For
> instance, thread A send a request to queue Q first, thread B send to queue
> Q
> later, but response for request B arrives first and response A later. Then
> thread A takes response of thread B.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/two-possible-issues-when-integrating-with-
> spring-jms-tp4716687.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message