You should use camel-netty4 with camel version 2.15.2 or higher. We had the
same problem but it is solved with 2.15.2. We send really lots of udp
packets and the file handles are stable. Before it took les then 30sec to
get into this issue.
Thomas
On Mon, Sep 14, 2015 at 12:31 PM, Willem Jiang
w
Hi,
tried it also with your Socket Client and works als fine.
Thomas
On Thu, Dec 11, 2014 at 10:20 AM, Thomas Termin
wrote:
> Hi,
>
> just tried the example route builder with mina2 (camel-2.14.0) and it
> works fine using telnet as client.
>
> telnet localhost 6789
Hi,
just tried the example route builder with mina2 (camel-2.14.0) and it works
fine using telnet as client.
telnet localhost 6789
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
hallo
Bye hallo
Connection closed by foreign host.
Which camel version do you use? Can you prov
Hello,
my answer was a bit confussing maybe. The first sentence is realted to your
sync=false which will not work in camel-mina2.
Btw. you should give camel-netty4 a try.
Thomas
On Wed, Dec 10, 2014 at 9:34 AM, Thomas Termin
wrote:
> Hello,
>
> Since camel-mina2 all consumer(from)
Hello,
Since camel-mina2 all consumer(from) exchanges are InOut. This is different
to camel-mina. Maybe it is related to that one.
But actually you say just it does not work. But what exactly is not working?
Thomas
On Tue, Dec 9, 2014 at 10:33 AM, Saurabh Singhal
wrote:
> I have been trying to
handling.
Thomas
On Wed, Feb 19, 2014 at 12:44 AM, Cristiano Costantini <
cristiano.costant...@gmail.com> wrote:
> Hi Thomas,
> where can I checkout the code you are working on?
> Maybe I can write some test to help you in your work...
>
> Cristiano
>
>
> 2014-02-18
I can't see where camel should limit this. You should turn on trace logging
to see the body which is send.
Thomas
On Mon, Feb 17, 2014 at 9:35 AM, bulutoprak wrote:
> Hi,
> I am using netty tcp route to handle requests and return a string message
> to
> the clients. The solution is working for
Hi,
I'm currently working on porting the netty component to netty 4. I also
implement that we can use client or server in consumer and producer. But as
I do this in my spare time it takes a little bit.
Thomas
On Tue, Feb 18, 2014 at 6:52 PM, Cristiano Costantini <
cristiano.costant...@gmail.com
We are using currently camel-mina for sending udp data. The problem is that
the default response handler log just all exception as error. The user of
the component has no possibility to react on some certain exceptions. It
e.g. an PortUnreachableException should be ignored the logger needs to be
se
I would like to extend the camel-netty component for connection less udp
support. Therefore I would introduce a new config parameter which enables
connection less sending of udp datagrams. If it is not connection less it,
a lot of errors come up when the receiver is not running on the given port.
I
Done for mina2 either.
On Wed, Apr 24, 2013 at 10:22 AM, Claus Ibsen wrote:
> Sounds good.
>
> And btw I dont think there was a good reason for the String
> conversion. It should have been bytes from the start.
>
> On Wed, Apr 24, 2013 at 10:13 AM, Thomas Termin
> wrote:
; > way.
> >
> > Regards,
> > Mike
> >
> >
> > On Mon, Apr 22, 2013 at 6:18 PM, Claus Ibsen
> wrote:
> >
> >> Hi
> >>
> >> Yeah udp should keep the data as byte[]. Fell free to log a JIRA and
> >> work on a patc
;
> On Mon, Apr 22, 2013 at 11:16 AM, Thomas Termin
> wrote:
> > Hi,
> >
> > no I don't use ByteBuffer as body type. The easiest example what I did is
> > to create the following route:
> >
> >
> >
> > Just route it from on p
we can do is to check the type of the body. If its already a
> ByteBuffer then use it as is.
> Otherwise we can try converting to byte[] and String. Which we need to
> create the ByteBuffer.
>
>
>
>
>
> On Thu, Apr 18, 2013 at 5:17 PM, Thomas Termin
> wrote:
> >
it should probably be byte[] instead of a String.
>
> And I assume you refer to camel-mina ?
>
> On Thu, Apr 18, 2013 at 1:35 PM, Thomas Termin
> wrote:
> > Hello,
> >
> > is there a special reason, that the MinaUdpProtocolCodecFactory encode
> > method always try t
Hello,
is there a special reason, that the MinaUdpProtocolCodecFactory encode
method always try to convert the message body to a string? Is there a way
to avoid the conversion to a String? I would need the falilback method
which is a conversion to a ByteBuffer. It would be nice to have that
config
16 matches
Mail list logo
