Unfortunately we didn't receive any replies. We ended up moving to Kafka
(http://incubator.apache.org/kafka/) which suited our throughput and
availability use cases better.
-Jonathan
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Async-error-occurred-Can-not-remove-a-
I would vote for that enhancement. Just out of curiosity what is the format
the messages are currently forwarded over tcp to the network of brokers? Do
the brokers maintain an open tcp connection to each other?
I am just trying to understand what kind of performance to expect if the
brokers are
Are there any drawbacks to turning on thread pools in terms of performance?
It would seem like it would use less memory but might have switching costs.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failover-with-networkConnectors-tp4415677p4425654.html
Sent from the Acti
Thanks for pointing this out Laures as we are using 5.5.1. We will definitely
add this case to our failure mode testing and use your thread pool
workaround if we experience the issue.
I am curious if using the NIO transport as we do makes any difference. I
doubt it since it still uses TCP to make
Thanks for your reply! I noticed I had the trailing ')' in the incorrect
spot based on your example. It is working now.
The start issue was getting my Windows and Linux environments confused and
typing 'activemq start' in Windows.
-Jonathan
--
View this message in context:
http://activemq.
Hi,
Is it possible to use the failover construct in the networkConnectors uri?
I have tried the following two uri values and both prevented ActiveMQ from
starting with an exception.
Both returned the following stack trace:
ERROR: java.lang.RuntimeException: Faile
I just experienced this in 5.5.1 so the issue still remains. Does anyone
know how to resolve this?
-Jonathan
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMq-console-fails-with-java-lang-ClassNotFoundException-org-apache-jsp-index-jsp-tp3437076p4337268.html
Sent f
Hi Gary,
Changing the client broker URL to use tcp protocol fixed the issue. This
looks like the following.
tcp://1.2.3.4:61618
Thanks again for your help!
-Jonathan
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-with-NIO-protocol-tp3540710p3545810.html
Sent f
Ah I see. I will give the new client broker URL later today.
In terms of the transportConnector we are using a specific IP address. I
just replaced it with Xs in this post for security reasons.
Thanks again!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-with-N
Hi Gary,
Thanks for your response.
Don't you mean the client should use
nio://ec2-x-x-x-x.us-west-1.compute.amazonaws.com:61618 which is what I have
tested that causes the error? Your client example uses tcp as the protocol.
-Jonathan
--
View this message in context:
http://activemq.2283324.n
Hi,
We are currently using ActiveMQ 5.4.2 with Spring/Tomcat clients. We have
this configured as standalone two node JDBC master/slave. Right now we are
only testing with one Spring/Tomcat client and the master ActiveMQ node.
When changing my broker URL on the clients to use the NIO protocol i
Hi,
We are currently using ActiveMQ 5.4.2 with Spring/Tomcat clients. We have
this configured as standalone two node JDBC master/slave. Right now we are
only testing with one Spring/Tomcat client and the master ActiveMQ node.
When changing my broker URL on the clients to use the NIO protocol in
I am also getting this issue on 5.4.1. Is it resolved in a later release?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Kaha-corruption-in-5-4-SNAPSHOT-tp2366036p3450835.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi Nag,
I have a very similar problem as the guy above and was wondering if you
think those links can also apply to my problem. I have read Bruce's blogs
but wasn't completely clear what to do. Do I have to setup a network of
brokers and shared database in order to take advantage of those settin
14 matches
Mail list logo