I see.
If Server_9900 is the sender/producer/client, then the name Server_9900 is
a misnomer, but I understand now server has a different meaning in your
program.
I would do something like this to send to the consumer, and get a response,
copied from a unit test[1].
String reply =
template.reques
Tariq,
Thanks for the reply.
Server_9900 is written to send messages to CAMEL, and to it "java program"
needs to be started prior to running CAMEL application (is this not the
right thing to do) . How can otherwise, messages be sent to port 9201 for
CAMEL to consume?
--
View this message in con
Server_9900 is claiming the same port as camel, so for sure it's
unavailable to camel.
Taariq
On Wed, Nov 23, 2011 at 1:10 PM, newbiee wrote:
> Tariq,
>
> Attached is the entire program. This is a very simple route and it doesn't
> require me to copy code from Hadrian's example.
>
> http://ca
Tariq,
Attached is the entire program. This is a very simple route and it doesn't
require me to copy code from Hadrian's example.
http://camel.465427.n5.nabble.com/file/n5016269/netty.zip netty.zip
Attached is the java program that I run prior to executing CAMEL
application.
http://camel.46
@Taariq, I suspect newbiee modified a sample I put out [1]to help him
(hopefully others too). But he did it in mysterious ways.
Hadrian
[1] https://github.com/hzbarcea/camel-samples/tree/master/camel-digi
On 11/22/2011 11:05 PM, Taariq Levack wrote:
Can you post a running maven project?
--
Can you post a running maven project?
Taariq
On Tue, Nov 22, 2011 at 11:51 PM, Tim wrote:
> Then I'm inclined to think that Hadrian's suggestion is correct and you are
> using the same port twice in your program or you are starting up twice for
> some reason.
>
> On Tue, Nov 22, 2011 at 2:38 PM
Then I'm inclined to think that Hadrian's suggestion is correct and you are
using the same port twice in your program or you are starting up twice for
some reason.
On Tue, Nov 22, 2011 at 2:38 PM, newbiee wrote:
> Tim
>
> Prior to posting this question, I tried it using 9900 port but no luck!
>
Tim
Prior to posting this question, I tried it using 9900 port but no luck!
--
View this message in context:
http://camel.465427.n5.nabble.com/CAMEL-is-throwing-error-tp5014337p5014654.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Could it be a stupid error of having localhost:8080 as your brokerURL?
Anyways, in the same line as Hadrian's answer. Why not just change 8080 to
something else like and give it another try?
On Tue, Nov 22, 2011 at 1:55 PM, newbiee wrote:
> Hadrian:
>
> I have sent my route. Here is the com
Hadrian:
I have sent my route. Here is the complete XML file
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:camel="http://camel.apache.org/schema/spring";
xsi:schemaLocation="
http://www.springframework.or
Newbie, that probably means that your program tries to open a socket on
the same port twice. But seriously, if you are having trouble with this
kind of issues, this is really not the place where you learn how to
investigate and resolve them.
Cheers,
Hadrian
On 11/22/2011 02:15 PM, newbiee wro
Claus:
Thanks for the reply.
As I have mentioned in my question. I have Java Client/Server program which
opens the socket conneciont using the same port i.e 8000.
I am able to run my java program and pass messages back and forth. When the
program is being run I applied the following command net
Some other service is already using port 8000 on your computer.
Try using another port number which is free, or stop that other service.
On Tue, Nov 22, 2011 at 7:50 PM, newbiee wrote:
> I have define the following simple route for testing:
>
> http://camel.apache.org/schema/spring";>
>
>
>
13 matches
Mail list logo
