maxFrameSize is a global limit on message sizes across all destinations; it
won't let you set the limit on a per-destination granularity.
You should be able to do what you described using an embedded Camel route,
though.
On Jun 4, 2015 3:41 AM, "Sajith Kariyawasam" wrote:
> Hi,
>
> In ActiveMQ i
Oh.. nice. well I didn’t see that.
I ended up implementing something with advisories to trace message flow.
It’s actually interesting as that you can just connect to a broker and
trace message flow.
We might want to open source it at some point.
On Fri, Jun 5, 2015 at 6:40 AM, Gary Tully wrote
have you run with trace=true on the transport urls. this will log4j
trace each openwire command on a per connection logger so that you can
at least identify the actual command that is taking time.
connection creation. producer creation, message send etc.
On 30 May 2015 at 00:06, Kevin Burton wrot
