I believe that I fixed the issue. Committers, please verify and pull if it
looks OK. Patch attached to the JIRA ticket.
https://issues.apache.org/jira/browse/AMQ-5385
Thank you so much Andreas!
It seems to work fine, now I'm getting a ResourceAllocationException in the
client side, that allow me to continue with the process.
Now i need to find out if the client can switch automatically and send the
msg to the slave broker.
Thank you for your quick and helpfu
Start with the basics for any network connectivity issue: Is ActiveMQ
running on that host and port? Are clients able to connect to that broker
directly using that URI? Are there any firewalls between the machines your
two brokers are running on that might be stopping traffic? Are
authentication
We are getting following WARN message in log file. It looks like clustering
is not working. We started getting this error after upgrading Active MQ to
5.4.3.
Configuration: Active MQ 5.4.3
Spring Framework
Jboss 4.2.3 CP6
2014-10-07 15:39:38,625 WARN
[org.apache.activemq.network.DiscoveryNetwork
Can I use object store here with ActiveMQ ?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-on-Amazon-AWS-cluster-tp4686208p4686225.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi Anuj ,
you may want to use one of the databases available in AWS RDS to provide HA
persistence for your messages as PersistenceAdapter. Easier than a shared
filesystem.
With guaranteed IOPS (depending on the message size) we observe ~ 1
message/sec per 2 IOPS.
Maybe a hosted solution like htt
> Multicast won't work on EC2
Here multicast means UDP multicast and discovery transports, right ?
I will be running master-slave broker with shared storage. And clients will
be connecting using the failover URI as :
failover:(tcp://primarybrokerURI:61616, tcp://failoverbrokerURI:61616)
I guess
Hi,
I'd say you are running into flow control.
http://activemq.apache.org/producer-flow-control.html
With configuration you can achieve that you get an exception if your
storage is full, for example:
||
|
You can also decide to throw the exception only after a given
You can always configure the Brokerservice programmatically if the Spring
config doesn't work for you.
Best regards
Andreas
On 08/10/14 06:48, Avinash wrote:
But In this case, there is no activeMq.xml where I can add the
ManagementContext.
I am using activemq-broker and activemq-client jars.