That's great news, and though I was happy to help, you solved your own
problem.
francong2000, whose original thread we've hijacked, do the two settings
Adam identified also fix your issue, or do we need to keep digging into
your problem?
Tim
On Feb 1, 2017 7:04 PM, "Adam Whitney" wrote:
> We r
We ran a couple tests with conduitSubscriptions="true" and
decreaseNetworkConsumerPriority="true".
The first test we had 3 brokers, 2 producers, and 4 consumers hosts ... and
made sure that each broker had at least 1 consumer host connected ... and
everything kept up just fine.
We ran again with
We have simple application running on mule runtime. When we hit the http
request with hostname and port no the request pass to this application and
return hardcoded payload to webpage.
And whiten the application we configure log4j2.xml file to send the generate
log by this application to specific
I actually thought about a self contained test, that we can use to
debug at our dev environment.
Putting something complex to be executed over the AWS wouldn't help
much. We would still need to figure out your whole app framework.
Why don't you use some of the examples infra-structure to create s
Although I strongly recommend you (and everyone) use both of those settings
unless there's a clear reason not to (and I didn't even consider the
possibility of you not having them on), I expect that conduitSubscriptions
will make the lion's share of the difference. Without it, brokers must pass
man
Ok, perfect.
I'd be very happy if Martyn could take a look on this.
Meanwile, I'll try to put in place a test environment on AWS, accessible to
everyone of the community ...this way I hope you'll be able to help me to
debug and solve the problem.
Thanks
Francesco
--
View this message in contex
