Re: Camel-QuickFIX jar issues
In the past, james Strachan publish those jars files on maven repository of iona / fusesource. Regards, Charles Moulliard Senior Enterprise Architect (J2EE, .NET, SOA) Apache Camel - Karaf - ServiceMix Committer ~~~ Blog : http://cmoulliard.blogspot.com | Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard On Wed, Aug 25, 2010 at 3:18 AM, Hadrian Zbarcea hzbar...@gmail.com wrote: Thanks for reporting this. I created https://issues.apache.org/activemq/browse/CAMEL-3076. Unfortunately jars are not available in any m2 repo, so we'll have have to republish them in some public place. I will try to get in touch with Steve for the second part of your question. Cheers Hadrian On Aug 24, 2010, at 8:22 PM, vcheruvu wrote: Hi, I have come across another issue with Jar dependency in Camel. I am exploring Camel-QuickFix component. I realized that Maven is unable to download Quickfix-all jar file from Jarvana. I have come to know that Jarvana or other ibiblio repository do not have quickfix jar files. Any idea what is happening there? Recently, Quickfixj released new version 1.5.0. Are there any plans in the roadmap to upgrade Camel-quickfix to use Quickfixj 1.5.0 version? I remember on this forum Steve Bate (QuickFixJ committer/founder) has been looking to re-write Camel-QuickFix component and suggested few enhancements. Is he still involved on camel-quickfix integration? Kind regards, -Vid- -- View this message in context: http://camel.465427.n5.nabble.com/Camel-QuickFIX-jar-issues-tp2652022p2652022.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel-QuickFIX jar issues
On Wed, Aug 25, 2010 at 8:43 AM, Charles Moulliard cmoulli...@gmail.com wrote: In the past, james Strachan publish those jars files on maven repository of iona / fusesource. Then it has to be a long time ago :) It was usually me uploading those jars. Regards, Charles Moulliard Senior Enterprise Architect (J2EE, .NET, SOA) Apache Camel - Karaf - ServiceMix Committer ~~~ Blog : http://cmoulliard.blogspot.com | Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard On Wed, Aug 25, 2010 at 3:18 AM, Hadrian Zbarcea hzbar...@gmail.com wrote: Thanks for reporting this. I created https://issues.apache.org/activemq/browse/CAMEL-3076. Unfortunately jars are not available in any m2 repo, so we'll have have to republish them in some public place. I will try to get in touch with Steve for the second part of your question. Cheers Hadrian On Aug 24, 2010, at 8:22 PM, vcheruvu wrote: Hi, I have come across another issue with Jar dependency in Camel. I am exploring Camel-QuickFix component. I realized that Maven is unable to download Quickfix-all jar file from Jarvana. I have come to know that Jarvana or other ibiblio repository do not have quickfix jar files. Any idea what is happening there? Recently, Quickfixj released new version 1.5.0. Are there any plans in the roadmap to upgrade Camel-quickfix to use Quickfixj 1.5.0 version? I remember on this forum Steve Bate (QuickFixJ committer/founder) has been looking to re-write Camel-QuickFix component and suggested few enhancements. Is he still involved on camel-quickfix integration? Kind regards, -Vid- -- View this message in context: http://camel.465427.n5.nabble.com/Camel-QuickFIX-jar-issues-tp2652022p2652022.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
threads(5,10) - spring DSL
Hi, What is the equivalent in srping DSL of the following java DSL syntax from(seda:stageName).thread(5,10) -- from uri=seda:stageName/ ??? Regards, Charles Moulliard Senior Enterprise Architect (J2EE, .NET, SOA) Apache Camel - Karaf - ServiceMix Committer ~~~ Blog : http://cmoulliard.blogspot.com | Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard
Re: threads(5,10) - spring DSL
On Wed, Aug 25, 2010 at 8:53 AM, Charles Moulliard cmoulli...@gmail.com wrote: Hi, What is the equivalent in srping DSL of the following java DSL syntax from(seda:stageName).thread(5,10) -- from uri=seda:stageName/ ??? Use your IDE to help you. Usually you just press ctrl + space and it shows what you can type/select. threads poolSize=5 maxPollSize=10/ Check out 10.3.1 in the Camel book. Regards, Charles Moulliard Senior Enterprise Architect (J2EE, .NET, SOA) Apache Camel - Karaf - ServiceMix Committer ~~~ Blog : http://cmoulliard.blogspot.com | Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
Re: threads(5,10) - spring DSL
Unfortunately, auto-completion of Eclipse tool does not work fine When we add the element-name that works but not for the element ex : camel:camelContext Ok camelContext NOK I will check the content of the book. Regards, Charles Moulliard Senior Enterprise Architect (J2EE, .NET, SOA) Apache Camel - Karaf - ServiceMix Committer ~~~ Blog : http://cmoulliard.blogspot.com | Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard On Wed, Aug 25, 2010 at 8:58 AM, Claus Ibsen claus.ib...@gmail.com wrote: On Wed, Aug 25, 2010 at 8:53 AM, Charles Moulliard cmoulli...@gmail.com wrote: Hi, What is the equivalent in srping DSL of the following java DSL syntax from(seda:stageName).thread(5,10) -- from uri=seda:stageName/ ??? Use your IDE to help you. Usually you just press ctrl + space and it shows what you can type/select. threads poolSize=5 maxPollSize=10/ Check out 10.3.1 in the Camel book. Regards, Charles Moulliard Senior Enterprise Architect (J2EE, .NET, SOA) Apache Camel - Karaf - ServiceMix Committer ~~~ Blog : http://cmoulliard.blogspot.com | Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
camelContext depending on dataSource
Hi, after upgrading to Camel 2.4.0 I am having a problem with some routes that depend on Hibernate daos. It all started with this error message: ... Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in class path resource [applicationContext-HSQLdb.xml]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'camelContext': Invocation of init method failed; nested exception is org.apache.camel.RuntimeCamelException: org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'sessionFactory': FactoryBean which is currently in creation returned null from getObject ... Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'camelContext': Invocation of init method failed; nested exception is org.apache.camel.RuntimeCamelException: org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'sessionFactory': FactoryBean which is currently in creation returned null from getObject.. It seems that when I define a bean with dependencies on hibernate DAOs, then the Camelcontext also becomse dependant on the sessionFactory, someting I find very odd. This whole setup worked very nicely before I upgraded to Spring 3/Camel 2.4.0. I just cannot understand what has causing this. According to google the error usually shows up when I have circular dependencies, but in this case that does not seem to be the issue. I have now refactored all objects so that they use setter injection, but this doesn't help. No dice. It seems that the camelContext changes the order that beans are created in. Basicly, this does not create the error: beans xmlns=http://www.springframework.org/schema/beans; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:aop=http://www.springframework.org/schema/aop; xmlns:context=http://www.springframework.org/schema/context; xmlns:camel=http://camel.apache.org/schema/spring; xsi:schemaLocation= http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context.xsd bean id=IndexLookupRoute class=com.scanmine.router.routes.IndexLookupRoute / camel:camelContext camel:contextScan camel:includes*/camel:includes /camel:contextScan /camel:camelContext But the route is not loaded into the camel process. While this: camel:camelContext camel:routeBuilder ref=IndexLookupRoute/ /camel:camelContext Generates the error above. Any tips? -- Regards / Med vennlig hilsen Tarjei Huse Mobil: 920 63 413
Re: camelContext depending on dataSource
Can you post the code of your route On Wed, Aug 25, 2010 at 2:07 PM, Tarjei Huse tar...@scanmine.com wrote: Hi, after upgrading to Camel 2.4.0 I am having a problem with some routes that depend on Hibernate daos. It all started with this error message: ... Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in class path resource [applicationContext-HSQLdb.xml]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'camelContext': Invocation of init method failed; nested exception is org.apache.camel.RuntimeCamelException: org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'sessionFactory': FactoryBean which is currently in creation returned null from getObject ... Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'camelContext': Invocation of init method failed; nested exception is org.apache.camel.RuntimeCamelException: org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'sessionFactory': FactoryBean which is currently in creation returned null from getObject.. It seems that when I define a bean with dependencies on hibernate DAOs, then the Camelcontext also becomse dependant on the sessionFactory, someting I find very odd. This whole setup worked very nicely before I upgraded to Spring 3/Camel 2.4.0. I just cannot understand what has causing this. According to google the error usually shows up when I have circular dependencies, but in this case that does not seem to be the issue. I have now refactored all objects so that they use setter injection, but this doesn't help. No dice. It seems that the camelContext changes the order that beans are created in. Basicly, this does not create the error: beans xmlns=http://www.springframework.org/schema/beans; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:aop=http://www.springframework.org/schema/aop; xmlns:context=http://www.springframework.org/schema/context; xmlns:camel=http://camel.apache.org/schema/spring; xsi:schemaLocation= http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context.xsd bean id=IndexLookupRoute class=com.scanmine.router.routes.IndexLookupRoute / camel:camelContext camel:contextScan camel:includes*/camel:includes /camel:contextScan /camel:camelContext But the route is not loaded into the camel process. While this: camel:camelContext camel:routeBuilder ref=IndexLookupRoute/ /camel:camelContext Generates the error above. Any tips? -- Regards / Med vennlig hilsen Tarjei Huse Mobil: 920 63 413 -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
RE: netty issue
1. That is good. Is it always going to run in async mode, is there any option
to make it run in sync mode. Also with threads(1), I can make sure only one TCP
connection and stream messages one after the other sequentially and receive
messages asynchronously?.
2.
from(netty:tcp://localhost:6205?textline=truesync=true).process(new
Processor() {
int i=0;
public void process(Exchange exchange) throws Exception
{
String body = exchange.getIn().getBody(String.class);
Thread.sleep(2000);
exchange.getOut().setBody(Bye 1 + body);
// if(i++%2==1) throw new IOException(custom
exception);
}
});
TCP server replied and producer got response. I guess it may be a defect in the
netty producer.
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: Sunday, August 22, 2010 9:02 AM
To: users@camel.apache.org
Subject: Re: netty issue
On Thu, Aug 19, 2010 at 11:20 PM, Sadanand Kusma sku...@arccorp.com wrote:
As suggested, I tried this with exchange pattern as inout. I think there are
2 issues.
1. it is not continuing with reply immediately, it waits till it receives a
response. is this how it supposed to work in async mode?.
No it doesn't wait in that sense there is no thread blocked. When the
reply comes back the async routing engine will continue in the Camel
route, and therefore in your example go to the log:reply endpoint.
That may be why you think it waits.
I would think that like we had in deprecated toasync feature, it sends
the async response to a new route to process messages received
asynchronously.
from(file:///test/test/response)
.convertBodyTo(String.class)
.threads(1)
.to(ExchangePattern.InOut,netty:tcp://localhost:6205?textline=truesync=true)
.to(log:+++ reply);
2. it throws this exception even though it receives the response. Detailed
stack trace is in the first post.
2010-08-19 16:40:38,663 [ Hashed wheel timer #1] DefaultErrorHandler
DEBUG Failed delivery for exchangeId:
afa68733-6228-4da2-b831-5a56ee39db51. On delivery attempt: 0 caught:
org.apache.camel.ExchangeTimedOutException: The OUT message was not received
within: 3 millis. Exchange[GenericFileMessage with body: Bye 1hello1]
The TCP server did not reply within the 30 seconds default timeout. So
check the TCP server what is happening.
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: Thursday, August 19, 2010 11:06 AM
To: users@camel.apache.org
Subject: Re: netty issue
On Thu, Aug 19, 2010 at 4:45 PM, Sadanand Kusma sku...@arccorp.com wrote:
Thanks for the response, if you set sync=true doesn't it make a synchronous
call.
Are you saying that it always runs in a async mode?,how do we tell it to run
in an async mode?.
Well the sync option is badly named, now the async non blocking
routing engine is in place.
Its kinda still there for compatibility. So view the sync as
request/reply (InOut)
What you need to ensure is the MEP is InOut. And sync=true is like saying
InOut.
The async routing ensures the thread is not blocked while waiting for
the reply to come back from the TCP server.
We should maybe @deprecate sync option and let it check the MEP of the
Exchange.
-Original Message-
From: Willem Jiang [mailto:willem.ji...@gmail.com]
Sent: Wednesday, August 18, 2010 10:43 PM
To: users@camel.apache.org
Subject: Re: netty issue
I just checked the netty's doc and camel-netty producer's code, if you
set the sync=false, the producer will never expect the response, and the
async callback will never be called.
So you just need to change your route like this
from(file:///test/test/response)
.convertBodyTo(String.class)
.threads(1)
.to(netty:tcp://localhost:6205?textline=truesync=true)
.to(log:+++ reply);
Willem
Sadanand Kusma wrote:
I am actually trying out asynchronous messaging with Netty producer. I get
below exception even though sync =false. Also, Is this the right way to
implement asynchronous processing.
Here is my route:
from(netty:tcp://localhost:6205?textline=truesync=true).process(new
Processor() {
int i=0;
public void process(Exchange exchange) throws Exception {
String body = exchange.getIn().getBody(String.class);
Thread.sleep(2000);
exchange.getOut().setBody(Bye 1 + body);
}
});
from(file:///test/test/response)
.convertBodyTo(String.class)
.threads(1)
.to(netty:tcp://localhost:6205?textline=truesync=false)
.to(log:+++
netty timeout bug.
Camel netty bug created. https://issues.apache.org/activemq/browse/CAMEL-3081
JMS Message header getting lost
I am sending data through ActiveMQ and Camel. I set a property value in the TextMessage object prior to sending to ActiveMQ. The property value I sent prior to sending to ActiveMQ is gone when I receive the message on the other side. How can I prevent this from happening?
Re: JMS Message header getting lost
I think I figured it out. I have a processor in which I am creating a new message to pass along. I need to set the headers in the new message with the headers from the old message. Is that the proper way to copy over message properties? On Wed, Aug 25, 2010 at 4:41 PM, Mark Webb elihusma...@gmail.com wrote: I am sending data through ActiveMQ and Camel. I set a property value in the TextMessage object prior to sending to ActiveMQ. The property value I sent prior to sending to ActiveMQ is gone when I receive the message on the other side. How can I prevent this from happening?
Camel Quickfix protocol level messages
Is it possible to receive session/protocol level messages via the
Camel/QuickFix combo in addition to the application level messages. I
configured my setup to connect to a Fix server and send messages using a
producer template:
ProducerTemplate producer = camelContext.createProducerTemplate();
producer.send(quickfix-client:configFile.cfg, exchange);
With this I can say send a NewOrderSingle.
To receive the ExecutionReport back I configured the following route:
camelContext.addRoutes(new RouteBuilder() {
@Override
public void configure() throws Exception {
from(quickfix-client:configFile.cfg).process(new Processor() {
public void process(Exchange e) throws
Exception {
//process incoming message
}
});
}
});
I can receive application level messages fine with this setup. However, how
can I configure Camel/QuickFix to receive session level messages along the
application level messages. One example is if I send a message that is
missing a required field or has invalid data and I get back a Reject
MsgType(35) = 3 ?
(http://btobits.com/fixopaedia/fixdic42/index.html?message_Reject_3.html)
Those messages can't seem to make it to my route configured above.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Quickfix-protocol-level-messages-tp2653431p2653431.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: JMS Message header getting lost
If you create a new Message you can use the copyFrom(message) to do this job. Willem Mark Webb wrote: I think I figured it out. I have a processor in which I am creating a new message to pass along. I need to set the headers in the new message with the headers from the old message. Is that the proper way to copy over message properties? On Wed, Aug 25, 2010 at 4:41 PM, Mark Webb elihusma...@gmail.com wrote: I am sending data through ActiveMQ and Camel. I set a property value in the TextMessage object prior to sending to ActiveMQ. The property value I sent prior to sending to ActiveMQ is gone when I receive the message on the other side. How can I prevent this from happening?
