Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <8EECE6C8A0ED7944B6166E1CCAF815E25996B24B93@2K8EXC01.m4u.com.br>
References: <8EECE6C8A0ED7944B6166E1CCAF815E25996B248B8@2K8EXC01.m4u.com.br>
 <CB8CEE40-61F5-4DAA-A745-563D21780538@gmail.com>
 <CAGB5yNkL4th-B+_3+acYMN_zxPr_DL4pOMhu-faqJMpjOFsxjQ@mail.gmail.com>
 <8EECE6C8A0ED7944B6166E1CCAF815E25996B249B2@2K8EXC01.m4u.com.br>
 <CAGB5yN=agDu=CSGO68WShMWK-daLfaz1Cqcy1geFhqTPmyWnDA@mail.gmail.com>
 <8EECE6C8A0ED7944B6166E1CCAF815E25996B24B93@2K8EXC01.m4u.com.br>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Sat, 6 Oct 2012 11:23:52 +0200
Message-ID: 
 <CAGB5yNn2vMsRrTt_p7kQBv_5xq4+6m+eWHCSx7SuyOijGe0cSQ@mail.gmail.com>
Subject: Re: Netty or Mina Async in the same socket
To: users@camel.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 5, 2012 at 7:55 PM, Flavio Magacho - M4U
<flavio.magacho@m4u.com.br> wrote:
> Claus, Thank you.
> It works, I think that I missed the transform tag :).
> I Simply set the body.
>
> But I got some concurrency problems.
> I opened 2 connections. . . and it mixes data between them.
>

Ah yeah we should use an ordered thread pool that Netty offers. I
logged a ticket
https://issues.apache.org/jira/browse/CAMEL-5689

> Is this component thread safe?
>
> Thank you!
> Magacho
>
>
> -----Original Message-----
> From: Claus Ibsen [mailto:claus.ibsen@gmail.com]
> Sent: sexta-feira, 5 de outubro de 2012 12:15
> To: users@camel.apache.org
> Subject: Re: Netty or Mina Async in the same socket
>
> Hi
>
> I have added an unit test that does netty request/reply async and uses th=
e same channel to write the response back http://svn.apache.org/viewvc?rev=
=3D1394556&view=3Drev
>
>
>
> On Thu, Oct 4, 2012 at 3:03 PM, Flavio Magacho - M4U <flavio.magacho@m4u.=
com.br> wrote:
>> Ok Claus let me try to show you what I=C2=B4m trying to do:
>>
>> <camelContext id=3D"context-teste-claus" xmlns=3D"http://camel.apache.or=
g/schema/blueprint">
>>                 <route>
>>                         <from   uri=3D"netty:tcp://localhost:10022?textl=
ine=3Dtrue&amp;sync=3Dtrue&amp;reuseAddress=3Dtrue&amp;synchronous=3Dfalse"=
 />
>>                         <log message=3D"reading ${bodyt}" />
>>                         <to uri=3D"activemq:readQueue" />
>>                 </route>
>>                 <route>
>>                         <from   uri=3D"activemq:writeQueue?concurrentCon=
sumers=3D10&amp;maxConcurrentConsumers=3D10" />
>>                         <setBody>
>>                                 <simple>Echo: ${body.text}!</simple>
>>                         </setBody>
>>                         <log message=3D"Writing ${body}" />
>>                         <to uri=3D"netty:tcp://localhost:10022?textline=
=3Dtrue&amp;sync=3Dfalse&amp;reuseAddress=3Dtrue&amp;synchronous=3Dfalse" /=
>
>>                 </route>
>> </camelContext>
>>
>> And I want to write in the same socket that the messages arrives.
>> The idea is to make the message exchange process to be Async.
>>
>> I tried to use the Headers that you said, but they are not Serializable,=
 so I=C2=B4ll need to write an endpoint based on the camel-netty and keep a=
 hashmap with the channel and a channel identifier as a key. I Should write=
 this identifier in the message properties and then, when it comes back, I=
=C2=B4ll be able to write it back in the same socket. Does it Makes sense t=
o you?
>>
>> Thanks,
>> Magacho
>>
>> -----Original Message-----
>> From: Claus Ibsen [mailto:claus.ibsen@gmail.com]
>> Sent: quinta-feira, 4 de outubro de 2012 03:30
>> To: users@camel.apache.org
>> Subject: Re: Netty or Mina Async in the same socket
>>
>> On Thu, Oct 4, 2012 at 12:54 AM, Chad Beaulac <cabeaulac@gmail.com> wrot=
e:
>>> Hi Flavio,
>>>
>>> You can't do what you're asking for using camel-mina or camel-mina2 at =
this point in time.
>>>
>>
>> He can grab the netty channel as its enriched on the message as a header=
. Then use that channel to write the 2nd message back. He would need to cod=
e that. Its a matter though where and when the 2nd message should be send b=
ack.
>> And what triggers when this should happen.
>>
>> Maybe you can tell us a bit more about what you do in a Camel route eg?
>>
>> from netty?sync=3Dfalse
>>  to ???
>>
>> So you want at ?? something to process the incoming message, and use the=
 same socket to send back a reply message?
>>
>>
>>> Chad Beaulac
>>> Objective Solutions, Inc.
>>> www.objectivesolutions.com
>>> chad@objectivesolutions.com
>>>
>>>
>>> On Oct 3, 2012, at 9:35 AM, Flavio Magacho - M4U wrote:
>>>
>>>> Hi,
>>>> My name is Flavio Magacho.
>>>> I have a specific problem:
>>>>
>>>> I=C2=B4ll receive a socket connection and receive messages in this soc=
ket.
>>>> The point is to answer the messages, they should be send by the same s=
ocket and we can=E2=80=99t use the sync option.
>>>> I tried to use Mina and Netty The only way I got to answer in the same=
 socket is to use the Sync option.
>>>>
>>>> Did anyone knows how to do that?
>>>>
>>>> Flavio Magacho
>>>> Gerente de Desenvolvimento
>>>> Diretoria de Tecnologia da Informa=C3=A7=C3=A3o
>>>>   M4U
>>>> +55 (21) 2546-4050 =E2=96=AA Ramal: 4082
>>>> +55 (21) 8889-1572
>>>>
>>>> =C3=BE Antes de imprimir, pense em sua responsabilidade e compromisso =
com o Meio Ambiente.
>>>> O conte=C3=BAdo desta mensagem =C3=A9 confidencial e pode ser privileg=
iado. =C3=89 vedada a sua c=C3=B3pia ou divulga=C3=A7=C3=A3o.
>>>> The contents of this message are confidential and may be privileged. C=
opying or disclosing is prohibited.
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen


--=20
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen