like
people typically maintain a pool of servers on the client side and then
handle switching servers if the clients tcp closes. Maybe there's a better
solution - let me know what you find!
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Load-Balancer-EIP-with-TCP
host.
Thanks, SteveR
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Load-Balancer-EIP-with-TCP-Endpoints-tp5772104p5772314.html
Sent from the Camel - Users mailing list archive at Nabble.com.
some more details on the sync/async nature of this
communication? We can start there, and then we can talk about how distribute
(or not distribute) the message consumers based on your needs, and how camel
might fit into your solution.
--
View this message in context:
http://camel.465
I have a stand-alone Java application using Camel 2.15 and camel-netty4 which
is running on Linux RHEL6. I see that Camel supports a Load Balancer EIP and
I'm wondering if it would a good fit based on the following requirements for
my application:
*REQUIREMENTS:*
- Accept various incomin
No I never read that in the Camel documentation.
I incorrectly assumed that was the behaviour.
--
View this message in context:
http://camel.465427.n5.nabble.com/Load-Balancer-EIP-tp5656311p5662755.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ver.
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Load-Balancer-EIP-tp5656311p5661342.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
CamelOne 2012 Conference, May 15-16, 2012: http:
://camel.465427.n5.nabble.com/Load-Balancer-EIP-tp5656311p5661342.html
Sent from the Camel - Users mailing list archive at Nabble.com.
On Mon, Apr 23, 2012 at 12:35 PM, Edwin wrote:
> Thanks for the response Claus
>
> I am assuming the load balancer EIP sticky implementation maintains state in
> memory to map between the correlation key and the processor. Is it possible
> to programatically purge/delete this mapp
Thanks for the response Claus
I am assuming the load balancer EIP sticky implementation maintains state in
memory to map between the correlation key and the processor. Is it possible
to programatically purge/delete this mapping?
Edwin
--
View this message in context:
http://camel.465427.n5
On Sat, Apr 21, 2012 at 4:28 PM, Edwin wrote:
> Hi Folks,
>
> I'm using the Load Balancer EIP in a current project with a sticky policy.
> The load balancer receives messages and based on header values places the
> message onto one of 5 jms queues.
>
> The "happy
Hi Folks,
I'm using the Load Balancer EIP in a current project with a sticky policy.
The load balancer receives messages and based on header values places the
message onto one of 5 jms queues.
The "happy path" is: the same messages are continuously received throughout
the day a
11 matches
Mail list logo