Hi Gary,
Thanks for the quick response.
Yelei
Gary Tully wrote:
>
> Queues are FIFO by default
>
> On 13 August 2010 11:37, WuKo wrote:
>>
>> Hello,
>>
>> Does anybody knows if ActiveMQ by default has FIFO function in Queue
>> model
>> (not
Hello,
Does anybody knows if ActiveMQ by default has FIFO function in Queue model
(not subscribe model)?
If not, is there any way to configure it?
Thanks.
Yelei
--
View this message in context:
http://old.nabble.com/How-to-ensure-FIFO-function-in-ActiveMQ-tp29427470p29427470.html
Sent from the
>
> Clark
>
>
> www.ttmsolutions.com
> ActiveMQ reference guide at
> http://bit.ly/AMQRefGuide
>
>
>
>
>
>
> WuKo wrote:
>>
>> Hello Alexandre,
>>
>> Thanks for your reply.
>> You are right that that the consumer code wi
Thanks Alexandre,
I'll try your solution.
Yelei
Hi Yelei,
You could try the following change to your jndi.properties file:
java.naming.provider.url = tcp://ws293.soadev.local:61616/localhost:1234
Where 1234 is a port you know to be open on the *client side*.
The local port number a client us
://10.8.76.24:61617/localhost:60606
>
>
> This is the kind of configuration I use, because I can only open specific
> ports on both the client and the server. (In this example, the server is
> listening on ssl://0.0.0.0:61617 and the client will connect through his
> local port
Hello Alexandre,
Thanks for your reply.
You are right that that the consumer code will stop receiving messages after
it gets a timeout.
The scenario in my environment is:
1. we have a scheduler on one of our SOA platforms, which triggers the
consumer code every 5 minutes and gets a certain amoun