I ran the same topology with everything in the same server, both brokers,
producer and multi-threaded consumer. I can reproduce this EVERY SINGLE
TIME.
I tried with 5.9.1 and see exactly the same behavior. I tried with 5.6
(which is the version I run in production) where I know this basic topology
You can set up two brokers, one persistent and one non-persistent and have
the consumers for the persistent messages connect to the persistent broker
and the non persistent consumers to the other one. Have the producers
connected to both enqueuing to the right broker for the corresponding
queues.
One question - where is the tcp:// address "seen"?
As long as there are no "tcp:" nor "nio:" transports configured on the
broker, there is no way for a client to connect without SSL. If they try,
the server logs an error about improper SSL handshake and suggests a
"plain-text" connection was atte
Perhaps the kahadb (assuming kahadb) is getting corrupt?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/What-causes-Duplicate-from-store-tp4684925p4684966.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Thanks for the reply, monday I'll give it a try.
Rob
On Aug 22, 2014 6:52 PM, "artnaseef [via ActiveMQ]" <
ml-node+s2283324n4684954...@n4.nabble.com> wrote:
> Try adding the parenthesis with the failover URL:
>
> failover://(tcp://127.0.0.1:61616)
>
> --
> If you reply
Those symptoms are easy to produce - although this may not be your problem:
- start broker
- continually send non-persistent messages to a queue
- don't consume the messages
Try using the webconsole to see how messages are (not) flowing.
--
View this message in context:
http://activemq.228332
That sounds like the typical Java memory leak. If so, it should be easy to
track down since it sounds easily reproduced.
I recommend grabbing a couple of heap dumps a few hours, or days, apart, and
comparing.
JVisualVM can help analyze the heap dump. YourKit is even better.
--
View this mess
Try adding the parenthesis with the failover URL:
failover://(tcp://127.0.0.1:61616)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/One-consumer-out-of-two-doesn-t-receive-messages-sent-to-a-topic-tp4684939p4684954.html
Sent from the ActiveMQ - User mailing list archive
Sorry - I'm not familiar with that error. Was there any information in the
webapp server log file?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-Subscribing-to-AMQ-Topic-using-amq-js-tp4684795p4684953.html
Sent from the ActiveMQ - User mailing list archive at
We have a fresh installation of ActiveMQ 5.9.1 running on Red Hat Linux. With
no outside connections, no queues, and only the default topic on the system,
the process runs out of memory (1GB allocated at startup with "-Xms1G
-Xmx1G") after about 30 minutes, even with absolutely no activity. I
initi
James, any chance you could post a link to some documentation on that bug
fix?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Broken-when-sending-lots-of-messages-tp2348519p4684873.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,I'm facing the problem in subject.The system is done by a broker (in
future a cluster of), a couple of consumers and some producers.Initially
I've setup one producer and messages sent arrive to one consumer only.I've
the broker configured with two TransportConnectors:First consumer connects
to "
It would be good if Apache ActiveMQ developer/user can share their
experience/resolution which I am facing in Production environment now.
We are using 4 network of brokers in the provider end. They are all using
ActiveMQ 5.5.1 (along with Fuse 7.0.2). All these brokers are running in
Ubuntu OS.
T
I wrote yesterday asking what could be causing messages to remain on a
queue despite a consumer being registered. Each morning I've had to restart
this AMQ instance to resume operations.
This morning was different. I had an alarm indicating hub and all spokes
were having issues. Hub was at 100% st
In my code of web.xml given in the screen shot, the last servlet was
commented, now when I removed the comments i received the following error:
*FAIL - Deployed application at context path /FinesseConsumer but context
failed to start
C:\FinesseConsumer\nbproject\build-impl.xml:1052: The module has
15 matches
Mail list logo