Hi,
I migrated from 2.11.1 to 2.12.0 and did not have too many issues, except in
terms of Netty.
My use case is that I need to create a custom ServerPipelineFactory, and
also require access to the ChannelGroup so that I can know when a new
channel is being added and when it is removed.
I also so
Hi
I am very new to Camel, and trying to implement some simple messaging to get
a feel for the basics.
Currently I have a simple Server using Camel Netty to listen for messages in
Request Only mode. It then sends the message it received via ActiveMQ, also
in Request Only mode. This seems to be wo
Today I have used a Request Reply approach with no JMS, Netty only.
I just sends a response and expects a reply. Again everything works great
for the first 10 messages then stops.
Is someone able to explain what I might be doing wrong?
Thanks
Matt
--
View this message in context:
http://camel.
eel that I must be missing something, with my usage of Camel and Netty.
And advice is appreciated.
From: maccamlc [via Camel] [mailto:ml-node+s465427n484764...@n5.nabble.com]
Sent: Wednesday, September 28, 2011 11:33 AM
To: Matthew McMahon
Subject: Re: Camel Netty Producer creating new connection o
OK, when I use the option "disconnect=true" on the Client (NettyProducer) it
works, ie. does not stop routing after 10 messages.
But I don't understand why it is necessary to open a channel, write data,
get a response and then close the channel for every individual message.
I feel that I must be
I have an interesting case, where one message type that a Netty Client send
will expect 2 response (1 immediately, and another asynchronously after some
processing has been done).
Is this possible to implement in Camel? I need the same SocketChannel to be
reused as well for receiving both response
No worries. This is a small Unit Test that shows the problem. Hope it helps:
--
package netty;
import java.util.Arrays;
import java.util.Collection;
import java.util.concurrent.TimeUnit;
import java.util.concurrent.atomic.AtomicBoolean;
import java.util.concurrent.atomic.AtomicInteger;
import j
No worries. I have just created an issue at
https://issues.apache.org/jira/browse/CAMEL-4556
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Netty-Producer-creating-new-connection-on-every-message-tp4844805p4912042.html
Sent from the Camel - Users mailing list archive at
