Hi,
I have problems creating a jmx connector for remote monitoring. I tried
putting -Dorg.apache.camel.jmx.createRmiConnector=true in the VM arguments,
as well as adding the rmi connector inside the code as below:
DefaultManagementAgent agent = new
DefaultManagementAgent(camelContext);
A good idea is to check the unit test of camel-jms and search for
exceptionListener to see how to use this option.
You need to refer to a bean id which it will lookup in the spring xml file.
exceptionListener=foo
On Tue, Dec 14, 2010 at 5:28 AM, Damian Harvey wrote:
> I had an error in a pro
Hello,
William Tam schrieb am 13.12.2010 23:18:31:
> We do have an unit test for JAXWS handler in PAYLOAD mode.
>
> https://svn.apache.org/repos/asf/camel/trunk/components/camel-
>
cxf/src/test/java/org/apache/camel/component/cxf/CxfWsdlFirstPayloadModeTest.java
>
> https://svn.apache.org/rep
I had an error in a property file with an incorrect queue name that didn't
exist. When the JMS Reply was hit a JMSException was generated "MQJMS2008:
failed to open MQ queue". This is to be expected. What happens is that Camel
goes into an infinite loop trying to process the message.
I was expe
I am a new Camel user.
I am trying to SFTP a file over to a local directory. I am using the
following code for the same:
public static void main(String args[]) throws Exception {
// create CamelContext
CamelContext context = new DefaultCamelContext();
Hi,
It's looks you are using the simple front end which means there is no
@WebService annotation in your SEI.
Current we don't support the JAXWS-handler in simple front end, please
make sure you are using the jaxws front end.
On 12/14/10 5:54 AM, Thomas KRIECHBAUM wrote:
Hello,
how can I a
We do have an unit test for JAXWS handler in PAYLOAD mode.
https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/CxfWsdlFirstPayloadModeTest.java
https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/resources/org/apac
Hello,
how can I assign JAXWS-handlers to an CXF-endpoint using data format
PAYLOAD?
The documentation
http://camel.apache.org/cxf.html#CXF-ConfiguretheCXFendpointswithSpring
suggests the child element cxf:handlers. But when starting the camel
context the following exception is thrown:
?
Cau
Thanks Claus.
For anyone else interested I just added:
public void process(Exchange exchange) {
camelContext.getInflightRepository().remove(exchange);
etc etc
And all works well.
On Mon, Dec 13, 2010 at 5:39 AM, Claus Ibsen wrote:
> When you stop a route from within the same route you have
On Mon, Dec 13, 2010 at 6:28 PM, klausb wrote:
>
> The bean integration is a nice thing, because it hides the camel middleware
> from the components. Unfortunately I can only use beans in a route, where
> the trigger is defined elsewhere as a camel endpoint. What is the strategy
> to define a rout
Hi Christian,
Unfortunately, I don't find yet the time to investigate this issue but
should done soon for a customer in Germany which would like to parse big
XML file (around 250 Mb) using Xpath. After a rapid quick search last
week, I found this interesting note on Saxon web site -->
http://
Hi Christian,
Unfortunately, I don't find yet the time to investigate this issue but
should done soon for a customer in Germany which would like to parse big
XML file (around 250 Mb) using Xpath. After a rapid quick search last
week, I found this interesting note on Saxon web site -->
http://
The bean integration is a nice thing, because it hides the camel middleware
from the components. Unfortunately I can only use beans in a route, where
the trigger is defined elsewhere as a camel endpoint. What is the strategy
to define a route, where a bean initiates a message exchange because it h
Hi All,
I have two brokers.
I also have 2 JMS Clients (a producer and a consumer)
jms config: tcp://brokerB-ip:61616
jms:queue:request?replyTo=queue:response
Producer sends a synchronous request (and it is expecting a response) to a
queue on broker B, and it expects a response on queue respon
Hi,
I have a simple scenario using the file endpoint that polls a file and
sends it to a oneway CXF endpoint that calls an external web service.
The scenario works fine with Camel 2.4.0 with CXF 2.2.11, but does not
work with Camel 2.5.0.
The processing itself works fine with 2.5.0, but after the
Thanks Claus!
On Mon, Dec 13, 2010 at 4:53 PM, Claus Ibsen wrote:
> Hi
>
> See also AMQ FAQs
> http://activemq.apache.org/should-i-use-transactions.html
>
>
>
> On Thu, Dec 9, 2010 at 2:07 PM, Ioannis Canellos
> wrote:
> > Hi Claus,
> >
> > Here are the results of the tests I run:
> >
> > Produ
Hi
See also AMQ FAQs
http://activemq.apache.org/should-i-use-transactions.html
On Thu, Dec 9, 2010 at 2:07 PM, Ioannis Canellos wrote:
> Hi Claus,
>
> Here are the results of the tests I run:
>
> Producer Only: 10msg/sec (transacted=true) / 2800 msg/sec
> (transacted=false).
> Consumer Only:
I added a System.out.println in the route class to show that when the route
is starting wsUrl is set properly.
I also added a println to the test class right before I add the adviceWith.
The adviceWith call in the test class appears to occur after the route has
successfully loaded.
I was trying
Add a system.out.println(wsUrl) so you can see that the url has been
resolved and spring have invoked the afterPropertiesSet. BEFORE the
adviceWith is being invoked in your test.
On Mon, Dec 13, 2010 at 2:55 PM, John wrote:
>
> My application has a route defined like:
>
> public MyRoute extends
My application has a route defined like:
public MyRoute extends RouteBuilder implements InitializingBean,
DisposableBean
{
private String host;
private String user;
private String pw;
private String wsUrl;
afterPropertiesSet()
{
wsUrl = "http://"; + host + "/some
Hi Claus,
As Ashwin pointed out, I'm really trying to use the onException to manage
retries to the web service. The aggregation collects requests together, then
calls a bean to create the web service call with all the aggregated
messages.
The problem I ran hit was that putting the onException be
Hi Claus,
Thanks. I had the correct content-type. What I did not realize, though, is
that the Content-Transfer-Encoding seems to be determined automatically
based on the actual content. Smart.
I always tested with a simple message without special characters; which
caused a 7bit encoding. Then b
I created a ticket
https://issues.apache.org/jira/browse/CAMEL-3423
Then in the future you can manage it using JMX.
Currently you can just stop and start the route again.
Or extend the FileIdempotentRepository class and add a reset method yourself.
On Mon, Dec 13, 2010 at 12:11 PM, jmh wrote:
Hello everyone,
I've got a situation where I encounter an exception from the netty producer
when it gets used right after Camel has started up.
This happens once and once only, afterwards everything is fine. The
exception I am getting is:
2010-12-12 00:59:15,856 14232 INFO [main]
[org.apache.cam
Hi Claus,
suppose I need to re(send) a set of messages (validation failed before but
now is OK) without stopping Camel.
My idea was to suppress some keys in the idempotent file to allow the the
set of messages to be performed again.
But I don't know if it's possible to reload the idempotent
Hi Claus,
suppose I need to re(send) a set of messages (validation failed before but
now is OK) without stopping Camel.
My idea was to suppress some keys in the idempotent file to allow the the
set of messages to be performed again.
But I don't know if it's possible to reload the idempotent fil
On Sun, Dec 12, 2010 at 2:28 PM, jmh wrote:
>
> Hi Camel riders,
>
> what is the best way to refresh at runtime a file-based Idempotent Consumer
> ?
What do you mean by refreshing?
And why do you want to do that?
>
> Thanks in advance for your suggestions...
>
> Jean-Marc
> --
> View this mess
On Fri, Dec 10, 2010 at 10:10 PM, John wrote:
>
> Hi,
>
> I'm using camel 2.2 to create an aggregation route with an onException.
> Unfortunately it appears the onException.end() and
> aggregate().groupExchanges() are exclusive? I know the .end() is required on
> the onException, but adding it cau
On Sun, Dec 12, 2010 at 6:55 AM, John wrote:
>
> Thanks Ashwin. I'll give that a shot. I thought I had read where onException
> had to be at the start of the route, so I didn't realize I could place it
> there.
No you should not put onException inside the route. Its supposed to be
in the start of
On Mon, Dec 13, 2010 at 11:44 AM, John wrote:
>
> Hi Claus,
>
> I'm already using a wild card to try and perform the match. The issue
> appears to be with using the adviceWith method to setup the
> interceptSendToEndpoint call in my unit test.
>
> This works perfectly when the endpoint in the rout
Hi Claus,
I'm already using a wild card to try and perform the match. The issue
appears to be with using the adviceWith method to setup the
interceptSendToEndpoint call in my unit test.
This works perfectly when the endpoint in the route I'm testing is not
configured via spring properties.
Here
On Mon, Dec 13, 2010 at 10:12 AM, Christian Mueller
wrote:
>
> Hello Richard!
> Thanks for your suggestion. I'm aware of the Smook integration, because I
> developed it together with the Smooks guys. :o)
> I thought if it's possible with the splitter EIP via XPath and the
> streaming() mode, it is
When you stop a route from within the same route you have to deal with this.
You need to unregister the current exchange from the inflight registry
so Camel knows there are no inflight exchanges while it performs
graceful shutdown.
Camel in Action chapter 13 shows how to do this.
On Fri, Dec 10,
Hello jburkhardt!
I was not aware of VDT. I will have a look on it today.
Thanks,
Christian
--
View this message in context:
http://camel.465427.n5.nabble.com/Splitting-big-XML-files-using-xpath-and-streaming-tp3300695p3302841.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hello Richard!
Thanks for your suggestion. I'm aware of the Smook integration, because I
developed it together with the Smooks guys. :o)
I thought if it's possible with the splitter EIP via XPath and the
streaming() mode, it is the easiest solution (also for my junior
co-workers). But it looks lik
On Sun, Dec 12, 2010 at 7:07 AM, John wrote:
>
> Hi,
>
> I am using camel 2.2, though I did give this a shot with 2.5
>
> I have a route that has an http endpoint that is configured at startup. In
> my route builder I have something like:
>
> String wsUrl = "http://host/ws";;
>
> from("activemq:so
36 matches
Mail list logo