I have got it working. By trial and error. I am not sure why I couldn't
find a working solution for Blueprint out there. Usually indicates to me
that I was asking the wrong question. Seems that the # in the URI is the
crucial element so that a reference to the bean is being passed to the
You can create two JmsComponent beans and use the id of the bean as the
scheme in the URI. So you could have something like mqremote:queueName and
mqlocal:queueName if you gave the beans IDs of mqremote and mqlocal
respectively.
On 14 June 2016 at 17:46, Gabriel Soto wrote:
>
Hello,
We need to connect to two different JMS providers in two different
application containers:
1. A remote MQ running on WebSphere
2. A local WebSphere using the native JMS implementation
We are using Spring-only configuration.
I managed to properly connect to both containers
Thanks for the reply,
in this case the sender has no interest in any replies, that's exactly
why I changed to InOnly in the first place. A response with content
length zero is perfect, only the HTTP status code is relevant for the
sender. It was perhaps misleading to add a return of anything
Hi Both,
Thanks for your interest.
@Claus,
this toD generates only one endpoint. I try to change it to "to" format and
let you know.
One more thing, our exposed endpoint is using camel servlet.
I saw in the http4 page that if we want
Here is the full stack trace without truncation.
https://gist.github.com/owain68/4d1941c8ed7d4a05d8a57103a7bb2a16
--
View this message in context:
http://camel.465427.n5.nabble.com/Repost-Unable-to-configure-component-spring-redis-RedisTemplate-with-Blueprint-XML-tp5784053p5784054.html
Sent
Apologies for the ugly original post.
I have set up a simple route to isolate the string serialization problem
that
I am experiencing, like others, the problem where the default jdk serializer
prepends "junk" at the start of the key and value, making it
difficult/impossible to perform
Hi,
I need to process around 10,000 records concurrently.
I used concurrent consumers option. But for a single record, multiple
threads are getting created.
Kindly suggest how to process around 10,000 records in parallel.
Disclaimer: Information contained in
One quick update, I replace cxf producer end point with http4 component and
the route ran with no issues/problems.
However I still would like to understand why cxf end point is failing.
Thanks,
Pravin
--
View this message in context:
Hi,
Yes the header solution works, thank you very much for your help.
Cheers.
Anil
--
View this message in context:
http://camel.465427.n5.nabble.com/Using-XML-elements-from-the-body-in-the-log-method-tp5783973p5784047.html
Sent from the Camel - Users mailing list archive at Nabble.com.
If you want jetty to return the response from the VM endpoint then you
need to use InOut pattern so it wait for the reply message to be
ready. Otherwise you have concurrent threads that .. depending on
timing .. will set the reply either before or after jetty writes the
response.
If you want to
On Tue, Jun 14, 2016 at 4:38 PM, owain wrote:
> Is there a typo toD in here?
>
> uri="{{pricing-wsrest-endpoint}}=true=true"
> />
>
toD is a dynamic to.
How many unique endpoints does {{pricing-wsrest-endpoint}} generate in
your test?
If the dynamic part is the
Is there a typo toD in here?
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-2-17-limited-performance-not-more-than-20-req-s-tp5783980p5784041.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Have a look at using the While mode on the loop pattern.
http://camel.apache.org/loop.html
${body.length} = 5
A${body}
--
View this message in context:
Sorry XML was "nabbled".
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="
http://www.osgi.org/xmlns/blueprint/v1.0.0
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
Hi, enabling MDC to tie output together, I can see some discrepancies
between the OK and the NOT-OK cases (these are probably present when
turning on trace logging as well, but are harder to catch due to the
vast amount of log statements):
OK scenario:
2016-06-14 15:27:01.029 [INFO]
I have set up a simple route to isolate the string serialization problem that
I am experiencing, like others
non XML version here: http://stackoverflow.com/questions/32245916/redis-
serialization-prefixed-with-extra-string
I have a route set up with some beans but seem to be going round
Hi,
Yeah probably something between the VM endpoint and the bean caused this.
I extend CamelBlueprintTestSupport but works for normal CamelTestSupport as
well. Hopefully the debug log will reveal what could be going wrong in
between. See below for adding the debug methods:
public class
Thanks for the quick reply, adding a log step to the route right after
message is received by the jetty component confirms that all exchanges
have a complete body at that point. I suspect the issue is related to
the transition from delivery to vm:test and consumption by the bean from
the same
Hello,
I am not able to test this at the moment but what happens if you change the
first "from" to from("jetty:" + URI).log("${body} and ${headers}".to("")
In the case of the empty messages, does the log statement also show that
the body being empty?
You can also include debug level logs in
Hi, I get sporadic cases of no body when having a client sending small
JSON messages over http, and a jetty endpoint receiving them, and a
short route with a vm endpoint and a bean. Stream-caching is enabled.
The issue only appears when MEP is InOnly. A simple test case to
reproduce the issue
I am tied to xml. I couldn't get it working in. Can the same be achieved
using Spring Xml.?
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-How-to-dequeue-all-messages-accumulated-every-X-minutes-tp5783739p5784012.html
Sent from the Camel - Users mailing list archive
Hello Preben,
Thanks for the suggestion, you should have a message in your inbox ;)
Best
Souciance
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-training-tp5783958p5784011.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
Yes, but you don't need to do that. It was just for reference. You can save
the xpath result in a header or exchange property and then log it.
.setHeader("myxpath", xpath("path"))
.log("The xpath result is ${header.myxpath}")
On Tue, Jun 14, 2016 at 11:19 AM, anilc7 [via Camel] <
Hi Souciance
If you want I can buy you a cup of coffe too, and we can discuss Camel.
We have been using Camel for the last 4-5 years and are running about 130++
camel context in production integrating more or less everything you can
think about.
Best,
Preben
Danish Broadcasting Corporation
Thank you very much for your reply, I did look at the link you provided, the
problem there is, its using setBody method which overwrites the IN body
message and I still need access to that.
Is there any way of storing in some kind of variable?
--
View this message in context:
Hello Claus,
Thanks for the suggestions. I was actually in correspondence with Jakub
Korab during winter, but at the time we had not got that far in our project
and it was not feasible to bring him here for just 1-2 days just for me.
But I will for sure keep this option in mind. I think he runs a
On Mon, Jun 13, 2016 at 10:54 AM, souciance
wrote:
> Hi,
>
> Yeah, but not the cheapest, especially for 1-2 days and it seemed they
> brought in consultants from Stockholm.
>
I do not do Camel training - the training you can get from me, is here
in the community
You can use camel xpath: http://camel.apache.org/xpath.html to extract
whichever element you want and log that. You can also look here for an
example:
http://stackoverflow.com/questions/22870755/camel-using-xpath-to-parse-xml-in-message-body
--
View this message in context:
Hi
Using log4j classloader log manager you should be fine.
Le 14 juin 2016 07:36, "balaji ponnusamy" a écrit :
> Hi All,
>
> I am having Ear file which has multiple WAR files inside and deployed in
> Web
> Logic 10.x server . Each WAR file is referring separate log
30 matches
Mail list logo