I have a problem with this failover parameter:
I can't stop the process now. I guess since it stays alive with attempts to
reconnect to the AMQ.
Any ideas of how i can shut it down?
Thanks, Michal
Michal Singer wrote:
>
> Great, it helped.
> thanks.
>
>
> Dejan Bosanac wrote:
>>
>> Hi,
>>
sorry, a small correction:
hackingbear wrote:
>
> - Server 1 receives user message 2, and so try to get a token, get token
> B, but get stuck.
>
I meant:
- Server 1 receives user message 2, and so try to get a token, but get
stuck. token B never arrives
--
View this message in context:
ht
Hi,
I have two server components in my system. A gateway server and multiple
application server.
The gateway server communicates with external system and does the following:
1. receive tokens from the external system and place them in a queue (the
token queue.)
2. receive business requests from
Hi,
I upgraded to 5.2.0 last week and witness my application performance dropped
substantially. I wrote a simple test which does:
producer:
loop
create a temporary reply queue
send a short object message to a non-persistent, non-durable queue
read from reply queue
delete the re
dear friends of the messaging,
i did yet not find a solution for a stomp client to use the phantastic
redelivery policies described as features for a consumer. is there a way to
use/define transacted session via a stomp connect?
this would be great cause all delayed delivery with support from t
Dejan Bosanac wrote:
>
>
> is your SamplePojo properly annotated so it can be marshaled with XStream?
>
>
In my tests (using ActiveMQ 5.2, XStream 1.3) I found that the serialization
to XML works fine even without annotations, a simple (serializable) class
can be received by a Stomp client i
