After committing the changes and re-deploy the app , we still see the
OOM Exception.
Seems like it's to much for the Java VM to create a now Consumer evert
30 seconds. Any other suggestions?
Thx
Norman
2010/3/19, Norman Maurer :
> Ah right..
>
> Thx for the pointer :)
>
> Bye,
> Norman
>
>
> 201
YESYESYES!
that did it
after replacing jetty-6.1.9 libs with the 6.1.22 libs everything went fine.
Thank you very very much for your short and precise analysis, this helped me
a lot!
Henning
Claus Ibsen-2 wrote:
>
> Hi
>
> Camel 2.2.0 is using Jetty 6.1.22, so maybe the old 6.1.9 has an iss
worked perfectly, thanks :)
Da: Claus Ibsen [claus.ib...@gmail.com]
Inviato: domenica 21 marzo 2010 14.14
A: users@camel.apache.org
Oggetto: Re: Problem with Http component and redeliveryPolicy
Hi
You XML is invalid.
The delay attribute is called redelive
Ok, I will do this.
I opened an issue on JIRA and will track further discussions there.
https://issues.apache.org/activemq/browse/CAMEL-2565
--
View this message in context:
http://old.nabble.com/Proposal-for-a-new-camel-bean-validation-component-based-on-jsr-303-tp27950969p27976253.html
Sent
Hi
Most of the work is done now. What remains is to do some wiki documentation.
I recon we got a good solution now with thread pool profiles which
makes it easy to setup the threading model you need.
On Fri, Mar 19, 2010 at 11:07 AM, Claus Ibsen wrote:
> Hi
>
> You can see notes here as well
>
Hi
Looks promising. Nice that JSR-303 can gather all the validations
error in one go, so you got them all.
I recon for starters you try to implement this as a new
bean-validation component.
Then later we can see how to hookup with a predicate.
On Sun, Mar 21, 2010 at 12:02 PM, Christian Mueller
Hi
You XML is invalid.
The delay attribute is called redeliveryDelay, eg something like this:
See this unit test just committed
http://svn.apache.org/viewvc?rev=925764&view=rev
On Sat, Mar 20, 2010 at 2:13 PM, Yari Marchetti wrote:
> Hi everyone,
> i configured Camel with
On Sat, Mar 20, 2010 at 2:13 PM, Yari Marchetti wrote:
> Hi everyone,
> i configured Camel with a route like:
>
>
>
>
>
> java.net.ConnectException
> backOffMultiplier="2"
> delay="1000"
>
Hi
Camel 2.2.0 is using Jetty 6.1.22, so maybe the old 6.1.9 has an issue.
Here is the Maven generated dependency:list for camel-jetty in Camel 2.2.0:
[INFO]
[INFO] Building Camel :: Jetty
[INFO]task-segment: [dependency
Hi Willem,
thank you for your reply.
Unfortunately the problem must be somewhere else
I tried some combinations always getting the same Exception:
jetty:http://localhost:9080/?matchOnUriPrefix=true
jetty:http://localhost:9080/MyApp/?matchOnUriPrefix=true
jetty:http://localhost:9080/
jet
Hello Claus!
My first and easiest implementation of the bean-validator looks like (it is
inspired from the schema validation component):
public class BeanValidatorComponent extends DefaultComponent {
protected Endpoint createEndpoint(String uri, String remaining,
Map parameters) throws Exce
yes i'm sorry, completely forgot about it. I'm using version 2.2.0
Da: Claus Ibsen [claus.ib...@gmail.com]
Inviato: sabato 20 marzo 2010 15.03
A: users@camel.apache.org
Oggetto: Re: Problem with Http component and redeliveryPolicy
Hi
Remember to state the
On Sat, Mar 20, 2010 at 8:43 PM, tide08 wrote:
>
> So, would it make sense that in my customConsumer that extends
> ScheduledPollConsumer, I override doStart() to schedule more tasks? Is this
> thread-safe to do?
>
You can do that.
Also nothing is thread safe out of the box, its something that YO
13 matches
Mail list logo
