Hi If your application starts by sending to tcpA and you want to wait for a response (in your application), then you should set sync=true as an option on the tcpA URI. Where as sync in this case means in-out. If sync=false then it's like in-only (fire and forget).
message in -> tcpA->qA->tcpB -> message out message in -> tcpB->qB->tcpA -> message out Is not possible as the 1st tcpA and the last tcpA is not the same, so to speak. What you can do is: Application -> tcpA->qA->tcpB->qB : And the reply to Application is the OUT message from the exchange at qB. Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: Jeff V [mailto:[EMAIL PROTECTED] Sent: 7. november 2008 16:19 To: [email protected] Subject: RE: Usage of Mina in camelContext for TCP loop. I am still having problems getting a tcp connection to relay messages outbound. I can connect to the defined TCP socket, however any messages sent to a queue routed to the tcp connection are not getting received by my application. Do you know if the tcp connection is bidirectional like this once the connection is established? I need this to be bidirectional but not synchronous. <endpoint id="tcpA" uri="mina:tcp://localhost:42000?textline=true&sync=false" /> <endpoint id="tcpB" uri="mina:tcp://localhost:42001?textline=true&sync=false" /> <!-- You can use Spring XML syntax to define the routes here using the <route> element --> <route> <from ref="tcpA"/> <to uri="activemq:qA"/> </route> <route> <from ref="tcpB"/> <to uri="activemq:qB"/> </route> <route> <from uri="activemq:qA"/> <to ref="tcpB"/> </route> <route> <from uri="activemq:qB"/> <to ref="tcpA"/> </route> Note this code generated a large number of messages to qB, so there must be a loop happening here. I was expecting a bidirectional flow from tcpA to tcpB routed through qA and qB depending on direction of flow: message in -> tcpA->qA->tcpB -> message out message in -> tcpB->qB->tcpA -> message out Claus Ibsen wrote: > > Hi > > Glad you got it working. Learning Camel is very mich learn by doing, as > its so quick to get running that most people jump in right away. No need > to read a 200 pages .pdf to start ;) > > So please continue to post questions or issues, that is why we have this > vibrant community to help. > > > > These 'errors' is logged at DEBUG level while Camel is loading the type > converters based on classpath scanning the .jars. > > You can basically ignore this, or if you want to remedy it, you can add or > remove needed .jars. > > For instance you have this -test jar on the classpath > Loading from jar: C:\Program > Files\apache-activemq-5.1.0\bin\win32\..\..\lib\activemq-core-5.1.0-tests.jar > > That depends on the camel -test jars as well. So you could add this .jar > camel-core-1.4.0-tests.jar > > The -tests .jars is used as support classes for unit testing. So if you > don't use unit testing then you could remove all the -tests .jars all > together. > > > Med venlig hilsen > > Claus Ibsen > ...................................... > Silverbullet > Skovsgårdsvænget 21 > 8362 Hørning > Tlf. +45 2962 7576 > Web: www.silverbullet.dk > -----Original Message----- > From: Jeff V [mailto:[EMAIL PROTECTED] > Sent: 6. november 2008 21:43 > To: [email protected] > Subject: RE: Usage of Mina in camelContext for TCP loop. > > > I appreciate your patience Claus. > > I changed that to use the full uri in my routes: > > <route> > <from > uri="mina:tcp://localhost:42000?textline=true&sync=false"/> > <to uri="activemq:qA"/> > </route> > > <route> > <from uri="activemq:qA"/> > <to > uri="mina:tcp://localhost:42001?textline=true&sync=false"/> > </route> > > This cause some exception explosions in my logs: > http://www.nabble.com/file/p20369255/activemq.log activemq.log > > However, it seems I now have a tcp socket. That is accepting text lines. > Sweet!!! > -- > View this message in context: > http://www.nabble.com/Usage-of-Mina-in-camelContext-for-TCP-loop.-tp20348095s22882p20369255.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > > -- View this message in context: http://www.nabble.com/Usage-of-Mina-in-camelContext-for-TCP-loop.-tp20348095s22882p20382571.html Sent from the Camel - Users mailing list archive at Nabble.com.
