There are some pc, A,B,C,D.
A' os is windows7 64 bit, B,C,D' os is windows xp.
Our program is based C/S.
The ActiveMQ version is 5.5.0
I did a few experiments:
1 the server program and ActiveMQ running on the A, others pc running client
program , the client program
send message to ActiveMQ, co
I have seen some messages which say that ActiveMQ works fine on EC2. I also
came across an article that said they had scalability problems with ActiveMQ
on EC2. What is the official word on ActiveMQ on EC2 and is which release
works on EC2.
thanks,
Ravi.
--
View this message in context:
h
Try removing the ?wireFormat.maxInactivityDuration=0 parameter from your
connection URI.
On Sun, Sep 4, 2011 at 8:53 PM, zcduthie wrote:
> I've been searching for a solution to this problem for a while, however I
> could not find something that actually worked anywhere on these forums.
>
> Basi
Can you try providing the --jmxurl argument to the stop script?
Is your broker really running a JMX listener on 10.50.39.76, port 1099?
The "Connection refused" error normally means there is no process listening on
the port you're trying to connect.
Alternatively you can stop the broker using a
With not persistent messages, the default producer sent mode is async.
This non guaranteed delivery mode is honored by the network connector,
it also does an async send when it forwards the message.
The thinking being that if it is ok to loose messages on a network
disconnect between client and bro
Hi Ravi,
the general recommendation is Stomp as it's more "messaging-oriented"
protocol than REST. With Stomp you can use all semantics important for
asynchronous messaging like transactions, various types of acknowledgment
modes and such. Also, the protocol is easy enough http-like so there are a
