camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chad Beaulac <>
Subject Re: tcp socket client consumer endpoint?
Date Thu, 12 Apr 2012 11:42:04 GMT
Hi Vid,

You are correct. camel-mina and camel-mina2 do not support this behavior at
this time. camel-mina2 will do this shortly. I have that scenario working
in my sandbox but it is not pushed to the repository yet. I'm also running
that scenario with a a Google Protocol Buffers Mina2 codec that I wrote;
which supports multiple message types over a single connection and handles
the scenario you laid out below. Look forward to seeing more camel-mina2
asynchronous functionality soon.

Chad Beaulac
Objective Solutions, Inc

On Tue, Apr 10, 2012 at 7:43 PM, vcheruvu <> wrote:

> Hi Chad,
>  Currently, I have to implement a tcp client that connects to a remote
> host. The following things takes place between client and remote host
> 1. Once connected to remote host, client send login message with a custom
> message format converted into bytes over wire. Remote host  will send
> sucessfull login code to client.
> 2. Once login is successfull,  TCP client send another  message that
> defines
> our interest to get data from remote host as asynchronous mode. The remote
> host will understand our message and publishes  data to our socket session.
> 3. While client is connected,  Remote host will send ping to Client for
> heartbeat check. Client must respond to the heartbeat for remote host
> within
> a time period, this is to ensure that remote host doesn't think that client
> is down otherwise socket session is closed after 3 tries.
> I am trying to see if above is possible with camel-mina2 with custom
> processors/handlers for sending/receiving messages to/from remote host.
> Kind regards,
> -Vid-
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message