Hi,
We are using the DB as a poor man's queue and we have two instances from our
application running. This means we have competing consumers.
By default the jpa consumer uses LockType.WRITE. Is it possible to configure
this to PESSIMISTIC locking? We call a legacy service which is not IDEM
POTENT
Hi
Ah looks like we can add an option so you can configure this. Feel
free to log a JIRA ticket. And as we love contributions, you are
welcome to work on a patch.
http://camel.apache.org/contributing.html
On Thu, Aug 29, 2013 at 8:55 AM, Bart De Neuter bdeneu...@gmail.com wrote:
Hi,
We are
Hi,
I have the following route:
from(cxf://http://0.0.0.0:8080/proxy?dataFormat=MESSAGEserviceClass=com.ProxyClass;)
.process(new Processor() {
@Override
public void process(Exchange exchange) throws
When you using the MESSAGE data format, you can consume and produce message
body as a stream.
Please go through the camel-cxf wiki page[1] for more information.
[1]http://camel.apache.org/cxf.html
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog:
Hi,
If you want to use payloads, why don't you use the dataFormat=PAYLOAD? Then you
will have the payload in the message body (and can do with it what you intend
to to).
Best regards
Stephan
-Original Message-
From: Ernest Lu [mailto:syf...@sina.com]
Sent: Donnerstag, 29. August 2013
Hello All!
We are using Apache Camel 2.10.4 within Apache Karaf 2.3.1.
We have a Camel Route and there is a logging endpoint inside:
The logging in Apache Karaf is configured in a way that every bundle
produces its
own logfile and that Camel Route also resides in such a bundle:
My intention
Hi Claus,
I created a jira ticket and included a patch.
--
View this message in context:
http://camel.465427.n5.nabble.com/Configurable-LockType-for-JpaConsumer-tp5738192p5738206.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Bharat.
I am still not able to get rid of that dependency issue.. Can you suggest
what too do now? The dendendency artifact ID and all that corresponds toa
valid path on the repositories.. Still the same issue..
--
View this message in context:
There is a workaround in order to use the bundle log file. You can reach this
by using a Camel Processor
and from there use the logger from the class that contains the route
definition:
The endpoint to(log:...) is part of Apache Camel and therefore the log
message doesn't reach
the bundle log
Hello,
I am trying to setup a CXF endpoint from a webapp, but I am getting the
exception:
How does CXF binds to the Servlet?
My web.xml is basically the one described at
http://cxf.apache.org/docs/servlet-transport.html
My Spring config contains :
Using Camel 2.11.1 / WebLogic 10.3.4 /
Well I found the solution (thanks Google ;-) ), I needed the address
attribute and I shouldn't prefix this address by http://...
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-endpoint-with-Servlet-transport-tp5738217p5738218.html
Sent from the Camel - Users mailing
Hi,
The below mentioned link will be use full for you.
http://servicemix.396122.n5.nabble.com/OSGI-Bundle-log4j-td421030.html
In you osgi application do you have log4j.xml file?
--
View this message in context:
Hi,
I'm writting because I'm trying to poll my Google mail inbox for mails. I
changed the settings of my Google mail account to allow IMAP access but I'm
having some problems.
This is my basic route definition:
Hi
*Any one advice me on this code snippet.The exception block onexception is
not triggered when the expection is thrown.The address in jaxws:client
id= is throwing target invocation error.But the exception handler is not
picking the exceptions.Advice me on the correct usage of exception handler
Hi,
I believe the on exception clues will not catch the exception thrown while
creating the jaxws:client. Because it catches the exceptions that are
triggered with in a camel context. Might be i am wrong. You can use
try/catch for catching the exceptions in a
Ok, i think that connecting with protocol imap (IMAP without SSL) does not
work because isn't supported by GMail. I need to use imaps (IMAP with SSL).
But in that case i still have a problem:
Consumer
http://stackoverflow.com/questions/9619030/resolving-javax-net-ssl-sslhandshakeexception-sun-security-validator-validatore
A more interesting question is why your Java installation does not
recognise the Google CA certificate. Either your installation is old or
Oracle isn't updating the shipped
Hi Hilderich,
Are you using the MDCSiftAppender? What key are you sifting on?
Perhaps this post will help you:
http://dywicki.pl/2012/02/advanced-apache-camel-logging-and-best-practices/.
Regards,
*Raúl Kripalani*
Apache Camel PMC Member Committer | Enterprise Architect, Open Source
Just to clarify: I think you should set appropriate contextIds for your
Camel Contexts, and sift your logs based on the camel.contextId key in
the MDC, not the camelContextId key as the post suggests (as we changed the
key from 2.10 onwards).
Otherwise, if you use the bundle ID as the sifting
Hi, I've been trying to get a route to work with the Camel Quickfix
implementation and could use some help. All I'm trying to do is create a
route that accepts messages from QuickfixJ and stores them in a SQL Server
database via the camel sql component and the MS JDBC driver. So I created
the
ok, after looking further at this, we discovered that we were under the wrong
assumption on how the splitter in Camel works. We got that assumption after
playing with the ZipSpliter. After running into this problem, we played
with simple spliters, we figured that our assumption was wrong. I
no, it will not. sounds like the error is being thrown when trying to
create the jaxws client when the spring context bootstraps? doesn't sound
related to camel, might have to ask the spring guys whats the best way to
handle exceptions on startup. best bet is to just correct the URL :)
On Thu,
I have a number of routes that do a bit of processing and then hand off to
other routes. One of the upstream routes splits streaming data to a
downstream route. If that downstream route encounters problems it should
notify the upstream route to stop splitting and cease processing. What
Have you tried the stopOnException() option of the Splitter?
Use it in combination with direct or seda endpoints. If you use JMS, you
can enable the transferException option to ensure that the Exception is
propagated back to the caller in its original form.
Regards,
*Raúl Kripalani*
Apache Camel
Dejan,
Should I create a formal bug for this issue with the sample of code which I
uploaded to this group?
At this point, I tried all the options I could think of and could not fix
this issue. For now, we are using JmsTemplate approach to go directly to
the ActiveMQ Broker bypassing Camel,
Claus,
I am running into the same issue as stated above. Are there any examples of
Camel splitting files 'out of the box'? I tried a prelim search, but it was
unsuccessful.
Thanks!
--
View this message in context:
26 matches
Mail list logo