I\'m sending MapMessages in Java to ActiveMQ and retrieving them using Stomp in PHP. My message creation code looks like this:
I tried what I think are 4 most popular XMPP (aka \"Jabber\") clients (Spark, Pidgin, Psi, Pandion) to connect to ActiveMQ instance (Apache ActiveMQ ver. 5.3.0)
I\'m starting a project which I think will be particularly suited to MongoDB due to the speed and scalability it affords.
Today, I saw many errors on my ActiveMQ 5.3.2 console: INFO | Usage Manager Memory Limit reached. Stopping producer (ID:...) to
Background: Our current system involves two services (one written in Java, the other in PHP) that communicate with each other using HTTP callbacks. We would like to migrate from HTTP callbacks to a me
I ran into a very disturbing issue that\'s been puzzling me for a while and I was wondering if anyone could give me some insight on this.
I am using ActiveMq 5.32 with Spring 2.5.5.I use pretty generic configuration, as long as I include the
What\'s the standard wisdom and considerations for dividing up a message queue? Assuming relatively small number of messages (< 1000/day), does it make sense to combine multiple message types int
I ran into the following problem in dynamically creating topics for our ActiveMQ system: I have a number of processes (M_1, ..., M_n), where n is not large, typically 5-10. Some of the processes will
I am using two brokers and create a consumer connection like this ccf = new ActiveMQConnectionFactory(new URI(\"failover://(tcp://0.0.0.0:61617,tcp://0.0.0.0:61618)\"));