Thanks Clause - in this case that wasn't it - line wrapping made it less
obvious but you can see the second ? was in a
commented out section /* */ I had switched to object serialization to
try and track the problem which ultimately helped.
by switching to object serialization it started complaini
You uri is wrong. You can only have 1 ? in the ur. It should be &textline=true.
On Thu, Apr 8, 2010 at 9:14 PM, Andrew Chandler wrote:
> Is there anything wrong with this definition:
> from("direct:rcv").to("mina:tcp://" + pingResponseHost +":" +
> pingResponsePort + "?timeout=30&transferExc
Well I fixed it I think - our routes weren't expecting to return a
response and it ultimately seems to have turned out to the default of
sync=true , not sure why the error message in question was what it was
but essentially when work after mina was done and transitioned through a
splitter etc appar
Is there anything wrong with this definition:
from("direct:rcv").to("mina:tcp://" + pingResponseHost +":" +
pingResponsePort + "?timeout=30&transferExchange=false"/*+
"?textline=true"*/);
My expectation is that the textline is ignored (commented out) and that
I have set a tcp object serialize
Ok further weirdness - since I'm using tcp and I don't really care if my
objects go as text I just wanted a lightweight socket protocol I took
the textline bit out of my uri's (should be serialized objects now )
So in watching it worked for a couple of seconds and then it blew up,
however when it b
Ok I'll look at that but what puzzles me is if each message is sent and
is only ever an int,IPADDRESS structure how could it exceed 1024? Or
is the buffer length really ALL messages that are pending for work?
On Thu, 2010-04-08 at 19:59 +0200, Claus Ibsen wrote:
> Hi
>
> Have you looked at
Hi
Have you looked at the encorder/decoder max length options.
http://camel.apache.org/mina.html
Could be that Mina has a default of one of them at 1024.
On Thu, Apr 8, 2010 at 7:14 PM, Andrew Chandler wrote:
> Hi there folks - hoping you can help me from gaining a permanent dent in
> my end
Hi there folks - hoping you can help me from gaining a permanent dent in
my end from hitting the wall.We are using Camel for many things but
we have setup a dedicate route to a simple standalone process - both
ends set up a send and a receive route (different ports) - The route
works until it
