thanks for your reply.
I have noticed similar issues while using admin operations using JMX.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Activemq-s-Pure-Master-Slave-shared-nothing-configuration-tp3677854p3680052.html
Sent from the ActiveMQ - User mailing list archive
Thanks Gary for your feedback.
Inside of the classloader universe on Glassfish, and AFAIK, the connector
classloader loads individually deployed RAR modules, which are shared
between the applications. So, I think that could be a problem according to
your post because all the classes are shared bet
Oops, somehow lost the ability to attach the script to the previous post, so
here it is.
http://activemq.2283324.n4.nabble.com/file/n3679606/stomptest3.pl
stomptest3.pl
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Non-ASCII-messages-via-Stomp-being-dropped-or-mangled-
Hi all, I'm running into a problem sending Stomp messages with anything
other than ASCII text in them. I'm connecting from a perl client and I'm
trying to send simple textual messages to a single queue, some of these
messages contain latin1 characters, others unicode characters, others plain
asci
I would say its a bug.
If you delete persistent msgs on a queue, this needs to get replicated to the
slave broker.
Deleting a queue that is already empty might not necessarily need to be
replicated to the slave broker as destinations get
recreated on the fly.
You could raise a JIRA ticket if
it looks like there is more than one classloader involved, and classes
cannot be shared between them.
Note the exception:
Caused by: java.lang.ClassCastException:
> org.apache.activemq.transport.failover.FailoverTransportFactory cannot be
> cast to org.apache.activemq.transport.TransportFactory
T
Its regarding Activemq's Pure Master Slave (shared nothing) configuration.
I have made this configuration and noticed that transactions are replicated
from master to salve.
BUT operations done from Admin Tool of master like deleting any message,
removing queue from master is not replicate in salv
I came across with a problem what it looks like a ActiveMQ problem, but if
anyone here knows more about it, please feel free to post any thought.
I have two ActiveMQ 5.4.2 RAs deployed on glassfish 3.1. Each RA connects
with two different brokers hosted on 192.168.1.10 and both brokers have a
type
Hi,
sync send is important for sending persistent message, in terms that when
producer sends a message broker first stores a message in the store before
acking back to the producer that message is received. In this way we can
guarantee that message will not be lost during the crash.
As for the ne
Its regarding Activemq's Pure Master Slave (shared nothing) configuration.
I have made this configuration and noticed that transactions are replicated
from master to salve.
BUT operations done from Admin Tool of master like deleting any message,
removing queue from master is not replicate in sa
10 matches
Mail list logo