But is the error sufficient to force Camel to shutdown? I assume it is given
the resource, in this case, is no different than memory; if there's none
left, the process cannot continue.
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-shutdown-Camel-context-when
i-2.15.1.redhat-621084.jar!/:2.15.1.redhat-621084]
>
>
> ----------
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/How-to-shutdown-Camel-
> context-when-threshold-exceeded-tp579
How-to-shutdown-Camel-context-when-threshold-exceeded-tp5793360p5793376.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ing it. We observe this
> happening under high load situations. Do any Camel endpoints have a default
> setting that automatically stops the context? I would think not but I
> figured I'd ask,
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/How-to-s
I'd ask,
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-shutdown-Camel-context-when-threshold-exceeded-tp5793360p5793366.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ically shuts down the context if a setting on the
> endpoint is exceeded?
>
>
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/How-to-shutdown-Camel-context-when-threshold-exceeded-tp5793360.html
> Sent from the Camel - Users
Is there any endpoint in Camel, either seda, direct, activemq, jpa, or
splitter, that automatically shuts down the context if a setting on the
endpoint is exceeded?
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-shutdown-Camel-context-when-threshold-exceeded
