I typically see the "Cannot publish to a deleted Destination" exception
hurled when the producing broker does not have a forwarding bridge back to
the consuming broker (i.e., broker w/the temp queue). Do you have
transportConnectors set up for both brokers?
Use caution when setting wireFormat.ma
Solved using the latest snapshot
Shimik wrote:
>
> The broker in the 5.2 tar.gz snapshot fails to start out of the box.
>
> Here is the log output:
>
> ...
> ...
> INFO log- ActiveMQ Console at
> http://0.0.0.0:8161/admin
> INFO log- A
Does anyone tried this kind of use case with BlobMessage?
Shimi
Shimik wrote:
>
> What is the best practice for using topic in medium to large cluster?
>
> In the topologies document (http://activemq.apache.org/topologies.html) it
> says:
> "Multicast is great in development though often you
The documentation is misleading. It shouldn't list multicast as one of the
transport protocols and definitely not on the main page.
http://activemq.apache.org/ - Supports pluggable transport protocols such as
in-VM, TCP, SSL, NIO, UDP, multicast, JGroups and JXTA transports.
http://activemq.apach
The broker in the 5.2 tar.gz snapshot fails to start out of the box.
Here is the log output:
...
...
INFO log- ActiveMQ Console at
http://0.0.0.0:8161/admin
INFO log- ActiveMQ Web Demos at
http://0.0.0.0:8161/demo
INFO log
From memory there are additional subdirectories with similar files for
32 bit and 64 bit architectures.
David Crisp wrote:
Hi,
I just downloaded ActiveMQ 5.1.0 and the distribution doesn't contain
any of the stuff I'm expecting. IE: no bin/activemq or conf/activemq.xml
or
the like... jus