Hello,
We have a system where we want to monitor all the exchanges flowing
throw camel pipeline (track completed, inprogress, failed exchanges).
*Camel context are added at runtime*. We want enrich pipeline to trigger
start and end of work flow, also add error handler to pipeline. Start
int
Hi,
We are running Camel 2.4 and are to unmarshal FixedLength lines to objects
using Bindy.
The FLV record is defined with:
@FixedLengthRecord(length = 128, paddingChar = ' ')
I.e. 128 character long with spaces as default paddingchar.
The last "field" in the line is defined as:
@DataField(pos
Hi,
Hmm - it looks like the trim() is removed in the 2.6 release so I'll see if
I can give it a try.
/Mikael
--
View this message in context:
http://camel.465427.n5.nabble.com/BindyFixedLengthDataFormat-trimming-lines-tp3374142p3374157.html
Sent from the Camel - Users mailing list archive at N
Hi,
I took a look at your code and I see that when you add interceptors you do
not stop the running camel context or the routes and then re-start it the
context or routes after adding the interceptors.
Please update your code and try again.
Cheers,
Ashwin...
-
Hi,
I took a look at your code and I see that when you add interceptors you do
not stop the running camel context or the routes and then re-start it the
context or routes after adding the interceptors.
Please update your code and try again.
Cheers,
Ashwin...
-
Hi,
I've a problem with this simple route (Camel 2.6.0):
from("servlet:///myServlet?matchOnUriPrefix=true").to("http://localhost:8080/service?bridgeEndpoint=true";)
If I send an HTTP packet to the servlet, the Content-Type header is removed.
The same behavior if I force the Content-Type between
On Mon, Feb 7, 2011 at 2:31 PM, Cappa Roberto
wrote:
> Hi,
>
> I've a problem with this simple route (Camel 2.6.0):
>
> from("servlet:///myServlet?matchOnUriPrefix=true").to("http://localhost:8080/service?bridgeEndpoint=true";)
>
> If I send an HTTP packet to the servlet, the Content-Type header i
Hi Ashwin,
Thanks for your reply.
adviceRoute javadocs mentioned "Will stop and remove the old route from
camel context and add and start this new advised route."
When tried with restarting camel context, got NPE while advice route for
start interception
Exception in thread "main" java.lan
I've just used jConsole to analyze our application after running it through
the weekend, many endpoints URI have been served and all of them have been
cached. It appears it is not caching 1000 endpoints at most.
--
View this message in context:
http://camel.465427.n5.nabble.com/Memory-leak-in-ca
On Mon, Feb 7, 2011 at 3:38 PM, Marco Crivellaro
wrote:
>
> I've just used jConsole to analyze our application after running it through
> the weekend, many endpoints URI have been served and all of them have been
> cached. It appears it is not caching 1000 endpoints at most.
Using jconsole you ar
Yes I am viewing JMX, sorry.
but mail recipients or ftp parameters in URI won't allow us to make use of
the recipientList which is very handy and it is on the basis of our
application (we are serving a very high number of endpoints dynamically
using the recipientList).
--
View this message in c
Hello,
I'm currently evaluating Camel for Data Integration purpose. So far, it
works very well, but I'm facing the following issue in my test case : when
dealing with a (not so) large file (5k lines), the Camel Context is shutdown
before all lines are processed, and some assertions
(MockEndpoint.
Is disabling JMX an option for you?
This could be a workaround/solution for you.
Christian
Hi Xavier,
I suspect camel did the right thing. Camel waits for in-flight messages to
complete [1].
I don't know how you set up your routes, but I suspect that you stop the
consumer in one of the steps while there are still messages to consume. Since
the consumer didn't grab them yet, and hence
Hi,
If you stop the CamelContext all the routes are automatically stopped.
Alternatively, you can stop the routes and make changes without stopping the
context and then start the routes individually.
As for the second error, it is quite clear... Looks like you are starting
two routes with the sa
Hello Hadrian,
Thank you for those answers. I'll have a look at the BAM facilities provided
by Camel. I agree that there needs to be some application-level specifics to
implement (such as the total number of treated messages I should look at,
including errors...)
I actually agree with you that Ca
I have a CXF configuration (in applicationContext.xml) that talks to
IBM MQ via JNDI resources.
I'd like to use this cxf-configured message queue as a Camel destination.
I'm stuck on the difference between
org.apache.cxf.transport.jms.JMSConfiguration and
org.apache.camel.component.jms.JmsConfigur
Hi Ashwin,
Sorry i think, i was not clear in last post.
I understand that stopping camel context will stop all the routes. What
i did was
*Test 1: *Tried stopping camel context and then modified routes and
again started the context
/CamelContext camelContext = (CamelContext)
context.getBea
On Mon, Feb 7, 2011 at 5:38 PM, Marco Crivellaro
wrote:
>
> Yes I am viewing JMX, sorry.
>
>
> but mail recipients or ftp parameters in URI won't allow us to make use of
> the recipientList which is very handy and it is on the basis of our
> application (we are serving a very high number of endpoi
On Mon, Feb 7, 2011 at 10:00 PM, Xavier Coulon wrote:
> Hello Hadrian,
>
> Thank you for those answers. I'll have a look at the BAM facilities provided
> by Camel. I agree that there needs to be some application-level specifics to
> implement (such as the total number of treated messages I should
On Mon, Feb 7, 2011 at 5:56 PM, Xavier Coulon wrote:
>
> Hello,
>
> I'm currently evaluating Camel for Data Integration purpose. So far, it
> works very well, but I'm facing the following issue in my test case : when
> dealing with a (not so) large file (5k lines), the Camel Context is shutdown
>
21 matches
Mail list logo
