Re: Camel processor memory leak

[majid]

Hi All,

I fixed the issue.
Basically, when errorHandler(deadLetterChannel("seda:error")) is global to a
route, some mbeanserver.NamedObject  is retaining a reference to the
processor.

I used instead 

 @Override 
    public void configure() throws Exception { 
        
        from("seda:error") 
                .errorHandler(deadLetterChannel("seda:error"))
                .process(errorHandlerProcessor).end(); 
   } 

Is it an issue in Camel ? or should we use specific error handler only ?



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-processor-memory-leak-tp5763905p5763947.html
Sent from the Camel - Users mailing list archive at Nabble.com.