Hi all,
I set up two activemq servers A, B. Server A will use network connector to
push all messages it receives to server B. The configuration is like this:
networkConnectors
xmlns:spring=http://www.springframework.org/schema/beans;
spring:bean
sss
peek at producer flow control -
http://activemq.apache.org/producer-flow-control.html
configure brokerB with the default store cursor that will stop caching
messages rather than retain messages in memory.
On 24 June 2014 10:42, multani multani1...@gmail.com wrote:
Hi all,
I set up two
Hi
I'm using ActiveMQ through ServiceMix and was hindered by the following
issue with SM 5.0.0 and ActiveMQ 5.9.0:
https://issues.apache.org/jira/browse/AMQ-5121
https://issues.apache.org/jira/browse/AMQ-5121
This is logged as an issue for ActiveMQ 5.9.
However, with the latest version of
I have resolved my problems, at least for now. There were two of them.
First, I did not install the stomp.py module correctly. Second, the Python
stomp examples shipped with ActiveMQ were not correct.
Here is the listener that I got to work:
#!/usr/bin/env python
#
Oops. One little thing: I used persistent='false' in the publisher.
Persistence is the subject of my next question.
RobR
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problems-installing-and-running-examples-on-Windows-7-tp4682400p4682434.html
Sent from the
I am new to ActiveMQ. I have gotten a simple example (from the ActiveMQ
python stomp example) to work without persistence. A listener waits for
messages and displays the number of messages received, and a publisher sends
1 messages. I wanted to see persistence work. If I understand the
On 06/24/2014 12:53 PM, RobR wrote:
I am new to ActiveMQ. I have gotten a simple example (from the ActiveMQ
python stomp example) to work without persistence. A listener waits for
messages and displays the number of messages received, and a publisher sends
1 messages. I wanted to see
Check your clocks. They may be out of sync, and the messages may become
stale and be ignored by a consumer. To test this, you can run the broker
and client on the same machine. If that is not possible, add the
TimestampPlugin to your broker. In NMS (I know you are using the Java
client), there
I was wondering if this problem was resolved? I am having the same issue also
--
View this message in context:
http://activemq.2283324.n4.nabble.com/First-chance-exception-tp4677476p4682460.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
10 matches
Mail list logo