Camel file pick up conditionally
Hi I have a scenario. I need to pick a file directory. but 1st i need to check DB record status. If it is true pick file else not. Is this kind of scenario can be implemented using camel spring dsl configuration. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-file-pick-up-conditionally-tp5752725.html Sent from the Camel - Users mailing list archive at Nabble.com.
Camel-in-Action : CXF Contract First
We're in the process of re-platforming part of our integration capability to FuseSource with Apache Camel. Just going over some of our existing web services I had a look on the Camel-in-Action sample code with CXF, and got a bit stuck on the example. What I see is that 'mvn test' runs fine with no failures, however when I start it up with 'mvn camel:run', and use a Soap client tool (SoapUI, XMLSpy) to first import the WSDL and then send a request, I can see my soap body in the response is always empty. After I added some extra logging in the route, first a log message which displays the $(body) just after the from uri=cxf:bean:orderEndpoint, and then a log with showAll=trueamp;multiline=true, before and after setting the 'OK' as a response in the ransform there is some more funnies: When I run the mvn test, the output for the body is 'motor' the first of the 3 parameters sent in the test class (params.add(motor); params.add(1); params.add(honda); If I send it via my SOAP tool there is nothing logged. In both cases I see the Body is set to 'OK', with BodyType String (and out is null) however that 'OK' does not make it back when sending my request via the Soap tool. Am I missing something? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-in-Action-CXF-Contract-First-tp5752731.html Sent from the Camel - Users mailing list archive at Nabble.com.
Camel-hbase : scan operation
Hello everybody, I'm new to camel. I'm using the camel-hbase component http://camel.apache.org/hbase.html and would like to perform a scan operation and get multiple rows with the producer. However I didn't find a way to do that with camel-hbase. If I create a route this way : I don't get anything in the output message (empty header, empty body). I tryed to add a CamelHBaseFamily and CamelHBaseQualifier value in the input header (the request should give the list of values from the column family:qualifier I choosed), however I only got 1 of the values of the list in the header. The body is always empty. I took a look at the source code of camel-hbase and what I got seems to be logical. Am I doing something wrong ? Did I miss something ? Then I looked at the camel-mongodb component to check if there was the same problem. In its producer MongoDbProducer https://github.com/apache/camel/blob/master/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbProducer.java , for a findAll request, it puts the results as an array in the body of the message : But I didn't find anything similar in camel-hbase. Thanks in advance, -- View this message in context: http://camel.465427.n5.nabble.com/Camel-hbase-scan-operation-tp5752732.html Sent from the Camel - Users mailing list archive at Nabble.com.
sftp excluding filename with date
Hello,
I try to download some files with names like this:
_MMDD(with MMDD the name of the day)
from(uriSFTP.concat(exclude=${date:now:MMdd}))
.to(local);
But I don't want to donwload today's file.
I can't use ${date:now:MMdd} with exclude.
How to do?
--
View this message in context:
http://camel.465427.n5.nabble.com/sftp-excluding-filename-with-date-tp5752734.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: sftp excluding filename with date
Hi
See the filter option and write a java bean that returns true|false if
the file should be downloaded or not.
http://camel.apache.org/file2
On Tue, Jun 24, 2014 at 11:07 AM, Benito jack...@laposte.net wrote:
Hello,
I try to download some files with names like this:
_MMDD(with MMDD the name of the day)
from(uriSFTP.concat(exclude=${date:now:MMdd}))
.to(local);
But I don't want to donwload today's file.
I can't use ${date:now:MMdd} with exclude.
How to do?
--
View this message in context:
http://camel.465427.n5.nabble.com/sftp-excluding-filename-with-date-tp5752734.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Jms Client_Acknowledgement Forced failure options
I am writting what would be the equivalent of an error queue retry ultility for a camel application that moves messages between different jms queues. I am looking for it to contain several features: 1) Only process messages that are older than when the route was created so messages that are sent back to the error queue aren't infinitely retried - I accomplish this by checking the JMSTimestamp header on the exchange and then forcing a route shutdown and throwing an exception to ensure the message remains on the queue with CLIENT_ACKNOWLEDGE mode. 2) Stop reading from the queue when there are no messages remaining. -I accomplish this by generating a route on the queue and adding that route Id to a list in a bean. Everytime that route runs it updates a timestamp in the bean to make sure it is still processing. Another route off a quartz timer runs every few seconds to find any timestamps that are past a timeout interval and stops those routes. What I am trying to do is remove the manual exception throwing for keeping the jms message on the queue because I don't want this application to be throwing an actual error over a standard feature that it needs. Is there anyway to end processing on an exchange and not call the jms.acknowledge() method behind the scenes? -- View this message in context: http://camel.465427.n5.nabble.com/Jms-Client-Acknowledgement-Forced-failure-options-tp5752737.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel file pick up conditionally
Is it possible to pick a file conditionally. To pick a file from dir I need to check status in DB. If status is ready then only file should be picked up. Is this kind of scenario possible. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-file-pick-up-conditionally-tp5752725p5752736.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel mail: content-transfer-encoding configurable
Hi, ok, just for clarification what would be a good solution for this: I've not mentioned that we need the content-transfer-encoding for the attachments of the mail. Some ideas from my side: 1. use a parameter like contentType, let's say content-transfer-encoding: If this parameter is set ALL attachments will have this content-transfer-encoding. The problem I see here is that it's probably a bit misleading as the contentType parameter affects the mailbody and content-transfer-encoding the attachments. Maybe this issue could be solved by renaming the parameter to something like attachment-transfer-encoding 2. when an attachment will be added to the exchange object the contentType could be defined like this: In the org.apache.camel.component.mail.MailBinding class then we extract the content transfer encoding, for example: Maybe we discuss the possible solutions before I start patching. kind regards, Christoph -- View this message in context: http://camel.465427.n5.nabble.com/camel-mail-content-transfer-encoding-configurable-tp5752504p5752738.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel file pick up conditionally
Hi Yes you can do that. You can for example implement a custom filter, where you return true if the DB check is okay, or false if not. See the filter option at http://camel.apache.org/file2 On Tue, Jun 24, 2014 at 2:09 PM, sakchakravarthi ajit.kalyan.chakravar...@gmail.com wrote: Is it possible to pick a file conditionally. To pick a file from dir I need to check status in DB. If status is ready then only file should be picked up. Is this kind of scenario possible. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-file-pick-up-conditionally-tp5752725p5752736.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: camel mail: content-transfer-encoding configurable
Maybe something similar to the ContentTypeResolver is also a good solution -- View this message in context: http://camel.465427.n5.nabble.com/camel-mail-content-transfer-encoding-configurable-tp5752504p5752744.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel-hbase : scan operation
Ok, I found the answer to my question. For people that might be asking the same, if there are multiple results, the header of the output message will contain all of them in its header with number suffixes (like CamelHBaseValue, CamelHBaseValue2, CamelHBaseValue3...). -- View this message in context: http://camel.465427.n5.nabble.com/Camel-hbase-scan-operation-tp5752732p5752743.html Sent from the Camel - Users mailing list archive at Nabble.com.
camel-solr, SSL, and SolrCloud
Hello Camel Users! My company has been doing a lot with the camel-solr component and we recently added SSL and SolrCloud support. We'd like to submit this back to Camel, so my question is whether we should make this a patch of camel-solr or create a completely separate component (maybe camel-solrs or camel-solrcloud). Do you have a preference? Thank you, Scott
Re: camel-solr, SSL, and SolrCloud
Hi Can it be in the existing camel-solr component? On Tue, Jun 24, 2014 at 4:55 PM, Scott Stults sstu...@opensourceconnections.com wrote: Hello Camel Users! My company has been doing a lot with the camel-solr component and we recently added SSL and SolrCloud support. We'd like to submit this back to Camel, so my question is whether we should make this a patch of camel-solr or create a completely separate component (maybe camel-solrs or camel-solrcloud). Do you have a preference? Thank you, Scott -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: camel-solr, SSL, and SolrCloud
Sure can! In fact that'd be the easiest. I'll make sure it's go and send a pull request. Is there something I should do with Jira as well? -Scott On Tue, Jun 24, 2014 at 11:09 AM, Claus Ibsen claus.ib...@gmail.com wrote: Hi Can it be in the existing camel-solr component? On Tue, Jun 24, 2014 at 4:55 PM, Scott Stults sstu...@opensourceconnections.com wrote: Hello Camel Users! My company has been doing a lot with the camel-solr component and we recently added SSL and SolrCloud support. We'd like to submit this back to Camel, so my question is whether we should make this a patch of camel-solr or create a completely separate component (maybe camel-solrs or camel-solrcloud). Do you have a preference? Thank you, Scott -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/ -- Scott Stults | Founder Solutions Architect | OpenSource Connections, LLC | 434.409.2780 http://www.opensourceconnections.com
Re: camel-solr, SSL, and SolrCloud
Hi Yeah log a JIRA about this enhancement, and then do a PR. Some info about contributing in general here http://camel.apache.org/contributing.html On Tue, Jun 24, 2014 at 5:46 PM, Scott Stults sstu...@opensourceconnections.com wrote: Sure can! In fact that'd be the easiest. I'll make sure it's go and send a pull request. Is there something I should do with Jira as well? -Scott On Tue, Jun 24, 2014 at 11:09 AM, Claus Ibsen claus.ib...@gmail.com wrote: Hi Can it be in the existing camel-solr component? On Tue, Jun 24, 2014 at 4:55 PM, Scott Stults sstu...@opensourceconnections.com wrote: Hello Camel Users! My company has been doing a lot with the camel-solr component and we recently added SSL and SolrCloud support. We'd like to submit this back to Camel, so my question is whether we should make this a patch of camel-solr or create a completely separate component (maybe camel-solrs or camel-solrcloud). Do you have a preference? Thank you, Scott -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/ -- Scott Stults | Founder Solutions Architect | OpenSource Connections, LLC | 434.409.2780 http://www.opensourceconnections.com -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
camel-cxf with rpc/literal style wsdl?
I am having the following problem and I am not sure if this is a known limitation. I have a rpc/literal styled wsdl that works fine with standalone CXF and would like to use this wsdl in my Camel scenario. In my Camel scenario, I set up a camel-cxf producer endpoint using a rpc/literal styled wsdl in the payload mode. That means, for an operation, its message parts corresponds to the parameters of the operation. And when the message is serialized, the operation name becomes the root element of the soap body child that in turn contains those parameters as its child elements. When I was passing the XML payload over my camel route to this endpoint, I thought I could pass the payload XML that has the operation name as the root element just as if its corresponding doc/literal wsdl were used. But this didn't work, as CXFEndpoint tried to match the root element against the message parts of the operation. That means, if the operation has one parameter and I pass this parameter as the XML payload, the call succeeds. But for other cases when there is zero parameter or more than one parameter in the operation, there is no way to pass a valid payload for this operation, as the payload is not a wellformed xml document. Ideally, I think we should be able to pass the same XML payload as if its corresponding doc/literal converted wsdl were used, that means, the XML payload with the operationName as the root and CXFEndpoint should unwrap the operation element for the rpc/literal case to fill the CXF's message content. I just wanted to ask if I am doing something wrong here or if this rpc/literal in camel-cxf is a known limitation? thanks. regards, aki
packagescan is not working in Java Webapp web.xml
I'm trying to register Camel Routes (written in Java DSL) in a package
through web.xml. The routes were not registered when I used the package
scanning (e.g.1 below). As a side note, the route registered fine when I
added it at the class level in web.xml (see e.g.2 below).
Camel version used: 2.13.1
Documentation is available at:* Using package scanning
http://camel.apache.org/servletlistener-component.htm *
*e.g.1:* Below does not work.
context-param
param-namerouteBuilder-MyRoute/param-name
param-valuepackagescan:com.isone.oishe24.camel.routes/param-value
/context-param
*e.g.2: *Below works fine
context-param
param-namerouteBuilder-MyRoute/param-name
param-valuecom.isone.oishe24.camel.routes.CamelMyBatisRoute/param-value
/context-param
All classes in the package extends RouteBuilder
*I'm using Maven and I do haven the dependencies below:*
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-servletlistener/artifactId
version${camel.version}/version
/dependency
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-servlet/artifactId
version${camel.version}/version
/dependency
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-core/artifactId
version${camel.version}/version
/dependency
Has anyone encountered the issue?
--
View this message in context:
http://camel.465427.n5.nabble.com/packagescan-is-not-working-in-Java-Webapp-web-xml-tp5752761.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Potential bug in sFTP (jSCH)?
Hi,
I am using Camel 2.12.0.
I have a route that establishes a sFTP connection.
I have set the route so that it will attempt to re-connect every 15 minutes
and then disconnect.
This is set up because the sFTP service provider has explicitly requested
not to keep connection open and poll at regular intervals.
route id=emir_sftpDTCCToReform5 reform:name=Emir Messages
from DTCC
SFTP5 reform:systemName=Emir Messages from DTCC SFTP5
from
uri=quot;sftp://${emir.dtcc.sftp.user}@${emir.dtcc.sftp.url}///DTS4.DOWN.G5${emir.gtr.OriginatorId}?filter=#sftpFilteramp;amp;disconnect=trueamp;amp;idempotent=trueamp;amp;idempotentRepository=#jpaStoreamp;amp;password=${emir.dtcc.sftp.password}amp;amp;binary=trueamp;amp;delay=90amp;amp;stepwise=falseamp;amp;lt;imaximumReconnectAttempts=0/
setHeader headerName=messageType
simpleSFTPDTCC/simple
/setHeader
to uri=jms:queue:queue.incomingEvents/
/route
The connection works fine as expected but I see the following in the log
every time the route disconnects
[2014-06-24 18:57:25,300 Camel (camel) thread #133 -
sftp://F7DGTLRW@207.45.41.162:22///DTS4.DOWN.G5TLR] SftpConsumer
INFO Connecte
d and logged in to: sftp://F7DGTLRW@207.45.41.162:22
[2014-06-24 18:57:25,707 Camel (camel) thread #133 -
sftp://F7DGTLRW@207.45.41.162:22///DTS4.DOWN.G5TLR] SftpOperations
INFO JSCH -
Disconnecting from 207.45.41.162 port 22
[2014-06-24 18:57:25,708 Connect thread 207.45.41.162 session]
SftpOperations INFO JSCH - Caught an exception, leaving
main loop due
to socket closed
I am trying to set the log to debug level - but I am unable to change the
log level for jSCH component to get debug.
I have tried setting
log4j.logger.org.apache.camel.component.jsch=DEBUG
But this has no effect.
Has anyone else had this problem - I do not see this as a show stopper -
since the route reconnects as expected but I am concerned that there could
be stale ssh sessions left open.
Can some one advise on how to tackle this?
regards
D
--
View this message in context:
http://camel.465427.n5.nabble.com/Potential-bug-in-sFTP-jSCH-tp5752764.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: seda not blocking when full
If I use the send API, and I'm assuming this is a producer template send method, how do I determine when the exchange has completed the seda route from the thread that calls send? -- View this message in context: http://camel.465427.n5.nabble.com/seda-not-blocking-when-full-tp5752712p5752765.html Sent from the Camel - Users mailing list archive at Nabble.com.
Failed to register topic
Hello, Has anyone seen the following error before, while working with JMS topics in Camel? I am using Camel to talk between a single JMS (AMQ) broker and a network of brokers. I have searched for answers, but apparently no one has encountered Failed to register topic before. Any help is appreciated. Here is the stack trace: jvm 1| 13:57:25,820 WARN [/wdts.lc][MBeanBridgeDestination] (ActiveMQ Transport: ssl://mc-primary.localhostcasino.wdgaming.local/127.0.0.1:62080) Failed to register topic://wdts.mgmt jvm 1| javax.management.InstanceAlreadyExistsException: wdts.lc:brokerName=lc-lc-01,connector=networkConnectors,networkConnectorName=bridge-lc-01,networkBridge=tcp_//127.0.0.1_62080,type=Broker,direction=inbound,destinationType=Topic,destinationName=wdts.mgmt jvm 1| at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453) jvm 1| at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1482) jvm 1| at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:962) jvm 1| at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:916) jvm 1| at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) jvm 1| at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:492) jvm 1| at org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380) jvm 1| at org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72) jvm 1| at org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:96) jvm 1| at org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115) jvm 1| at org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1642) jvm 1| at org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:614) jvm 1| at org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:195) jvm 1| at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116) jvm 1| at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50) jvm 1| at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113) jvm 1| at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:270) jvm 1| at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83) jvm 1| at org.apache.activemq.transport.tcp.SslTransport.doConsume(SslTransport.java:102) jvm 1| at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214) jvm 1| at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) jvm 1| at java.lang.Thread.run(Thread.java:695) Regards, Jeff Please take note: This email, including attachments, contains information which may be confidential or legally privileged and is only for the use of the individual or entity to whom it is properly addressed. Any unauthorized review, use, disclosure, copying, or distribution is prohibited. If you have reason to believe that you have received this communication in error, or that it may be misaddressed or not intended for you, please destroy it and notify the sender immediately. Thank you.
Re: Potential bug in sFTP (jSCH)?
Could you try Camel 2.13.2?
Best,
Christian
Am 24.06.2014 20:09 schrieb deepak_a angesh...@gmail.com:
Hi,
I am using Camel 2.12.0.
I have a route that establishes a sFTP connection.
I have set the route so that it will attempt to re-connect every 15 minutes
and then disconnect.
This is set up because the sFTP service provider has explicitly requested
not to keep connection open and poll at regular intervals.
route id=emir_sftpDTCCToReform5 reform:name=Emir
Messages from DTCC
SFTP5 reform:systemName=Emir Messages from DTCC SFTP5
from
uri=quot;sftp://${emir.dtcc.sftp.user}@
${emir.dtcc.sftp.url}///DTS4.DOWN.G5${emir.gtr.OriginatorId}?filter=#sftpFilteramp;amp;disconnect=trueamp;amp;idempotent=trueamp;amp;idempotentRepository=#jpaStoreamp;amp;password=${emir.dtcc.sftp.password}amp;amp;binary=trueamp;amp;delay=90amp;amp;stepwise=falseamp;amp;lt;imaximumReconnectAttempts=0/
setHeader headerName=messageType
simpleSFTPDTCC/simple
/setHeader
to uri=jms:queue:queue.incomingEvents/
/route
The connection works fine as expected but I see the following in the log
every time the route disconnects
[2014-06-24 18:57:25,300 Camel (camel) thread #133 -
sftp://F7DGTLRW@207.45.41.162:22///DTS4.DOWN.G5TLR] SftpConsumer
INFO Connecte
d and logged in to: sftp://F7DGTLRW@207.45.41.162:22
[2014-06-24 18:57:25,707 Camel (camel) thread #133 -
sftp://F7DGTLRW@207.45.41.162:22///DTS4.DOWN.G5TLR] SftpOperations
INFO JSCH -
Disconnecting from 207.45.41.162 port 22
[2014-06-24 18:57:25,708 Connect thread 207.45.41.162 session]
SftpOperations INFO JSCH - Caught an exception, leaving
main loop due
to socket closed
I am trying to set the log to debug level - but I am unable to change the
log level for jSCH component to get debug.
I have tried setting
log4j.logger.org.apache.camel.component.jsch=DEBUG
But this has no effect.
Has anyone else had this problem - I do not see this as a show stopper -
since the route reconnects as expected but I am concerned that there could
be stale ssh sessions left open.
Can some one advise on how to tackle this?
regards
D
--
View this message in context:
http://camel.465427.n5.nabble.com/Potential-bug-in-sFTP-jSCH-tp5752764.html
Sent from the Camel - Users mailing list archive at Nabble.com.
