Hi Tereza Usually it says why it failed to bind. I suppose you checked that your port is not still opened by another process you were debugging or whatever.
There's nothing wrong simulating data from a file instead, just ensure that you don't now have 2 routes trying to own that port. PS if you want to listen you don't need your IP, you can use 0.0.0.0 as Willem said. Taariq On 11 Aug 2011, at 11:11 PM, Tereza Nedelescu <[email protected]> wrote: > Hi, > > The code below > <camel:route> > <camel:from uri="file:/path/src/data/input/inDir?noop=true" /> > <camel:to uri="netty:tcp://999.999.99.99:8985"/> > </camel:route> > > <camel:route> > <camel:from uri="netty:tcp://999.999.99.99:8985" /> > <camel:pipeline> > <bean ref="customProcessor"/> > <camel:to uri="file:/path/src/data/output/Pipeline" /> > </camel:pipeline> > </camel:route> > > gives the following error: SEVERE: Context initialization failed > org.apache.camel.RuntimeCamelException: > org.jboss.netty.channel.ChannelException: Failed to bind to > /999.999.99.99:8985 > at ....... > (Note: 999.999.99.99 is not actually my ip address) > > I'm trying to simulate having input to the bean "customProcessor" coming > from a socket. I cannot do that directly, so I send text from a file to a > socket, and then I try to read from the same socket. Is there something > wrong with this ? > > Thanks, > Tereza > > -- > View this message in context: > http://camel.465427.n5.nabble.com/File-contents-socket-socket-pipeline-fails-tp4691086p4691086.html > Sent from the Camel - Users mailing list archive at Nabble.com.
